Difference: Data (1 vs. 2)

Revision 22010-08-16 - AlbertoOliva

Line: 1 to 1
 
META TOPICPARENT name="AmsTracker"

Data Quality Check

Line: 19 to 19
 Monitor.png

For the test beam purposes several other plots are produced please check them.

Deleted:
<
<

Data Quality Check of Many Blocks:

The hmon files can be joined via hadd: hadd hmon-sum.root hmon1.root hmon2.root

or via the scripts mergeblocks.sh and LastHMon.sh (they are in the ~/TrackerUser/Monitor/ dir) (LastHMon.sh needs to be launched two times with parameters 'LastHMon.sh 1' and 'LastHMon.sh 2']. If this two scripts are on, you can use:

  • LastBlockHmon.root: last hmon produced by decoding (created by 'LastHMon.sh 1')
  • Last3BlocksHmon.root: last 3 hmon produced by decoding added (created by 'LastHMon.sh 1')
  • Last5BlocksHmon.root: last 5 hmon produced by decoding added (created by 'LastHMon.sh 1')
  • Last10BlocksHmon.root: last 10 hmon produced by decoding added (created by 'LastHMon.sh 2')
  • LastRunHmon.root: last hmon produced by decoding, belonging to the same run (same RunId) added (created by 'LastHMon.sh 2')
  • incrhmon.root: sum of all blocks starting from the one indicated in the script mergeblocks.sh

A typical application is to us:

  • MonitorUI Output/incrhmon.root
  • MonitorUI Output/LastBlockHmon.root

and making updates every 30 secons.

and

  • MonitorUI Output/LastCalDB.root (created by LastHMon.sh 1)

Revision 12010-08-16 - AlbertoOliva

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AmsTracker"

Data Quality Check

The Output/*_ErrReport.txt files are a very compact source of information. Please check there the event size, trigger rate, track reconstruction rate, presence of errors.

Instead you can open the files Output/*_hmon.root with the MonitorUI program as:

MonitorUI Output/0092716_1281323720_hmon.root

From the available histos you can choose:

  • Tracker data quality parameters: ladder average size, signal, tracker size, crates single sizes
  • Data taking quality: distribution inter-event
  • Ladder-by-ladder informations: signal, cluster size, seed occupancy, size
  • Reconstruction parameters: number of cluster, hits and tracks versus event number, rigidity, chisquared, eccetera

An example follows:

Monitor.png

For the test beam purposes several other plots are produced please check them.

Data Quality Check of Many Blocks:

The hmon files can be joined via hadd: hadd hmon-sum.root hmon1.root hmon2.root

or via the scripts mergeblocks.sh and LastHMon.sh (they are in the ~/TrackerUser/Monitor/ dir) (LastHMon.sh needs to be launched two times with parameters 'LastHMon.sh 1' and 'LastHMon.sh 2']. If this two scripts are on, you can use:

  • LastBlockHmon.root: last hmon produced by decoding (created by 'LastHMon.sh 1')
  • Last3BlocksHmon.root: last 3 hmon produced by decoding added (created by 'LastHMon.sh 1')
  • Last5BlocksHmon.root: last 5 hmon produced by decoding added (created by 'LastHMon.sh 1')
  • Last10BlocksHmon.root: last 10 hmon produced by decoding added (created by 'LastHMon.sh 2')
  • LastRunHmon.root: last hmon produced by decoding, belonging to the same run (same RunId) added (created by 'LastHMon.sh 2')
  • incrhmon.root: sum of all blocks starting from the one indicated in the script mergeblocks.sh

A typical application is to us:

  • MonitorUI Output/incrhmon.root
  • MonitorUI Output/LastBlockHmon.root

and making updates every 30 secons.

and

  • MonitorUI Output/LastCalDB.root (created by LastHMon.sh 1)
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback