How to Produce Data Files Compatible with the Liverpool Velo Production DB from ACDC3 Data

Preliminaries

  • This will only work on csh since VetraEnv is broken.
  • The ACDC3 data can be found on CASTOR: rfio:///castor/cern.ch/lhcb/testbeam/lhcbvelo/acdc3/
  • If you already have an ACDC3-ready Vetra setup you can skip the setup instructions and proceed with Running the Analysis.

How setup Vetra for ACDC3

This section is a shameless rip off from Howto Run Vetra and Panoramix on ACDC Data with some minor modifications. The setup described here will setup Vetra (and only Vetra) for ACDC3 analysis.

If you already have a working Vetra setup for ACDC3 and know exactly what you are doing, you can skip to the Running the Analysis section. Otherwise it is recommended to create a new work installation from scratch like described below.

  • the following assumes you are on a machine with access to a LHCb software installation, e.g. lxplus.
  • you have to use csh because VetraEnv is broken. So if you have a different login shell the first thing is to switch to csh:

    csh -l

  • go to a directory where you have write privileges, create a new directory and change to it, e.g.

    mkdir cmtacdc3
    cd cmtacdc3

  • downlod the setup script and source it

    source setupACDC3.csh

    This will take a while to complete when you run it the first time. It installs several packages, updates and compiles them. Once the script is finished you find yourself in the job/ directory of VeloACDC. Do not source any cmt setup scripts afterwards! Doing so is likely to break the settins for XML conditions and the geometry description.
You will have to source the setup script from within your install directory every time you start a new session. This will take not much time since the packages are installed already.

You are now ready to run the analysis as described below.

Running the Analysis

Running the analysis is simple. You only have to run one command specifying an input file name on CASTOR. Everything else like picking the correct cable configuration XML, creating the directory structure for the results etc. is done for you. So here is how it works.

  • change to the VeloACDC job/ directory:

    cd $VELOACDCROOT/job

    (if you ran the setup script described in the previous section you are already there).
  • run the command

    ./tbnoiseped -infile <input file>

    where <input file> is one of the ACDC3 data files you can find in rfio:///castor/cern.ch/lhcb/testbeam/lhcbvelo/acdc3/ without the CASTOR path, eg.

    ./tbnoiseped -infile Target_small_moved_25mm_down-2006.11.11-01.39.09.mdf

Assuming the example above, the following directory structure will be created

Target_small_moved_25mm_down/
    11.11-01.39.09/
        datafiles/
        plots/

in the results directory. The default results direcctory is ./, i.e. your current working directory. You can specify a different results directory using the -resdir switch. If you happen to have ACDC3 files in a different place than the default CASTOR location, you can also set the input path using the -inpath option. The tbnoiseped script features some more useful options, try ./tbnoiseped -h to learn about them. Note that the order in which you specify options on the command line has no significance. If a switch is used more than once, the last occurence will be overrides all previous settings.

After the job finishes the datafiles/ directory contains .dat files compatible with the Liverpool Velo production DB. These are human readable plain text files. The meaning of the data columns is documented in the files themselves. Per chip and per sensor summary files are produced for each TELL1. The plots/ directory contains the corresponding plots in .eps and .png format.

-- Kurt Rinnert - 17 Nov 2006

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2006-11-23 - KurtRinnert
 
    • 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-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