| |
evfile [file] |
| |
|
Input event file. If several events files have to be input, an ASCII file with the complete list of them should be entered here. |
| |
|
|
| |
(evtable = EVENTS) [string] |
| |
|
Event extension name. This is a hidden parameter. (default: EVENTS) |
| |
|
|
| |
scfile [file] |
| |
|
Spacecraft data file containing information such as the spacecraft pointing as a function of time. This file can be generated by gtorbsim for simulated observations, or it can be obtained from the SLAC Data Portal. |
| |
|
|
| |
(sctable = SC_DATA) [string] |
| |
|
Spacecraft data extension. This is a hidden parameter. (default: SC_DATA) |
| |
|
|
| |
outfile [file] |
| |
|
Output file name. The output file is an ASCII file where the initial starting values; the intermediate, as well as the final, values for the best fit position (RA and DEC); and the TS and the circle radius (in decimal degrees) are given. |
| |
|
|
| |
irfs = P6_V3_DIFFUSE [string] |
| |
|
Instrument response functions. |
| |
|
|
| |
expcube = none [file] |
| |
|
FITS file containing livetime as a function of sky position and off-axis angle. This file should be generated by gtltcube. (See gtltcube and gtltcube Help.) |
| |
|
|
| |
expmap = none [file] |
| |
|
Exposure map file used in an unbinned likelihood analysis and created by gtexpmap. (See gtexpmap and gtexpmap Help for further explanation. |
| |
|
|
| |
srcmdl = none [file] |
| |
|
XML file containing the source model definitions. This is the same source model file used by gtlike. (See gtlike and gtlike Help.) The source model could be generated by the Model Editor, or by following source model templates. |
| |
|
|
| |
target [string] |
| |
|
Target source name from srcmdl. This is the name of the source for which the best position will be optimized with gtfindsrc.
If no target source is provided, you will be prompted for the initial coordinates of a putative point source, which will be modeled by a simple power-law. |
| |
|
|
| |
coordsys = CEL <CEL|GAL> [string] |
| |
|
Coordinate system for input of the putative point source.
If you choose CEL, you will be prompted for ra and dec (J2000).
If you choose GAL, you will be prompted for l and b coordinates. |
| |
|
|
| |
ra <-360 - 360> [double] |
| |
|
Initial guess for the source right ascension (decimal degrees).
(default: zero) |
| |
|
|
| |
dec <-90 - 90> [double] |
| |
|
Initial guess for the source declination (decimal degrees).
(default: zero) |
| |
|
|
| |
l <-360 - 360> [double] |
| |
|
Initial guess for the source Galactic longitude (decimal degrees).
(default: zero) |
| |
|
|
| |
b <-90 - 90> [double] |
| |
|
Initial guess for source Galactic latitude (decimal degrees). (default: zero) |
| |
|
|
| |
optimizer = MINUIT <MINUIT|DRMNGB|LBFGS> [string] |
| |
|
Optimizer package to use. (See gtlike and gtlike Help.) Due to the fact that gtfindsrc calls the same routines as gtlike to obtain the TS of the detection at each analyzed position, the optimizer should be the same than the ones used for that tool. (default: MINUIT) |
| |
|
|
| |
ftol = 1e-2 [double] |
| |
|
Fit tolerance. This is the fit tolerance for the likelihood analysis. It is the same parameter used for gtlike. (See gtlike Help.)
(default: 1e-8) |
| |
|
|
Hidden Parameters |
| |
(reopt = yes) [bool] |
| |
|
Refit all free parameters at each candidate point source location. The "free" parameters are the parameters marked as "free" in the source model file, and are the ones to be fitted in the likelihood analysis. (See gtlike Help.) This is a hidden parameter. (default: yes) |
| |
|
|
| |
atol = 0.01 [double] |
| |
|
Convergence tolerance for positional fit. [default:
0.001 (decimal degrees)] |
| |
|
|
| |
(toltype = ABS) |
| |
|
Fit tolerance convergence type (absolute vs relative). |
| |
|
|
| |
|
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. |