| |
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, for real observations, it can be obtained from the SLAC Data Portal. |
| |
|
|
| |
(sctable = SC_DATA)
[string] |
| |
|
Spacecraft data extension. This is a hidden parameter. (default: SC_DATA) |
| |
|
|
| |
filter [ = DATA_QUAL==1 && LAT_CONFIG==1 && ABS(ROCK_ANGLE)<52 ] [string] |
| |
|
This is the filter expression. The cuts are make using C-style relational syntax; for example: ! (not), && (and), || (or), !=(different), >, <, >=, <=, abs(), cos(), sin(), etc.. This string will be anded verbatim to the time selection string and the optional zenith angle-based ROI cut, e.g., if "DATA_QUAL==0 || IN_SAA!=T" is the specified filter string, then "DATA_QUAL || IN_SAA!=T && (START >= tstart) && (STOP <= tstop)" would be the filter applied to the FT2 file when creating the GTIs. The user will need to add parentheses explicity in order to group the components of the input filter string that is anded with the default strings. |
| |
|
|
| |
roicut [= yes]
[bool] |
| |
|
Apply ROI-based zenith angle cut to exclude times where the region of interest is outside the field of view.
If "yes", then the code will construct a filter string expression of the form: angsep(RA_ZENITH,DEC_ZENITH,RA_ROI,DEC_ROI) < ZENMAX–ROI_RADIUS
This expression will be "and"-ed it with the filter expression provided by the user. The zenith angle cut and acceptance cone information used in this expression are read from the DSS keywords in the EVENTS header of the input FT1 file. These keywords are written by gtselect when the selections are made. If the required DSS keywords are missing, a warning message is printed and no additional filter string is applied. |
| |
|
|
| |
evfile
[file] |
| |
|
Input event file; contains the event data. This file can be obtained from the SLAC Data Portal. |
| |
|
|
| |
(evtable = EVENTS)
[string] |
| |
|
Event table extension name. This is a hidden parameter. (default: EVENTS) |
| |
|
|
| |
outfile
[file] |
| |
|
Output event FITS file name. |
| |
|
|
| |
(apply_filter = yes)
[bool] |
| |
|
Flag to apply GTI filter to event data. This is a hidden
parameter.
(default: yes) Set this to
"no" for non-FT1 files. |
| |
|
|
| |
(overwrite = no)
[bool] |
| |
|
Build the GTIs from scratch, overwriting the existing GTI extension. This is a hidden parameter. By default, the new GTIs will be merged with any existing GTIs in the file. By setting this option to "yes", the old GTI extension will be ignored. |
| |
|
|
| |
(header_obstimes =
yes) [bool] |
| |
|
Use the FITS table header values for TSTART and TSTOP.
This is a
hidden parameter. This option is only relevant if "overwrite=yes", otherwise it is
ignored. |
| |
|
|
| |
(tstart = 0)
[double] |
| |
|
Observation start time Mission Elapsed Time (MET) seconds. The reference time used for MET is midnight (0h:0m:0s) on January 1, 2001, in Coordinated Universal Time (UTC). The Fermi convention is that MJDREF=51910 (UTC)=51910.0007428703703703703 (TT); the fractional part of MJDREF in the TT system compensates for the use of midnight in the UTC system as the reference time.
MJDREF is divided into two keywords: MJDREFI=51910, the integer part; and MJDREFF=7.428703703703703D-4, the fractional part. This is a hidden parameter. This option is only relevant if "header_obstimes=no". The DATE-OBS and TSTART header keywords and earliest GTI start time will
be modified to be consistent with this value. |
| |
|
|
| |
(tstop = 0)
[double] |
| |
|
Observation stop time (MET seconds.) This option is
only relevant if "header_obstimes=no". The DATE-END and TSTOP header
keywords and latest GTI start time will be modified to be consistent
with this value. |
| |
|
|
| |
(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. (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) |
| |
|
|