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