The document discusses the work package 4 (WP4) goals of an research project including: 1) Developing a REST framework to access in-situ data from multiple spacecraft without downloading. 2) Deciding on techniques like Grad-Shafranov modeling and minimum variance analysis to analyze flux rope structures. 3) Determining which parameters to include in the catalog such as event times, speeds, and modeling results. 4) Addressing issues like how to categorize complex events and connect the catalog to other solar and heliospheric catalogs.

1.
WP4:
Getting
in-­‐situ
data
CDAS
REST
framework
ž Provides
universal
interface
to
access
CDAWeb
data
ž No
need
to
download
data
ž Can
be
used
with
any
programming
language
ž Already
tested
and
successfully
applied
by
our
students
CDAS
REST
XML
request
data
IDL/C/Python/etc.

2.
WP4:
Deciding
on
techniques
Flux
rope
modeling
ž Grad-­‐Shafranov
(mostly
for
Wind,
ACE,
STEREO,
Ulysses)
ž MVA
(VEX,
MESSENGER)
ž Should
we
use
some
other
techniques?

3.
WP4:
Deciding
on
catalogue
parameters
Times
of
different
structures
ž Shocks
time
ž Ejecta
start
and
stop
times
ž Flux
rope
time
ž Do
we
list
only
clear
flux
rope
ejecta
or
complex
ejecta
too?
Basic
parameters
ž Average/maximum
speed,
magnetic
field,
etc.
ž Average/maximum
density
in
different
parts
of
the
structure
Modeling
parameters
ž Flux
rope
orientation
ž Helicity
ž Impact
parameter

4.
WP4:
Issues
How
to
start?
ž Start
from
a
few
clear
flux
ropes
with
unique
solar/HI
CME
association
ž First,
build
a
simple
catalog
(add
details
when
needed)
ž Discuss
with
HI/solar
WPs
Questions
ž How
to
deal
with
the
large
variety
of
ICME
events
and
with
complex
and
unclear
events?
(Or
do
we
include
only
clear
events?)
ž How
to
connect
most
efficiently
with
the
HI/solar
catalogs
(e.g.,
agreeing
on
data
formats,
parameters
that
are
most
useful
for
comparison,
etc.)

5.
Interplanetary
shocks
database
ž Currently
is
being
developed
at
the
University
of
Helsinki
ž Can
be
used
in
conjunction
with
HELCATS
catalogue
ž An
example
of
user-­‐friendly
yet
feature-­‐rich
interface