Page History

...

• default overlay job options are included,

  No Format
  #include "$OVERLAYROOT/src/MergeAlgs/Overlay.txt";

• overlay XML input location is specified,

  No Format
  OverlayInputSvc.InputXmlFilePath = "path_to_Leon's_latest_overlay_files";

• RootIo option to avoid memory leak,

  No Format
  RootIoSvc.RebuildIndex = false;

• orbit inclination set, but probably not important relevant for systests ? (thrown in detector coords)

  No Format
  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 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/

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

It produces the same output histograms as AllGamma for now. Probably some things should be added. My short list is below.

Overlay Comparisons

I rigged a direct comparison for the overlay vs non-overlay First, is to do a baseline comparison of the overlay and non-overlay versions. I rigged a direct comparison through the systest interface for GR v17r7.
The GRv17r7 run includes outputs for GR v17r7 run shows 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 allows an easy comparison of AllGamma against AllGammaOverlay.
See the failed plots.

Note that one 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.overlay test is working properly. For example, is it okay to run these with ideal calibrations? Any other configuration issues?

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 very noticeable outliers for in the TkrDigiLayer and TkrDigiTower plots. 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 a 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.

A secondary item is if the overlay test is sufficient at the system test level. Do we want additional tests for specific energies or magnetic latitudes?

Miscellanea

...

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

• TriggerAlg.applyPrescales = falseTest 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".

Another item of note: The default Geant 4 physics model in the basic options is "GLAST". The preferred model is now QGSP_BERT, which includes the updated LPM effect.

Suggested New

...

Histograms 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).

...