| |
srcmaps [file] |
| |
|
FITS file of individual source model components that
have been convolved through the instrument response using gtsrcmaps |
| |
|
|
| |
srcmdl [file] |
| |
|
XML file containing the source model definitions. The format of this file is the same used by gtlike. The source model could be generated by the ModelEditor utility (recommended), or by following the source model templates. (See Model Editor.) |
| |
|
|
| |
outfile [file] |
| |
|
Name of the output FITS file that will contain the generated counts map. |
| |
|
|
| |
irfs = P6_V3_DIFFUSE [string] |
| |
|
The instrument response (PSF, effective area, energy resolution) is currently a function of energy, inclination angle (the angle between the source and the LAT normal), and photon event class. Since the LAT will usually survey the sky, a source will be observed at different inclination angles. Each count will therefore be characterized by a different instrument response function (IRF). |
| |
|
|
| |
expcube [file] |
| |
|
Exposure cube. |
| |
|
|
| |
bexpmap = none [file] |
| |
|
Binned exposure map. |
Hidden Parameters |
| |
(convol = yes) [bool] |
| |
|
Perform the convolution of the model maps with the psf.
This applies only for on-the-fly source map calculations. |
| |
|
|
| |
(resample = yes) [bool] |
| |
|
Resample input counts map for convolution. |
| |
|
|
| |
rfactor = 2 |
| |
|
Resampling factor. |
| |
|
|
|
(outtype = ccube) <CCube|CMAP> |
|
|
Enables gtmodel to write ccube maps with geometry and energy planes matching the input source map file.
To write a counts cube instead of a summed counts map, specify the outtype parameter at the command line. |
| |
|
|
| |
(chatter = 2) |
| |
|
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. |
| |
|
|
| |
(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.
|
| |
|
|
| |
(gui = no) |
| |
|
If the parameter specified is "yes", the Graphical User Interface (GUI) mode is activated. This is a hidden parameter. (default: no) |
| |
|
|
| |
(mode = ql) |
| |
|
Mode of automatic parameters. This is a hidden parameter. (default: ql) |
| |
|
|