Working with TLE-AUX

Data formats, HDF5, XML profiles, etc.

Working with TLE-AUX

Postby markgreenman » Wed Feb 08, 2012 2:56 pm

If I run ADL_Unpacker on H5 TLE products, it produces a file set per input H5 like:

TLE-AUX_npp_20120109162801Z_20120109000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.msd
TLE-AUX_npp_20120109162801Z_20120109000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.msd.CMP_FILENAME

the .msd file looks like a standard ASCII TLE. I see from the slides from the January 18-19 ADL workshop, presentation 'ADL 3.1 Workshop: Tools Demo' that since this is an Auxiliary Data, the ADL_Unpacker does an 'Unwrap'.

The Conversion to TLE-AUX-Int outlined on Page 33 of the presentation 'Running the CrIMSS Chain' is straightforward, add a space to each line in the '.msd' file.

1) What should the resulting naming pattern be for the TLE-AUX-Int file created?
2) The example copied an existing Metadata .asc file and edited it. What metadata fields should be updated, and to what should their values be set? For example, how is the 'Effectivity' time range determined for a given input TLE?

thanks,
Mark
Mark Greenman Computer Scientist IV
Space Dynamics Laboratory mark.greenman@sdl.usu.edu
1695 N Research Park Way 435.713.3336 T,W,F (SDL Office)
North Logan, UT 84341
markgreenman
 
Posts: 9
Joined: Wed Jan 19, 2011 2:41 pm

Re: Working with TLE-AUX

Postby kbisanz » Thu Feb 09, 2012 5:49 pm

The AUX file naming convention is specified in the CDFCB-X, Volume 1, Table 3.4.4-1.

Basically, you can copy "TLE-AUX_npp_20120109162801Z_20120109000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.msd", put a URID on the front, and replace "msd" with "txt_Internal". So it'd be "URID.TLE-AUX_npp_20120109162801Z_20120109000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.txt_Internal". You can use $ADL_HOME/tools/bin/UridCreator.exe to create a new URID.

Effectivity is taken from the file name. In your example of "TLE-AUX_npp_20120109162801Z_20120109000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.msd" :
--"20120109162801Z" is the Production Timestamp (2012-01-09 16:28:01Z)
--"20120109000000Z" is the Effectivity Start
--"ee00000000000000Z" is the Effectivity Stop (the "ee00000000000000Z" means the maximum IET time, which is 2038-01-19 03:14:07.000000. (See http://en.wikipedia.org/wiki/Year_2038_problem for a reason for that date)

The other time fields (RangeDateTime and ObservedDateTime) I would just leave as in the example I posted to your thread titled "CmnGEO-Anomaly-TLE" ("2000-05-18 14:00:30.000000" "2038-01-19 03:14:07.000000").
Kevin Bisanz
Raytheon Company
kbisanz
 
Posts: 280
Joined: Wed Jan 05, 2011 7:02 pm
Location: Omaha NE

Re: Working with TLE-AUX

Postby markgreenman » Thu Feb 09, 2012 5:59 pm

Thanks Kevin. This was consistent with what I was expecting/doing. Just wanted to ensure I was treating them correctly.
Mark Greenman Computer Scientist IV
Space Dynamics Laboratory mark.greenman@sdl.usu.edu
1695 N Research Park Way 435.713.3336 T,W,F (SDL Office)
North Logan, UT 84341
markgreenman
 
Posts: 9
Joined: Wed Jan 19, 2011 2:41 pm


Return to Input and Output

Who is online

Users browsing this forum: No registered users and 2 guests

cron