2405
Comment:
|
2416
|
Deletions are marked like this. | Additions are marked like this. |
Line 15: | Line 15: |
|| sdo.fds || sdo.fds_orbit_ingesthist sdo.fds_orbit_vectors (contains both helio- and geo-centric velocity) sdo.fds_orbit_vectors_sbox sdo.hk_dayfile (Prime keys – date, apid, source, also keyword source=moc. Contains all dayflies for all SDO APIDs from MOC product server) sdo.moc_fds sdo.ancillary_science_data |
. sdo.fds . sdo.fds_orbit_ingesthist . sdo.fds_orbit_vectors (contains both helio- and geo-centric velocity) . sdo.fds_orbit_vectors_sbox . sdo.hk_dayfile (Prime keys – date, apid, source, also keyword source=moc. Contains all dayflies for all SDO APIDs from MOC product server) . sdo.moc_fds . sdo.ancillary_science_data |
Line 24: | Line 23: |
hmi.lev0 hmi.hk_dayfile |
. hmi.lev0 . hmi.hk_dayfile |
Line 27: | Line 26: |
aia.lev0 aia.hk_dayfile |
. aia.lev0 . aia.hk_dayfile |
Line 31: | Line 29: |
A drms module, getfdsorbit – input: time (something that is not on the original time grid, so interpolation will be necessary), coord system (also specifies helio or geo/J2000 ecliptic or something else or interpolation parameters); output: position vector and velocity vector. Make the output doubles. (Art) No need for an intermediate series with interpolated/converted data. |
. A drms module, getfdsorbit – input: time (something that is not on the original time grid, so interpolation will be necessary), coord system (also specifies helio or geo/J2000 ecliptic or something else or interpolation parameters); output: position vector and velocity vector. Make the output doubles. . No need for an intermediate series with interpolated/converted data. |
Level 0.3 / Level 0.5 Data
Level 0.3 and Level 0.5 data are very similar. One could say that the Level 0.3 data is a temporary, best effort set of Level 0.5 data based on what is available at the time of computation.
In theory, after N days the Level 0.3 data will disappear from a given date and a person will only view the Level 0.5 data. The value of N is yet to be determined. It may be as low as 5 days. Essentially, Level 0.3 is intended to be "QuickLook" data, only desired by the user who needs data ASAP (as opposed to a science analyst user).
Sources for the Level 0.3/0.5 data include:
- Level 0.1 data (metadata and images from the instruments)
- Orbit prediction data from the GSFC Flight Dynamics Center
- Attitude data from the spacecraft
- Temperature and Power data from the spacecraft and instruments
Data series that feed Level 0.3/0.5 include:
sdo.*
- sdo.fds
- sdo.fds_orbit_ingesthist
- sdo.fds_orbit_vectors (contains both helio- and geo-centric velocity)
- sdo.fds_orbit_vectors_sbox
- sdo.hk_dayfile (Prime keys – date, apid, source, also keyword source=moc. Contains all dayflies for all SDO APIDs from MOC product server)
- sdo.moc_fds
- sdo.ancillary_science_data
hmi.*
- hmi.lev0
- hmi.hk_dayfile
aia.*
- aia.lev0
- aia.hk_dayfile
Functions intended to feed the Level 0.3/0.5 data series include:
- A drms module, getfdsorbit – input: time (something that is not on the original time grid, so interpolation will be necessary), coord system (also specifies helio or geo/J2000 ecliptic or something else or interpolation parameters); output: position vector and velocity vector. Make the output doubles.
- No need for an intermediate series with interpolated/converted data.
- Must change the master LZP MOC server download script, mocDlLzp.csh (JSOC/proj/lev0/scripts/mocserver), to download files to /surge, and then call script to ingest into sdo.hk_dayfile.
- The script/module to ingest into sdo.hk_dayfile must be created.
- Needs a sdo.asdp - Contains all the ancillary science data packet information (apid 129) (Jennifer).
- Need to write an ingest script/module for sdo.asdp.
- Input to this script is sdo.hk_dayfile.
- Need a master lev 0.3 record creation module. It calls modules like getfdsorbit.