You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

I have added a new system test to provide feedback on overlay simulations.

This page summarizes details of the test and initial release comparisons.
Please comment below to recommend changes and additions. See the suggested new histogram list.

Overlay System Test Configuration

As a starting point, the overlay test (AllGammaOverlay) is run exactly like the system test AllGamma sample with the following exceptions:

  • default overlay job options are included, 
    #include "$OVERLAYROOT/src/MergeAlgs/Overlay.txt";
  • overlay XML input location is specified, 
    OverlayInputSvc.InputXmlFilePath = "path_to_Leon's_latest_overlay_files";
  • RootIo option to avoid memory leak, 
    RootIoSvc.RebuildIndex = false;
  • orbit inclination set, but probably not important for systests? 
    FluxSvc.OrbitInclination = 25.8;

See the note below about the general system test job options.

It produces the same output histograms as AllGamma, although we should probably add some things. My short list is below.

Right now the overlay input files are selected by setting an environment variable.
The overlay event format changes a bit with the releases requiring updates to the file location. Here is what I am using, but I think there may be additional access options.

GR v17r7: Overlay_path=/nfs/farm/g/glast/u31/lsrea/McIlwainL/5-Feb-2009/
GR v17r10: Overlay_path=/nfs/farm/g/glast/u31/lsrea/McIlwainL/18-Mar-2009/

Overlay Comparisons

I rigged a direct comparison for the overlay vs non-overlay for GR v17r7.
The GRv17r7 run includes outputs for the AllGammaOverlay test with the overlays disabled (exactly the same as normal AllGamma). The run GR v17r7OVRLY has overlays turned on. This is just to easily see the comparison of AllGamma against AllGammaOverlay.
See the failed plots

Note that one thing I am trying to confirm is that the system tests are actually providing a sensible test of the overlays. There are a few differences from the validation runs. I'm not sure if there should be some configuration changes for the overlay test.

In general, there are more digis and less 0's for all the subsystems. Energies are shifted a bit higher. More triggers and more vetoes. These are not surprises.

There are odd outliers for TkrDigiLayer and TkrDigiTower. I'm not sure what should be special in the overlays for Layers 7 and 17 or Towers 0 and 8? Maybe this is just the calibration mismatch? The overlays are derived from data, but the system tests use ideal calibrations.

I also ran tests for GRv17r10 and GRv17r13.
The overall level of digis is reduced. The layer and tower outliers are still there.

Miscellanea

System Test Job Options

The system tests (circa GR v17) are run using the standard Gleam job options, $GLEAMROOT/src/basicOptions.txt, with only a couple notable additions:

  • TriggerAlg.applyPrescales = false
  • Test specific flux library and source

The system tests do not pick up calibrations from the database and default to ideal calibrations, i.e. calibration flavor = "ideal".

Suggested New Hists for Overlay Test

I picked out some items based on new merit ghost/overlay merit variables. Please add other parameters of interest (or even better, code).

  • Ghosts in the Tracker
    • TkrNumGhosts
    • TkrNumToT255s
    • TkrNumWideClusters
    • TkrNumWiderClusters
    • TkrNumGhostsOnTracks
    • TkrNumToT255sOnTracks
    • anything else?
  • Overlay event info
    • Overlay event trigger bits
    • Overlay PtMcIlwainL (or PtLambda?)
    • anything else?
  • No labels