How to edit/read the logbook

-- PaulaCollins - 15 Jun 2006

How to extract basic calibration information from histogram file generated by Vetra

  • Start root
    1. Log onto lxplus node as lhcbvelo
    2. Make sure that ROOT is in the default search PATH, otherwise follow Vetra setup procedure
    3. Change current default working directory to: cd ~/cmtuser/Velo/Vetra/v3r0/work
    4. Copy the output histogram file to working directory
    5. Start root and run various scripts

  • Script badChannel.C can be used to check noise performance and bad channels
    1. The script can be run by following commands in root:
        .L badChannel.C
        badChannel("M18P_0607_Noise1.root", 'p', 1.5, 3.0)
    2. The arguments is as follows: the name of histogram file of a noise run, the type of hybrid (p/r), the low limit of total noise, and the upper limit of common mode suppressed noise
    3. The script produces a list of bad channels that are beyond the noise limit
    4. The script also produces following plots
      • Noise vs electronic channel ID
      • Noise vs software channel ID, where a channel mapping is used
      • Noise distribution of all channels
      • Total noise for inner and outer phi strips
    5. User interactive control is provided on whether or not (y/n) to save the plot into a file or skip (q) all the rest plots. For option (y), user needs to provide file name after the prompt

  • Script headerAna.C can be used to check signal to noise ratio using header signals
    1. The script can be run by following commands in root:
        .L headerAna.C
    2. Handling of plots is the same of the first script
    3. The script generates following plots
      • Signal in last bit of all headers
      • Average signals (High/Low) in last bits vs link
      • Difference of High and Low in last bits. The difference corresponds to roughly 66,000 electrons (3 MIPs in 300 um Si)
      • Average common mode suppressed noise per link vs link
      • Last bit High/Low difference divided by (3 x noise). The ratio represents real signal to noise ratio of 300 um Si

-- Jianchun Wang - 15 Jun 2006

How to transfer data to Castor The raw data files from DAQ are directly stored on machines with local IP address (eg, velotest.daq.lhcb). The files are copied to a machine on both local and public networks (eg, veloassembly4.daq.lhcb or first, and later copied to CASTOR storage. Two csh scripts are written to make file transfer a little easier.

  1. /home/velo/Velo_File_Trans/cp_data_out. This script should be run on local machine (velotest). It can be called either by online process after the data file is generated, or manually. It uses "scp" to transfer data file to veloassembly4 machine. The syntax is
       cp_data_out datafile.bin
  2. /home/data/Velo_File_Trans/cp_2_castor. This script runs on pcveloassembly4 as cron job under "lhcbvelo" username. It checks directory /home/data every ten minutes. If a file with name (*.bin) is at least 5 minutes old, it is copied to CASTOR.
  3. On CASTOR the testbeam data are stored in /castor/

-- Jianchun Wang - 19 Jun 2006


How to Run the Tell1 console

   1 - log in to your favourite tell1.

   2 - run the script startConsole (./startConsole)  

   3 - press m for monitoring and m again to get the raw data 

   4 - type the number of the selected ppfpga (the input on the tell1 == ARx == counting from 0 from the top of the crate)

   5 - Look at the data.





Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2006-08-07 - KazuyoshiAkiba
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback