Creates, filters, and/or combines pulsar ephemerides database files.
Usage: gtpulsardb psrdbfile outfile filter psrname tstart tstop solareph
One or more pulsar ephemerides database files in either Fermi D4 FITS format, and/or a text format which will be described below.
| |
psrdbfile [file name] |
| |
|
Name of input file containing ephemerides. Multiple files may be combined by listing them in a text file, one per line, and supplying the list file name preceded by an @ sign. |
| |
|
|
| |
outfile [file name] |
| |
|
Name of output file, which will be in Fermi (formerly GLAST) D4 FITS format. |
| |
|
|
| |
filter = NONE [enumerated string (NAME|TIME|SOLAREPH|NONE)] |
| |
|
Type of filtering to be performed. If filter is NAME, the pulsar name will be used to select only ephemerides for the named pulsar. If filter is TIME, the parameters tstart and tstop will be used to filter the ephemerides based on that time range. If filter is SOLAREPH, only ephemerides that match the solareph parameter will be selected. If filter is NONE, no filtering will be performed. |
| |
|
|
| |
psrname = ANY [string] |
| |
|
Name of the pulsar, used to select only ephemerides valid for a particular pulsar. This only has effect when the filter parameter is NAME. |
| |
|
|
| |
tstart = 0. [double] |
| |
|
Time used for the beginning of the interval used for time filtering. This only has effect when the filter parameter is TIME. |
| |
|
|
| |
tstop = 1.e5 [double] |
| |
|
Time used for the end of the interval used for time filtering. This only has effect when the filter parameter is TIME. |
| |
|
|
| |
solareph = JPL DE405 [enumerated string (JPL DE200|JPL DE405)] |
| |
|
Solar system ephemeris used to filter the ephemerides. This only has effect when the filter parameter is SOLAREPH. |
| |
|
|
| |
author = Anonymous User [string] |
| |
|
Name of person responsible for generation of the database being compiled. The name will be recorded in AUTHOR header keyword of the primary extension of the output ephemeris database file. The value is intended to help identify the created file, together with DATE header keyword value, which is the file creation time of the output ephemeris database file that the application automatically computes. It also appears in the creation history recorded in HISTORY header keywords of the primary extension of the output ephemeris database file, in order to help trace back originating ephemeris data. |
| |
|
|
| |
(leapsecfile = DEFAULT) [file name] |
| |
|
Name of the file containing the name of the leap second table, in OGIP-compliant leap second table format. If leapsecfile is the string DEFAULT, the default leap-second file (leapsec.fits), which is distributed with the extFiles package, will be used. |
| |
|
|
| |
(chatter) |
| |
|
This parameter fixes the output verbosity: no screen output (0), nominal screen output (2), maximum verbosity (4). (default: 2) |
| |
|
|
| |
(clobber = yes) |
| |
|
If true, an existing file of the same name will be overwritten. This is a hidden parameter. (default: yes) |
| |
|
|
| |
(debug = no) |
| |
|
Activate debugging mode. (default: no)
When debug is "no", all exceptions that are not caught and handled by individual tool-specific code are caught by a top-level exception handler that displays information about the exception and then exits.
When debug is "yes", such exceptions are not caught by the top level code. Instead the tool produces a segmentation violation, which is more useful for debugging. When debugging mode is enabled, the tool produces more verbose output describing any errors or exceptions that are encountered. |
| |
|
|
| |
(gui = no) |
| |
|
If "yes", the graphical user Interface (GUI) mode is activated.
(default: no) |
| |
|
|
| |
(mode = ql) |
| |
|
Mode of automatic parameters. (default: ql) |