| |
evfile [file] |
| |
|
Input photon file. |
| |
|
|
| |
(evtable = EVENTS) [string] |
| |
|
Event data extension. This is a hidden parameter. |
| |
|
|
| |
scfile [file] |
| |
|
Spacecraft data file.
Contains information such as the spacecraft pointing as a function of time. |
| |
|
|
| |
(sctable = SC_DATA) [string] |
| |
|
Spacecraft data extension. This is a hidden parameter. |
| |
|
|
| |
outfile [file] |
| |
|
Output filename.
The output photon file with columns added for each source containing the probabilities. |
| |
|
|
| |
srcmdl [file] |
| |
|
XML file containing the source model definitions.
This is the source model file used by gtlike or the pyLikelihood python tools. |
| |
|
|
| |
irfs = P6_V3_DIFFUSE [string] |
| |
|
Instrument response functions.
The instrument response (consisting of the PSF, effective area, and energy dispersion) is a function of energy, inclination angle (the angle between the source and the LAT normal), and event category. Since the LAT usually surveys the sky, a source is observed at various inclination angles. Each count is therefore characterized by a different instrument response function (IRF). |
Hidden Parameters |
| |
(srclist = none) [file] |
| |
|
ASCII list of sources to include in the output.
When set to "none", probabilities for all sources in the XML file are included in the output. If the user is only interested in a subset of those sources then, in order to save space on output and execution time, that subset may be specified via this file. Each source should be listed on a separate line. |
| |
|
|
| |
(chatter = 2) |
| |
|
This parameter fixes the output verbosity: no screen output (0), nominal screen output (2), maximum verbosity (4). (default: 2) |
| |
|
|
| |
(clobber = yes) |
| |
|
Overwrite or do not overwrite existing output files. This is a hidden parameter. (default: yes) |
| |
|
|
| |
(debug = no) |
| |
|
Activate debugging mode. This is a hidden parameter. (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.
|
| |
|
|
| |
(mode = ql) |
| |
|
Mode of automatic parameters. This is a hidden parameter. (default: ql) |
| |
|
|