gtexpmap

See gtexpmap:

Help | Examples

Also see:

Synopsis:

Calculates exposure maps for unbinned analysis.

This tool creates exposure maps that are needed to compute the predicted number of photons within a given Region-of-Interest (ROI) for diffuse components in your source model.

Usage: gtexpmap evfile scfile expcube outfile irfs srcrad nlong nlat nenergies

Links:

General Parameters

  evfile [file]
    Input event data file in FITS format. Typically, this file will have been created with the gtselect tool.
     
  (evtable = EVENTS) [string]
    Event table 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)
     
  expcube [file]
    FITS file containing livetime as a function of sky position and off-axis angle. This file should be generated by gtltcube. If no livetime cube file is provided, gtexpmap will integrate the livetimes directly from the spacecraft file.
     
  outfile [file]
    Output FITS file name containing the exposure map used in unbinned likelihood analysis.
     
  irfs = P6_V3_DIFFUSE [string]
    The instrument response (PSF, effective area, energy resolution) as a function of energy, inclination angle (the angle between the source and the LAT normal), and photon event class. Since the LAT usually surveys the sky, a source is observed at various inclination angles. Each count will therefore be effectively characterized by a different instrument response function (IRF)
     
  srcrad = 30 [double]
    Radius of source model region (degrees). The center of the source region is obtained from the Data Sub-Space DSS keywords defining the Region-of-Interest in the event file.
     
  nlong = 120 <2-1000> [int]
    Number of longitude points. Half-degree pixels are a nominal choice for gtexpmap. That means nlong=120 and nlat=120 if 30 degrees radius was chosen for the srcrad parameter.
     
  nlat = 120 <2-1000> [int]
    Number of latitude points. Half-degree pixels are a nominal choice for gtexpmap. That means nlong=120 and nlat=120 if 30 degrees radius was chosen for the srcrad parameter.
     
  nenergies = 20 <2-100> [int]
    The number of energy bands to consider. Minimum and maximum energies are obtained from the DSS keywords. The number of energies for your grid depends on complexity of the spectra of the diffuse components, but 4 to 5 per decade are usually sufficient.
     

Hidden Parameters

  (submap = no) [bool]
   

This parameter allows you to compute a submap. This is a hidden parameter. (default: no)

If "yes", this feature was intended to allow for parallelization of the gtexpmap computation for a given geometry. You can set the application to run in parallel on different regions of the overall map and then add the resulting FITS
images together using standard FTOOLS. The user should be careful to define the submaps so that they do not overlap or leave gaps.

     
  (nlongmin [int])
    Minimum longitude index for submap. This is a hidden parameter.
     
  (nlongmax [int])
    Maximum longitude index for submap. This is a hidden parameter.
     
  (nlatmin [int])
    Minimum latitude index for submap. This is a hidden parameter.
     
  (nlatmax [int])
    Maximum latitude index for submap. This is a hidden param
     
  (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)
     

Owned by: J. Chiang

Last updated by: Chuck Patterson 01/19/2011