Difference: DataAnalysisVelo (1 vs. 5)

Revision 52008-07-02 - StefanoDeCapua

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

Data analysis

Line: 13 to 13
 
  1. Go to the Vetra scripts directory: "cd $VETRAROOT/scripts". In here you find a couple of shell scripts to run different Vetra jobs:
    • taskDelayscan.sh: digitisation delay scan
    • taskCabletest.sh: cable test
Changed:
<
<
    • taskSnapshot.sh: standard data taking with and without test pulses
>
>
    • taskSnapshot.sh: standard data taking without test pulses
    • taskSnapshotZS.sh: standard data taking with test pulses
 
  1. For the cable test and the standard data taking the scripts are executed with the following syntax:
    ./scriptName.sh filepath/filename.dat
    (e.g. ./slicetestCabletest.sh /daqarea/data/velo/slicetest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.dat).
  2. Wait for Vetra to finish.
  3. The Root output file is written to the corresponding directory in /group/velo/task
    (e.g. /group/velo/slicetest/cabletest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.root).
Line: 47 to 48
 

Noise and Pedestals before and after CM suppression

Changed:
<
<
  1. Change to the directory /group/velo/task/snapshot
  2. For this analysis a python script is used.
>
>
  1. Change to the directory /group/velo/task/snapshot (no test pluses) or /group/velo/task/snapshotZS (test pulses)
  2. For this analysis two python scripts can be used:
 
  1. Invoke the script via "python -i ../macros/SensorSnapshot.py"
  2. Wait for PYTHON to start.
  3. Call the analysis macro at the command prompt (>>>) via "SensorSnapshot(rootFilename, [tell1SerialNumber])"
    • The name of the root file has to be given in double quotes with or without the extension ".root". Both versions work.
    • The TELL1 serial number will be automatically detected from the contents of the file if the root file contains data from only one TELL1. If more than one TELL1 is present please provide the TELL1 serial number as an integer.
Added:
>
>
    • If you want to analyze data from all the tell1s in one go then invoke the script "SensorSnapshotSara.py".
  -- OlafBehrendt - 24 Apr 2008

Revision 42008-06-25 - OlafBehrendt

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

Data analysis

Line: 6 to 6
 

Vetra

Changed:
<
<
  1. Log on to the analysis PC plus01 on the online network.
>
>
  1. Log on to the analysis farm plus on the online network.
  2. Only temporary: Setup the CMT environment by executing "source /group/velo/sw/scripts/setup_pre64bit.sh".
 
  1. Set up Vetra by executing "setenvVetra v5r1".
  2. Run the setup script in the Vetra installation group directory: "source $User_release_area/Vetra_v5r1/Velo/Vetra/v5r1/cmt/setup.sh"
  3. Go to the Vetra scripts directory: "cd $VETRAROOT/scripts". In here you find a couple of shell scripts to run different Vetra jobs:
    • taskDelayscan.sh: digitisation delay scan
    • taskCabletest.sh: cable test
    • taskSnapshot.sh: standard data taking with and without test pulses
Changed:
<
<
  1. For the cable test and the standard data taking the scripts are executed with the following syntax:
    ./scriptName.sh filepath/filename.dat
    (e.g. ./slicetestCabletest.sh /data/velo/slicetest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.dat).
>
>
  1. For the cable test and the standard data taking the scripts are executed with the following syntax:
    ./scriptName.sh filepath/filename.dat
    (e.g. ./slicetestCabletest.sh /daqarea/data/velo/slicetest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.dat).
 
  1. Wait for Vetra to finish.
  2. The Root output file is written to the corresponding directory in /group/velo/task
    (e.g. /group/velo/slicetest/cabletest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.root).

Root

Changed:
<
<
If you start a new session instead of continuing with the same session that you used for VETRA, please repeat steps 1-3 of the Vetra section to set up the environment properly.
>
>
If you start a new session instead of continuing with the same session that you used for VETRA, please repeat steps 1,3,4 (not 2) of the Vetra section to set up the environment properly. At the moment you have to start a separate session for Root.
 

Delay scan

Revision 32008-05-06 - OlafBehrendt

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

Data analysis

Line: 50 to 50
 
  1. For this analysis a python script is used.
  2. Invoke the script via "python -i ../macros/SensorSnapshot.py"
  3. Wait for PYTHON to start.
Changed:
<
<
  1. Call the analysis macro at the command prompt (>>>) via "SensorSnapshot(rootFilename)"
>
>
  1. Call the analysis macro at the command prompt (>>>) via "SensorSnapshot(rootFilename, [tell1SerialNumber])"
 
    • The name of the root file has to be given in double quotes with or without the extension ".root". Both versions work.
Changed:
<
<
    • The TELL1 serial number will be automatically detected from the contents of the file.
>
>
    • The TELL1 serial number will be automatically detected from the contents of the file if the root file contains data from only one TELL1. If more than one TELL1 is present please provide the TELL1 serial number as an integer.
  -- OlafBehrendt - 24 Apr 2008

Revision 22008-05-06 - OlafBehrendt

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

Data analysis

Line: 9 to 9
 
  1. Log on to the analysis PC plus01 on the online network.
  2. Set up Vetra by executing "setenvVetra v5r1".
  3. Run the setup script in the Vetra installation group directory: "source $User_release_area/Vetra_v5r1/Velo/Vetra/v5r1/cmt/setup.sh"
Changed:
<
<
  1. Go to the Vetra scripts directory: "cd $VETRAROOT/scripts". In here you find all the a couple of shell scripts to run the different Vetra jobs:
>
>
  1. Go to the Vetra scripts directory: "cd $VETRAROOT/scripts". In here you find a couple of shell scripts to run different Vetra jobs:
 
    • taskDelayscan.sh: digitisation delay scan
    • taskCabletest.sh: cable test
    • taskSnapshot.sh: standard data taking with and without test pulses
Line: 30 to 30
 
    • The name of the root file has to be given in double quotes without the extension ".root".
    • The TELL1 serial number has to be provided as an integer.
    • The boolean print determines whether the plots are saved as ps/png files. The default is true.
Changed:
<
<
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in bath mode via shell script. The default is false. 1 The text file rootFilename_optimaldelay.txt contains the phase an cycle delays to be set for each PP-FPGA.
>
>
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in batch mode via shell script. The default is false.
  1. The text file rootFilename_optimaldelay.txt contains the phase an cycle delays to be set for each PP-FPGA.
 

Cable test

Line: 41 to 42
 
    • The name of the root file has to be given in double quotes without the extension ".root".
    • The TELL1 serial number has to be provided as an integer.
    • The boolean print determines whether the plots are saved as ps/png files. The default is true.
Changed:
<
<
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in bath mode via shell script. The default is false.
>
>
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in batch mode via a shell script. The default is false.
 

Noise and Pedestals before and after CM suppression

Changed:
<
<
  1. Change to the directory to /group/velo/task/snapshot
>
>
  1. Change to the directory /group/velo/task/snapshot
 
  1. For this analysis a python script is used.
Changed:
<
<
  1. Invoke the script via python -i ../macros/SensorSnapshot.py
>
>
  1. Invoke the script via "python -i ../macros/SensorSnapshot.py"
 
  1. Wait for PYTHON to start.
Changed:
<
<
  1. Call the analysis macro at the command prompt (>>>) via SensorSnapshot(rootFilename)
>
>
  1. Call the analysis macro at the command prompt (>>>) via "SensorSnapshot(rootFilename)"
 
    • The name of the root file has to be given in double quotes with or without the extension ".root". Both versions work.
    • The TELL1 serial number will be automatically detected from the contents of the file.

Revision 12008-04-24 - OlafBehrendt

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

Data analysis

Please find general instructions concerning the analysis with Vetra v5r1 here. This chapter focuses on specific tasks for which a few scripts have been defined to make the analysis more efficient. Two tasks have been considered so far, the slice test and the module power up. The following instructions cover both, please replace task with either "slicetest" or "modulepowerup".

Vetra

  1. Log on to the analysis PC plus01 on the online network.
  2. Set up Vetra by executing "setenvVetra v5r1".
  3. Run the setup script in the Vetra installation group directory: "source $User_release_area/Vetra_v5r1/Velo/Vetra/v5r1/cmt/setup.sh"
  4. Go to the Vetra scripts directory: "cd $VETRAROOT/scripts". In here you find all the a couple of shell scripts to run the different Vetra jobs:
    • taskDelayscan.sh: digitisation delay scan
    • taskCabletest.sh: cable test
    • taskSnapshot.sh: standard data taking with and without test pulses
  5. For the cable test and the standard data taking the scripts are executed with the following syntax:
    ./scriptName.sh filepath/filename.dat
    (e.g. ./slicetestCabletest.sh /data/velo/slicetest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.dat).
  6. Wait for Vetra to finish.
  7. The Root output file is written to the corresponding directory in /group/velo/task
    (e.g. /group/velo/slicetest/cabletest/slicetest_slot_VL05_CT_tell1_207_cabletest_080208_1040.root).

Root

If you start a new session instead of continuing with the same session that you used for VETRA, please repeat steps 1-3 of the Vetra section to set up the environment properly.

Delay scan

  1. Change to the directory to /group/velo/task/delayscan
  2. Start root.
  3. Load the analysis macro via ".L ../macros/taskDelayscan.C"
  4. The macro has 4 arguments: taskDelayscan(rootFilename, tell1SerialNumber, print=true, quit=false)
    • The name of the root file has to be given in double quotes without the extension ".root".
    • The TELL1 serial number has to be provided as an integer.
    • The boolean print determines whether the plots are saved as ps/png files. The default is true.
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in bath mode via shell script. The default is false. 1 The text file rootFilename_optimaldelay.txt contains the phase an cycle delays to be set for each PP-FPGA.

Cable test

  1. Change to the directory to /group/velo/task/cabletest
  2. Start root.
  3. Load the analysis macro via ".L ../macros/taskCabletest.C"
  4. The macro has 4 arguments: taskCabletest(rootFilename, tell1SerialNumber, print=true, quit=false)
    • The name of the root file has to be given in double quotes without the extension ".root".
    • The TELL1 serial number has to be provided as an integer.
    • The boolean print determines whether the plots are saved as ps/png files. The default is true.
    • The boolean quit determines whether Root is quit after the macro execution. This option is useful when the analysis is performed in bath mode via shell script. The default is false.

Noise and Pedestals before and after CM suppression

  1. Change to the directory to /group/velo/task/snapshot
  2. For this analysis a python script is used.
  3. Invoke the script via python -i ../macros/SensorSnapshot.py
  4. Wait for PYTHON to start.
  5. Call the analysis macro at the command prompt (>>>) via SensorSnapshot(rootFilename)
    • The name of the root file has to be given in double quotes with or without the extension ".root". Both versions work.
    • The TELL1 serial number will be automatically detected from the contents of the file.

-- OlafBehrendt - 24 Apr 2008

 
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