2384
Comment:
|
3038
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
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. | Level 0.3 and Level 0.5 data are very similar. 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. |
Line 7: | Line 7: |
Sources for the Level 0.3/0.5 data include: | === Sources for the Level 0.3/0.5 data include: === |
Line 13: | Line 13: |
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. (Art) No need for an intermediate series with interpolated/converted data. 1. 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. 2. The script/module to ingest into sdo.hk_dayfile must be created. 6. Needs a sdo.asdp - Contains all the ancillary science data packet information (apid 129) (Jennifer). |
=== 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. * The master LZP MOC server download script, mocDlLzp.csh (JSOC/proj/lev0/scripts/mocserver), downloads files to /surge, and then calls script to ingest into sdo.hk_dayfile. * The script/module to ingest into sdo.hk_dayfile * Needs a sdo.asdp - Contains all the ancillary science data packet information (apid 129). |
Line 39: | Line 36: |
7. Need a master lev 0.3 record creation module. It calls modules like getfdsorbit. | * Need a master lev 0.3 record creation module. It calls modules like getfdsorbit. * sdo_get_pointing: a function to query the pointing data from the ancillary science data packet and return spacecraft pointing data in the co-ordinate system of the user's choice * sdo_telem_processing: a statistics function performed on housekeeping data. This function will take in a parameter file, an input series and a type of statistical process to be performed, and a destination series. The input parameter file would contain three columns: source keyword, operation to be performed, and destination keyword. . A parameter file example: || source keyword || operation || destination keyword || || oventemp || m || ov_avg || || oventemp || rms || ov_r || || oventemp || min || ov_min || |
Level 0.3 / Level 0.5 Data
Level 0.3 and Level 0.5 data are very similar. 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.
- The master LZP MOC server download script, mocDlLzp.csh (JSOC/proj/lev0/scripts/mocserver), downloads files to /surge, and then calls script to ingest into sdo.hk_dayfile.
- The script/module to ingest into sdo.hk_dayfile
- Needs a sdo.asdp - Contains all the ancillary science data packet information (apid 129).
- 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.
- sdo_get_pointing: a function to query the pointing data from the ancillary science data packet and return spacecraft pointing data in the co-ordinate system of the user's choice
- sdo_telem_processing: a statistics function performed on housekeeping data. This function will take in a parameter file, an input series and a type of statistical process to be performed, and a destination series. The input parameter file would contain three columns: source keyword, operation to be performed, and destination keyword.
- A parameter file example:
source keyword |
operation |
destination keyword |
oventemp |
m |
ov_avg |
oventemp |
rms |
ov_r |
oventemp |
min |
ov_min |