The Galileo Energetic Particles Detector
Galileo EPD Handbook
Appendices
Appendix E. EPD File Structure
Table of Contents:
- Description of EPD File Header Record (below; please scroll down)
- Record Header
- Rate Block
- CMS PHA Block
- LEMMS PHA Block
- Rate Calc Block
- Binned Rate Averages
1. Description of EPD File Header Record
Source: T. P. Armstrong, March 1985
This record will be present at the beginning of all Galileo EPD sequential files which are written by the EPD processor or average processor. The purpose of this record is to carry along the descriptive information about the run. This information is obtained in several ways:
- From the system via calls to DATE.
- From the operator by echoing all operator responses to program prompts to a file.
- From the program and the input data set as a result of the run.
When EPD runs in a mode of writing its output file to disc, the file header record can easily be written into the first position on the data set. However, when END is writing a magnetic tape, it must first write a "dummy record" to hold the space at the beginning of the files for the file header record. When the run has completed successfully and the information needed for the file header record is available, END will rewind the tape and write the file header record in the first position. The record lengths must be carefully controlled in order to avoid overwriting into the second record or leaving an unerased fragment of the "dummy record" which would confuse and cause tape errors on subsequent attempts to read the output file.
The items which are included in the file header are:
- Program name
- Operator name
- Input file label
- Output file label
- Production date to begin run
- Production date to end run
- Input file start time
- Input file end time
- Input file number of time discontinuities
- Input file number of overlapping records
- Input file gap time--amount of missing time.
- Input file overlap time--amount of duplicate time.
- Input file number of successful reads.
- Input file number of unsuccessful (skipped) reads.
- Output file start time
- Output file end time
- Output file number of rate blocks
- Output file number of CMS PHA blocks
- Output file number of LEMMS PHA blocks
- Output file number of RATE CALC blocks
- Echo of program/operator interaction (ASCII)
Next: 2. Record Header
Return to Galileo EPD Handbook Table of Contents Page.
Return to main
Galileo Table of Contents Page.
Return to Fundamental
Technologies Home Page.
Updated 8/23/19, Cameron Crane
QUICK FACTS
Mission Duration: Galileo was planned to have a mission duration of around 8 years, but was kept in operation for 13 years, 11 months, and 3 days, until it was destroyed in a controlled impact with Jupiter on September 21, 2003.
Destination: Galileo's destination was Jupiter and its moons, which it orbitted for 7 years, 9 months, and 13 days.