Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • New ScaleFactor class: This is a decorator class that layers an additional overall scale factor to the spectral model function, in addition to the usual normalization parameter. To use, prepend the qualifier "ScaleFactor" to the function name in the xml definition and add a ScaleFactor parameter, e.g.,
    <spectrum type="ScaleFactor::PowerLaw2">
    <parameter free="1" max="1000.0" min="1e-05" name="Integral" scale="1e-06" value="1.0"/>
    <parameter free="1" max="-1.0" min="-5.0" name="Index" scale="1.0" value="-2.0"/>
    <parameter free="0" max="200000.0" min="20.0" name="LowerLimit" scale="1.0" value="20.0"/>
    <parameter free="0" max="1000000.0" min="20.0" name="UpperLimit" scale="1.0" value="1e6"/>
    <parameter free="1" max="10" min="0." name="ScaleFactor" scale="1.0" value="1"/>
    </spectrum>
  • Implemented changes to allow use of unbinned analysis with extended source templates
    • Enabled map-based integration for Npred using the source map pixels in unbinned analysis. This will circumvent the normal integration, which uses the exposure map pixels, only for map-based sources.
    • Enabled the map-based diffuse response calculation. This will circumvent the theta-phi integral only for map-based diffuse sources.
    • Enabled map-based Npred and diffuse response integrals to be specified in the xml definition for a source via the "map_based_integral" attribute:
      <source name="W44_mapIntegral" type="DiffuseSource">
      <spectrum type="PowerLaw2">
      <parameter free="1" max="1000.0" min="0.0" name="Integral" scale="1e-5" value="1.0"/>
      <parameter free="1" max="-1.0" min="-5.0" name="Index" scale="1.0" value="-2.1"/>
      <parameter free="0" max="200000.0" min="20.0" name="LowerLimit" scale="1.0" value="20.0"/>
      <parameter free="0" max="600000.0" min="20.0" name="UpperLimit" scale="1.0" value="600000.0"/>
      </spectrum>
      <spatialModel file="W44.fits" type="SpatialMap" map_based_integral="true">
      <parameter free="0" max="1000.0" min="0.001" name="Prefactor" scale="1.0" value="1.0"/>
      </spatialModel>
      </source>
      The environment variable mechanism from Likelihood-17-21-04 still works, but this method allows the map-based integration to be activated on a source-by-source basis.
      To avoid the map-based integration, simply omit the attribute:
      <source name="W44" type="DiffuseSource">
      <spectrum type="PowerLaw2">
      <parameter free="1" max="1000.0" min="0.0" name="Integral" scale="1e-5" value="1.0"/>
      <parameter free="1" max="-1.0" min="-5.0" name="Index" scale="1.0" value="-2.1"/>
      <parameter free="0" max="200000.0" min="20.0" name="LowerLimit" scale="1.0" value="20.0"/>
      <parameter free="0" max="600000.0" min="20.0" name="UpperLimit" scale="1.0" value="600000.0"/>
      </spectrum>
      <spatialModel file="W44.fits" type="SpatialMap">
      <parameter free="0" max="1000.0" min="0.001" name="Prefactor" scale="1.0" value="1.0"/>
      </spatialModel>
      </source>
      This allows for backwards-compatibility with older XML model definitions.
    • Page: http://fermi.gsfc.nasa.gov/ssc/data/analysis/scitools/likelihood_tutorial.htmlImage Removed
    • Page: http://fermi.gsfc.nasa.gov/ssc/data/analysis/scitools/python_tutorial.htmlImage Removed
    • Page: http://fermi.gsfc.nasa.gov/ssc/data/analysis/scitools/extended/extended.htmlImage Removed
    • Page: http://fermi.gsfc.nasa.gov/ssc/data/analysis/scitools/xml_model_defs.htmlImage Removed
    • WHICH HELPFILES WILL THIS CHANGE?
  • Use DSS keyword info on the CONVERSION_TYPE selection by gtselect to determine whether front, back (or both) should be used in exposure calculations. This means that the irfs keyword need not be specified with the ::FRONT, ::BACK qualifiers when running gtexpmap, gtdiffrsp, gtlike, or the pyLikelihood module. The only exception is when running gtexpcube2 with ccube=none. In this case, the DSS keyword info is not available from any of the inputs, and the qualifiers must be added, e.g., gtexpcube2 ccube=none irfs=P7SOURCE_V6::FRONT.
    • Elizabeth suggests not modifying the documentation for this change. Using gtexpcube2 in the way we recommend would require entering the IRF name differently than for other tools. However, using the ::FRONT and ::BACK nomenclature elsewhere (hopefully) does not cause issues. Better to be consistent across the tools in the documentation.

gtobsim

Pulsar Tools

...

  • Output format change: Use RATE instead of COUNTS for the background spectrum inferred from an unbinned likelihood analysis so that real values (rather than integers) can be used. Also, fill the STAT_ERR column with the model error estimate on the predicted rate.

Other