Name Template: PUB/MISSION/level1b/atmObj/YYYY.DDD/atmObj_IIII.YYYY.DDD.HH.MM.GGG_SSSS.VVVV_pl
| DDD | Day of year |
| GGG | GNSS id (G28 = GPS satellite 28) |
| HH | Hour |
| IIII | Mission ID (CHAM, SACC, CO01-06, GPSM, etc) |
| LLL | LEO number (1-6 for COSMIC) |
| MISSION | Mission ID (eight characters or less--champ, champrt, sacc, sacctst, etc) |
| MM | Minute |
| PUB | Base directory for the pub hierarchy |
| SSSS | Subtype (an ID which tells the command options used in generating this file) |
| VVVV | Version (an ID which tells the version of all codes using in generating thie file) |
| YYYY | Year |
Atmospheric occultation object file. Contains file names
of all files needed
to process an atmospheric occultation (excess phase + inversion).
At least the following variables will be defined in each occ object:
$startTime # The start time of the occultation in GPS seconds
$endTime # The end time of the occultation in GPS seconds
$setting # True if this is a setting occultation
$occPrn # The GPS PRN number of the occulting satellite
$refPrn # The GPS PRN number of the reference satellite
$clockfile # The full path of the GPS clock offset file to use
$leoPodfile # The full path of the LEO orbit file (in Berne STD format)
$gpsPodfile # The full path of the GPS orbit file (in SP3 format)
@hrfiles # The full paths of all high rate data files needed to process
# this occulation
The file is in the form of a perl snippet, which can be read in from perl like so:
package whatever;
my $atmObj = shift; # read atmObj file in from command line
package parms;
require $atmObj;
package whatever;
# Now file names in $atmObj can be referred to like this:
my $infile = $parms::filename;
|
