Difference: DataQuality (1 vs. 10)

Revision 102010-08-17 - AlbertoOliva

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

Data Quality

Line: 10 to 10
  You can reach this programs from the data quality directory from every PC in the POCC. You have to logon with the tracker user (no password required) and go to the ~/TrackerUser/Monitor directory.
Deleted:
<
<
* If you want AMI interface wirking properly you need the AMI monitor scanner startuo procedure (if not executed) * If you want the Data Quality files ...

META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281892052" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="189641" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp25737" user="mduranti" version="2"
META FILEATTACHMENT attachment="Monitor.png" attr="" comment="" date="1281326118" name="Monitor.png" path="Monitor.png" size="77250" stream="Monitor.png" tmpFilename="/usr/tmp/CGItemp16515" user="oliva" version="1"

Revision 92010-08-16 - AlbertoOliva

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

Data Quality

Revision 82010-08-16 - AlbertoOliva

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

Data Quality


>
>

Data Quality

 
Changed:
<
<
Raw data came from AMS in form of Blocks, binary files containing the AMS encoded informations. Block files a come 1 per minute. We promptly decode, reconstruct and analyze this data in order to have a fast quality check.
>
>
Raw data came from AMS in form of Blocks, binary files containing the AMS encoded informations. Block files a come 1 per minute. We promptly decode, reconstruct and analyze this data in order to have a fast quality check. The decoded informations are:
 
Deleted:
<
<
You have several tools in order to achieve this job:
 
  • AMI Monitor: in order to have meaningful data is important to have the Tracker in stable temperature condition (a rapid increase temperature will give a raise in the Tracker event size!)
  • Decoding program: this program does all the job. It takes a block, decodes it, reconstructs the track and prepares histograms.
  • MonitorUI: user interface to the monitoring and calibration files.

You can reach this programs from the data quality directory from every PC in the POCC. You have to logon with the tracker user (no password required) and go to the ~/TrackerUser/Monitor directory.

Deleted:
<
<


 
Changed:
<
<

Decoding program


>
>
* If you want AMI interface wirking properly you need the AMI monitor scanner startuo procedure (if not executed) * If you want the Data Quality files ...
 
Deleted:
<
<
Incoming blocks from JMDC can be found on /Data/BLOCKS/HRDL-@/xxxx/yyy (where @: stands for "A" or "B", depending of which HRDL server we are using; yyy is the block file number (it ranges from 000 to 999); xxxx is the directory name)

Block files are produced 1 per minute (if JMDC is alive). When the block number reaches 999 a new directory named xxxx+1 is created and the block number restarts from 0.

In block file you can find event blocks, calibration blocks, slowcontrol blocks, nothing, everything ...

The program able to produce usable information from Block files is called Decode. It's launched normally with a python script: scanmagon_new.py.

The default values of this script are:

  • produce the calibration (if is in the block)
  • select events with 3/4 TOF planes hitted (every 3/4 is a good particle candidate for Tracker)
  • prescale events 1 over 20 (in order to scan faster)
  • reconstruct only tracker, from Raw Clusters up to the Tracks
  • produce monitoring histos

scanmagon_new.py -d -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999

This is an example of the use of this script, you can find more informations simply typing scanmagon_new.root <enter>.

This program will produce in the Output directory few files:

  • CalDB _1261365522.root: this file contains a calibration (can be viewed by MonitorUI)
  • 0040580_126136727_ErrReport.txt: this text file provides several important parameters (event size, trigger rate, recon status). It is very useful for data quality quick check.
  • 0040580_1261365727_recon.root: contains the DST of the block (pg-standalone reconstruction)
  • 0040580_1261365727_hmon.root: contains monitoring infos (can be viewed by MonitorUI)
  • 0040580_126136727_ErrReport.txt is a text file with the statistics and error counting

N.B.: Probably you find this demon running so you don't need to launch it!


Calibration Visualization


The produced CalDB_*.root may have a size of almost 800k on disk. Please be sure of that. From time to time a short calibration (only 800 byte) could appear: delete it!

The CalDB _*.root can be opened by the MonitorUI application, type:

MonitorUI Output/CalDB_1281323717.root

A display similar to the one in attachment wil appear. From this interface you could alternatively observe:

  • cumulative distributions: pedestals, sigmas, status bits
  • ladder-by-ladder distributions: pedestals, sigma, common noise, occupancy, TDR code, Power Failure status, eccetera
  • comparison with past calibration: if you chose a reference file (a set can be founded in the RefFiles directory)

Monitor_CalDB.png


Data Monitoring


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.

Other useful informations:


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)
 
META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281892052" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="189641" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp25737" user="mduranti" version="2"
META FILEATTACHMENT attachment="Monitor.png" attr="" comment="" date="1281326118" name="Monitor.png" path="Monitor.png" size="77250" stream="Monitor.png" tmpFilename="/usr/tmp/CGItemp16515" user="oliva" version="1"

Revision 72010-08-15 - MatteoDuranti

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

Data Quality


Line: 64 to 64
 
  • ladder-by-ladder distributions: pedestals, sigma, common noise, occupancy, TDR code, Power Failure status, eccetera
  • comparison with past calibration: if you chose a reference file (a set can be founded in the RefFiles directory)
Changed:
<
<
Monitor_CalDB.png
>
>
Monitor_CalDB.png
 


Line: 87 to 87
  An example follows:
Changed:
<
<
Monitor.png
>
>
Monitor.png
  For the test beam purposes several other plots are produced please check them.
Line: 111 to 111
 and making updates every 30 secons.

and

Changed:
<
<
  • MonitorUI Output/LastCalDB.root (created by LastHMon.sh 1)
>
>
  • MonitorUI Output/LastCalDB.root (created by LastHMon.sh 1)
 
Changed:
<
<
META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281324441" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="495211" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp16684" user="oliva" version="1"
>
>
META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281892052" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="189641" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp25737" user="mduranti" version="2"
 
META FILEATTACHMENT attachment="Monitor.png" attr="" comment="" date="1281326118" name="Monitor.png" path="Monitor.png" size="77250" stream="Monitor.png" tmpFilename="/usr/tmp/CGItemp16515" user="oliva" version="1"

Revision 62010-08-15 - MatteoDuranti

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

Data Quality


Line: 6 to 6
 Raw data came from AMS in form of Blocks, binary files containing the AMS encoded informations. Block files a come 1 per minute. We promptly decode, reconstruct and analyze this data in order to have a fast quality check.

You have several tools in order to achieve this job:

Changed:
<
<
  • AMI Monitor: in order to have meaningful data is important to have the Tracker in stable temperature condition (a radid increase temperature wil give a raise in the Tracker event size!)
>
>
  • AMI Monitor: in order to have meaningful data is important to have the Tracker in stable temperature condition (a rapid increase temperature will give a raise in the Tracker event size!)
 
  • Decoding program: this program does all the job. It takes a block, decodes it, reconstructs the track and prepares histograms.
  • MonitorUI: user interface to the monitoring and calibration files.
Line: 14 to 14
 


Deleted:
<
<

AMI Monitor


http://ams.cern.ch:8081/AMI/show/tracker_temperatures/

From here you can constantly monitor the tracker temperatures. A typical behaviour follows:

 
Deleted:
<
<
AMI.png


 

Decoding program


Line: 73 to 64
 
  • ladder-by-ladder distributions: pedestals, sigma, common noise, occupancy, TDR code, Power Failure status, eccetera
  • comparison with past calibration: if you chose a reference file (a set can be founded in the RefFiles directory)
Changed:
<
<
Monitor_CalDB.png
>
>
Monitor_CalDB.png
 

Added:
>
>
 
Added:
>
>
 

Data Monitoring


Line: 94 to 87
  An example follows:
Changed:
<
<
Monitor.png
>
>
Monitor.png
 
Changed:
<
<
For the test beam purposes several other plots are produced please che them.
>
>
For the test beam purposes several other plots are produced please check them.
 
Changed:
<
<
Other useful informations:
>
>

Other useful informations:


  The hmon files can be joined via hadd: hadd hmon-sum.root hmon1.root hmon2.root
Changed:
<
<
or via the scripts mergeblocks.sh and LastHMon.sh. If this two scripts are on, you can use:

lasthmon.root: last hmon produced by decoding

incrhmon.root: sum of all blocks starting from the one indicated in the script mergeblocks.sh

>
>
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:
Changed:
<
<
MonitorUI Output/incrhmon.root

MonitorUI Output/lastmon.root

>
>
  • MonitorUI Output/incrhmon.root
  • MonitorUI Output/LastBlockHmon.root
  and making updates every 30 secons.
Added:
>
>
and
  • MonitorUI Output/LastCalDB.root (created by LastHMon.sh 1)
 
META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281324441" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="495211" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp16684" user="oliva" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="AMI.png" attr="" comment="" date="1281325650" name="AMI.png" path="AMI.png" size="181425" stream="AMI.png" tmpFilename="/usr/tmp/CGItemp16642" user="oliva" version="1"
 
META FILEATTACHMENT attachment="Monitor.png" attr="" comment="" date="1281326118" name="Monitor.png" path="Monitor.png" size="77250" stream="Monitor.png" tmpFilename="/usr/tmp/CGItemp16515" user="oliva" version="1"

Revision 52010-08-09 - AlbertoOliva

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

General Info

>
>

Data Quality

 
Changed:
<
<
The data coming from JMDC after the deframing can be found following this path:
>
>
Raw data came from AMS in form of Blocks, binary files containing the AMS encoded informations. Block files a come 1 per minute. We promptly decode, reconstruct and analyze this data in order to have a fast quality check.
 
Changed:
<
<
/Data/BLOCKS/HRDL-@/xxxx/yyy
>
>
You have several tools in order to achieve this job:
  • AMI Monitor: in order to have meaningful data is important to have the Tracker in stable temperature condition (a radid increase temperature wil give a raise in the Tracker event size!)
  • Decoding program: this program does all the job. It takes a block, decodes it, reconstructs the track and prepares histograms.
  • MonitorUI: user interface to the monitoring and calibration files.
 
Changed:
<
<
@: stands for "A" or "B", depending of which HRDL Server we are using.
>
>
You can reach this programs from the data quality directory from every PC in the POCC. You have to logon with the tracker user (no password required) and go to the ~/TrackerUser/Monitor directory.


AMI Monitor


http://ams.cern.ch:8081/AMI/show/tracker_temperatures/

 
Changed:
<
<
yyy is the block file number (it ranges from 000 to 999)
>
>
From here you can constantly monitor the tracker temperatures. A typical behaviour follows:
 
Changed:
<
<
xxxx is the directory name
>
>
AMI.png


Decoding program


Incoming blocks from JMDC can be found on /Data/BLOCKS/HRDL-@/xxxx/yyy (where @: stands for "A" or "B", depending of which HRDL server we are using; yyy is the block file number (it ranges from 000 to 999); xxxx is the directory name)

  Block files are produced 1 per minute (if JMDC is alive). When the block number reaches 999 a new directory named xxxx+1 is created and the block number restarts from 0.
Changed:
<
<
In block file you can find: event blocks, calibration blocks, slowcontrol blocks, nothing, ...
>
>
In block file you can find event blocks, calibration blocks, slowcontrol blocks, nothing, everything ...

The program able to produce usable information from Block files is called Decode. It's launched normally with a python script: scanmagon_new.py.

The default values of this script are:

  • produce the calibration (if is in the block)
  • select events with 3/4 TOF planes hitted (every 3/4 is a good particle candidate for Tracker)
  • prescale events 1 over 20 (in order to scan faster)
  • reconstruct only tracker, from Raw Clusters up to the Tracks
  • produce monitoring histos

scanmagon_new.py -d -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999

This is an example of the use of this script, you can find more informations simply typing scanmagon_new.root <enter>.

This program will produce in the Output directory few files:

  • CalDB _1261365522.root: this file contains a calibration (can be viewed by MonitorUI)
  • 0040580_126136727_ErrReport.txt: this text file provides several important parameters (event size, trigger rate, recon status). It is very useful for data quality quick check.
  • 0040580_1261365727_recon.root: contains the DST of the block (pg-standalone reconstruction)
  • 0040580_1261365727_hmon.root: contains monitoring infos (can be viewed by MonitorUI)
  • 0040580_126136727_ErrReport.txt is a text file with the statistics and error counting

N.B.: Probably you find this demon running so you don't need to launch it!


Calibration Visualization


The produced CalDB_*.root may have a size of almost 800k on disk. Please be sure of that. From time to time a short calibration (only 800 byte) could appear: delete it!

 
Changed:
<
<

Scan Block Demon

>
>
The CalDB _*.root can be opened by the MonitorUI application, type:
 
Added:
>
>
MonitorUI Output/CalDB_1281323717.root

A display similar to the one in attachment wil appear. From this interface you could alternatively observe:

  • cumulative distributions: pedestals, sigmas, status bits
  • ladder-by-ladder distributions: pedestals, sigma, common noise, occupancy, TDR code, Power Failure status, eccetera
  • comparison with past calibration: if you chose a reference file (a set can be founded in the RefFiles directory)

Monitor_CalDB.png


Data Monitoring

 
Changed:
<
<
From the directory TrackerUser/Monitor exist several scan block demons (python script). You can start one of them typing:
>
>
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.
 
Changed:
<
<
scan.py -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999
>
>
Instead you can open the files Output/*_hmon.root with the MonitorUI program as:
 
Changed:
<
<
scanmagon.py -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999
>
>
MonitorUI Output/0092716_1281323720_hmon.root
 
Changed:
<
<
This scan demon will produce in the TrackerUser/Monitor/Output (or [...]/OutputHighRes) directory some files:
>
>
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
 
Changed:
<
<
CalDB _1261365522.root contains a calibration (TrCalDB)
>
>
An example follows:
 
Changed:
<
<
0040580_1261365727_recon.root or 0040580_1261365727_data.root contains the DST of the block (pg-standalone reconstruction)
>
>
Monitor.png
 
Changed:
<
<
0040580_1261365727_hmon.root contains monitoring infos
>
>
For the test beam purposes several other plots are produced please che them.
 
Changed:
<
<
0040580_126136727_ErrReport.txt is a text file with the statistics and error counting
>
>
Other useful informations:
 
Changed:
<
<
N.B.: Probably you find this demon running so you don't need to launch it!

Display


>
>
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. If this two scripts are on, you can use:

lasthmon.root: last hmon produced by decoding

incrhmon.root: sum of all blocks starting from the one indicated in the script mergeblocks.sh

 
Changed:
<
<
We can use two different displays:
>
>
A typical application is to us:
 
Changed:
<
<
For CalDB _*.root and _hmon.root we can use:
TrackerUser/MonitorUI/MonitorUI
  • To look at the data as they came out you have to look (with MonitorUI) the penultimate *_hmon.root (the last can be not a closed file...) or the last CalDB _.root.
>
>
MonitorUI Output/incrhmon.root
 
Changed:
<
<
For test beam purpose a very quick monitor of the data (in particular position of the beam in the tracker) can be done by using:
ROOT macro TestBeam.C in TrackerUser/Monitor/.
  • To launch it (from this directory) you have to type:
    root -l TestBeam.C
    Two windows will be appear. These windows updates themself every 10 seconds looking at the data as they come out. When another Run is launched, i.e. RunNumber (or RunID) changes, the histos will be claered and restarted with the new data.
>
>
MonitorUI Output/lastmon.root
 
Changed:
<
<
For reconstructed data *_recon.root or *_data.root we can use:
TrackerUser/tkdisplay/tkdisplay
>
>
and making updates every 30 secons.
 
Changed:
<
<
-- AlbertoOliva - 21-Dec-2009
>
>
META FILEATTACHMENT attachment="Monitor_CalDB.png" attr="" comment="" date="1281324441" name="Monitor_CalDB.png" path="Monitor_CalDB.png" size="495211" stream="Monitor_CalDB.png" tmpFilename="/usr/tmp/CGItemp16684" user="oliva" version="1"
META FILEATTACHMENT attachment="AMI.png" attr="" comment="" date="1281325650" name="AMI.png" path="AMI.png" size="181425" stream="AMI.png" tmpFilename="/usr/tmp/CGItemp16642" user="oliva" version="1"
META FILEATTACHMENT attachment="Monitor.png" attr="" comment="" date="1281326118" name="Monitor.png" path="Monitor.png" size="77250" stream="Monitor.png" tmpFilename="/usr/tmp/CGItemp16515" user="oliva" version="1"

Revision 42010-02-07 - MatteoDuranti

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

General Info


Line: 27 to 27
  scanmagon.py -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999
Changed:
<
<
This scan demon will produce in the TrackerUser/Monitor/Output directory some files:
>
>
This scan demon will produce in the TrackerUser/Monitor/Output (or [...]/OutputHighRes) directory some files:
  CalDB _1261365522.root contains a calibration (TrCalDB)
Line: 36 to 36
 0040580_1261365727_hmon.root contains monitoring infos

0040580_126136727_ErrReport.txt is a text file with the statistics and error counting

Added:
>
>
N.B.: Probably you find this demon running so you don't need to launch it!
 

Display


We can use two different displays:

Changed:
<
<
For CalDB _*.root and *_hmon.root we can use

TrackerUser/MonitorUI/MonitorUI

>
>
For CalDB _*.root and _hmon.root we can use:
TrackerUser/MonitorUI/MonitorUI
  • To look at the data as they came out you have to look (with MonitorUI) the penultimate *_hmon.root (the last can be not a closed file...) or the last CalDB _.root.
 
Changed:
<
<
For reconstructed data *_recon.root or *_data.root we can use:
>
>
For test beam purpose a very quick monitor of the data (in particular position of the beam in the tracker) can be done by using:
ROOT macro TestBeam.C in TrackerUser/Monitor/.
  • To launch it (from this directory) you have to type:
    root -l TestBeam.C
    Two windows will be appear. These windows updates themself every 10 seconds looking at the data as they come out. When another Run is launched, i.e. RunNumber (or RunID) changes, the histos will be claered and restarted with the new data.
 
Changed:
<
<
TrackerUser/tkdisplay/tkdisplay
>
>
For reconstructed data *_recon.root or *_data.root we can use:
TrackerUser/tkdisplay/tkdisplay
  -- AlbertoOliva - 21-Dec-2009

Revision 32009-12-21 - AlbertoOliva

Line: 1 to 1
 
META TOPICPARENT name="AmsTracker"
Changed:
<
<
  • TO CHECK CALIBRATION:

    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])

    • Look for the latest calibration file “yyy”:

      calibration blocks have a typical size of 2 M

    • Then:

      cd /home/ams/TrackerUserMonitor


    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars


      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B"

    • Open (automagically) CalPainter:

      ./DoMonitor xxyyy



  • TO CHECK DATA:

    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])

    • Look for the block file “yyy”: typical size is 50-60 M (it depends mainly on OUR threshold obviously!!!)

    • Then

      cd /home/ams/TrackerUserMonitor/

    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars


      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B".

    • Open (automagically) Root with same useful plots:

      ./DoMonitor xxyyy


>
>

General Info


 
Changed:
<
<
-- MatteoDuranti - 08-Dec-2009
>
>
The data coming from JMDC after the deframing can be found following this path:

/Data/BLOCKS/HRDL-@/xxxx/yyy

@: stands for "A" or "B", depending of which HRDL Server we are using.

yyy is the block file number (it ranges from 000 to 999)

xxxx is the directory name

Block files are produced 1 per minute (if JMDC is alive). When the block number reaches 999 a new directory named xxxx+1 is created and the block number restarts from 0.

In block file you can find: event blocks, calibration blocks, slowcontrol blocks, nothing, ...

Scan Block Demon


From the directory TrackerUser/Monitor exist several scan block demons (python script). You can start one of them typing:

scan.py -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999

scanmagon.py -B /Data/BLOCKS/HRDL-A -f 0040/529 -l 0040/999

This scan demon will produce in the TrackerUser/Monitor/Output directory some files:

CalDB _1261365522.root contains a calibration (TrCalDB)

0040580_1261365727_recon.root or 0040580_1261365727_data.root contains the DST of the block (pg-standalone reconstruction)

0040580_1261365727_hmon.root contains monitoring infos

0040580_126136727_ErrReport.txt is a text file with the statistics and error counting

Display


We can use two different displays:

For CalDB _*.root and *_hmon.root we can use

TrackerUser/MonitorUI/MonitorUI

For reconstructed data *_recon.root or *_data.root we can use:

TrackerUser/tkdisplay/tkdisplay

-- AlbertoOliva - 21-Dec-2009

Revision 22009-12-08 - MatteoDuranti

Line: 1 to 1
 
META TOPICPARENT name="AmsTracker"
Changed:
<
<
  • TO CHECK CALIBRATION:
    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])
    • Look for the latest calibration file “yyy”:

      calibration blocks have a typical size of 2 M
    • Then:

      cd /home/ams/TrackerUserMonitor
    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars
    • It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B"
    • Open (automagically) CalPainter:

      ./DoMonitor xxyyy

  • TO CHECK DATA:
    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/
      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])
    • Look for the block file “yyy”: typical size is 50-60 M (it depends mainly on OUR threshold obviously!!!)
    • Then
      cd /home/ams/TrackerUserMonitor/
    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):
      source ./pocc.cern.vars
      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B".
    • Open (automagically) Root with same useful plots:
      ./DoMonitor xxyyy
>
>
  • TO CHECK CALIBRATION:

    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])

    • Look for the latest calibration file “yyy”:

      calibration blocks have a typical size of 2 M

    • Then:

      cd /home/ams/TrackerUserMonitor


    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars


      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B"

    • Open (automagically) CalPainter:

      ./DoMonitor xxyyy



  • TO CHECK DATA:

    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])

    • Look for the block file “yyy”: typical size is 50-60 M (it depends mainly on OUR threshold obviously!!!)

    • Then

      cd /home/ams/TrackerUserMonitor/

    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars


      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B".

    • Open (automagically) Root with same useful plots:

      ./DoMonitor xxyyy


  -- MatteoDuranti - 08-Dec-2009

Revision 12009-12-08 - MatteoDuranti

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AmsTracker"
  • TO CHECK CALIBRATION:
    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/

      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])
    • Look for the latest calibration file “yyy”:

      calibration blocks have a typical size of 2 M
    • Then:

      cd /home/ams/TrackerUserMonitor
    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):

      source ./pocc.cern.vars
    • It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B"
    • Open (automagically) CalPainter:

      ./DoMonitor xxyyy

  • TO CHECK DATA:
    • Data blocks should be found in :/Data/BLOCKS/HRDL-@/00xx/
      Where "@" is "A" or "B", depending of which HRDL Server we are using (usually is the "A" and you can check it by looking for the newest block file [each block file is a 00xx directory...])
    • Look for the block file “yyy”: typical size is 50-60 M (it depends mainly on OUR threshold obviously!!!)
    • Then
      cd /home/ams/TrackerUserMonitor/
    • Set the environment variable $BlkDir (that points to /Data/BLOCKS/HRDL-@/):
      source ./pocc.cern.vars
      It will ask for you if we're working on HRDL-A or HRDL-B, so you have to reply "A" or "B".
    • Open (automagically) Root with same useful plots:
      ./DoMonitor xxyyy

-- MatteoDuranti - 08-Dec-2009

 
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