Project

General

Profile

Feature #1385

Validation of Batch Reconstruction

Added by Rogers, Chris almost 8 years ago. Updated almost 8 years ago.

Status:
Open
Priority:
Normal
Assignee:
Category:
bin(aries)
Target version:
Start date:
05 December 2013
Due date:
% Done:

0%

Estimated time:
Workflow:
New Issue

Description

Need a script to validate a reconstruction job:-

  • Calculate efficiencies
  • Compare with expected efficiencies
  • Raise a flag if values go out of range

Because the sorts of analyses people will want to do are many and varied, we need to raise many and varied flags indicating e.g. if this detector or that detector has a problem. Propose the following efficiencies as checks. It is, I suggest, beyond the scope of this analysis to cross-check with magnet currents. So if e.g. D2 is off, we will raise a flag on TOF0 rates (and the rest) nonetheless...

Trigger
-------
  • Some checks against the scalars?
  • Triggers vs CDB triggers (generated during data taking)
  • Triggers vs space points in the triggering detector (which could be TOF0 or TOF1)
Global
------
  • Space points vs Triggers in TOFs
  • Tracker tracks vs TOF2 space points
  • TOF2 trigger rate vs EMR tracks
  • Global tracks vs all detector tracks and spacepoints, as appropriate

For the detectors we just walk up the reconstruction tree and look at efficiencies:

TOFs
----
  • Space points vs Slab Hits vs Digits in TOFs
Ckov
----
  • A low momentum beam won't trigger Ckov - so probably I can't see how we can do a low level check of whether Ckov was working
Tracker
-------
  • Tracks vs space points vs clusters vs digits

KL
--

EMR
---
  • ADC hits vs TDC hits plane by plane

Files

efficiency.tar.gz (484 KB) efficiency.tar.gz Rogers, Chris, 05 December 2013 07:07
#1

Updated by Rogers, Chris almost 8 years ago

Added tarball containing the calculation script that I used for the MICE CM (and some sample output data and plots)

Also available in: Atom PDF