Enhance meta-data #23
Comments
|
An email from Bob McGuire at GSFC. Some of the changes have been made, but not all. Warren: Let me take one CDF as an example and illustrate the kind of changes I'd suggest making (if you have agree/have time). At random (more or less), I picked the series of CDFs including bar118_1A_2_l2_fspc_20130208_v01.cdf. Dumping the global metadata in our .skt file format gives "File_naming_convention" "Data_type" 1: CDF_CHAR { "Fast_X-Ray_Spectra" } . "Logical_source_description" "Mission_group" 1: CDF_CHAR { "RBSP" } . "PI_affiliation" 1: CDF_CHAR { "Dartmouth College" } . "Source_name" 1: CDF_CHAR { "Payload_ID" } . "Project" 1: CDF_CHAR { "LWS>Living With a " - "PI_name" 1: CDF_CHAR { "Robyn Millan" } . "Data_version" 1: CDF_CHAR { "1" } . "TEXT" 1: CDF_CHAR { "Four channels of fast " - "Instrument_type" 1: CDF_CHAR { "Gamma and X-Rays" } . "Descriptor" 1: CDF_CHAR { "Scintillator" } . "Discipline" 1: CDF_CHAR { "Space " - "Acknowledgement" . "LINK_TITLE" . "Generated_by" 1: CDF_CHAR { "barrel.ssl.berkeley.edu" } . "Rules_of_use" . "Generation_date" 1: CDF_CHAR { "yymmdd" } . "HTTP_LINK" . "LINK_TEXT" . "MODS" . "Time_resolution" 1: CDF_CHAR { "20Hz" } . "ADID_ref" . "Logical_source" 1: CDF_CHAR { "payload_id_fast_x-ray_spec" - "Logical_file_id" 1: CDF_CHAR { "payload_id_fast_x-ray_spec" - A revised set of values might instead be "File_naming_convention" "Data_type" 1: CDF_CHAR { "l2>Level-2" } . "Logical_source_description" "Mission_group" 1: CDF_CHAR { "BARREL" } . "PI_affiliation" 1: CDF_CHAR { "Dartmouth College" } . "Source_name" 1: CDF_CHAR { "bar118_1a_2" } . "Project" 1: CDF_CHAR { "LWS>Living With a " - "PI_name" 1: CDF_CHAR { "Robyn Millan" } . "Data_version" 1: CDF_CHAR { "1" } . "TEXT" 1: CDF_CHAR { "Four channels of fast " - "Instrument_type" 1: CDF_CHAR { "Gamma and X-Rays" } . "Descriptor" 1: CDF_CHAR { "fspc>Fast x-ray SPeCtra" } . "Discipline" 1: CDF_CHAR { "Space " - "Acknowledgement" . "Generated_by" 1: CDF_CHAR { "barrel.ssl.berkeley.edu" } . "Rules_of_use" . "Generation_date" 1: CDF_CHAR { " VALUE SHOULD BE FILLED IN" } . "LINK_TITLE" 1: CDF_CHAR { "BARREL" } . "HTTP_LINK" 1: CDF_CHAR { "http://barrel.ssl.berkeley.edu" } . "LINK_TEXT" 1: CDF_CHAR { "home page with descriptions and additional data/plots" } . "MODS" . "Time_resolution" 1: CDF_CHAR { "20Hz" } . "ADID_ref" . "Logical_source" 1: CDF_CHAR { "bar118_1a_2_l2_fspc" } . "Logical_file_id" 1: CDF_CHAR { "bar118_1a_2_l2_fspc_20130208_" - In addition, the CATDESC values (and possibly the LABLAXIS) values for LC1 etc. aren't very informative. What energy ranges are involved for each light curve channel, can you give any clue as to where the instrument is looking (solar x-rays, ionospheric/auroral x-rays, all-hemisphere integration) etc.? I know there will be documentation to go with these data, but it's good to describe the data to some level of usability in the data files. Similar changes and comments probably apply to all the CDFs. |
|
Problem with min/max values in housekeeping file. |
|
Fix the following CATDESC fields: |
|
"Payload_ID" |
|
Logical Source Name "payload_id_l2_scintillator " |
|
Change formats to FORTRAN style. |
|
Mag data: Specify balloon coordinates in CATDESC, (change B_X/Y/Z) |
No description provided.
The text was updated successfully, but these errors were encountered: