You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

DTFitter: environment

The same environment provided by the guide is suitable.

DTFitter: downloading and building the code

The source code for the DTFitter is stored in Baltig.

Since the source code of the DTFitter can be downloaded only by the authorized developers, credentials for Baltig are necessary.

The simplest way is using RSA keys, the public key must be uploaded into Baltig and the private key must be saved into ${HOME}/.ssh/id_rsa

Once git client has been correctly configured the commands are:

git clone git@baltig.infn.it:muontomography/DTFitter.git
cd DTFitter

The commands to build the code are:

cmake3 <path-to-source>
make

<path-to-source> is the path to the CMakeLists.txt file in DTFitter directory, e.g.: /home/centos/DTFitter

The executable is found in the directory run/


DTFitter: running the code

The DTFitter application performs the reconstruction of tracks of the Drift Tubes (DT) detectors from:

Preliminary settings: the configuration file

All the input parameters needed to run the code must be set in a dedicated configuration file config.ini. A template of this file can be found in the utils/ directory and must be copied in the run/ directory. Now you can modify the config.ini file in your run/ directory. 

  • General information

    VariableTypeDescription
    runNumberintnumber that identifies the dataset to be analyzed
    rawDirNamestringpath of the input file directory
    rawFileName_1stringname of the input DATA file for DET 0 (file 1_)
    rawFileName_2stringname of the input DATA file for DET 1 (file 2_)
    rawFileNameMCstringname of the input MC file
    t0FileNamestringname of the file with the initial t0 (for DATA only)
    noiseFileNamestringname of the file with noisy channels (for DATA only)
    outputDirNamestringpath of the output file directory, e.g. ../output
    outputFileNamestringname of the output file
    logFileNamestringname of the log file
    maxEventNumberintmaximum number of events to be read
  • Prototype

    VariableTypeDescription
    detectorintdetector to be analyzed: 1 for DET 0 (file 1_ of DATA), 2 for DET 1 (file 2_ od DATA), or 4 for both
  • Execution mode

    The application can be run in three different modes (please choose only one mode at each execution)

    1. Display mode: show event-per-event display
    2. Histogram mode: fill histograms for track reconstruction analysis, save them in a root output file and eventually display them at the end of execution
    3. TTree mode: fill a root TTree with the reconstructed track parameters and save them in a root output file
    VariableTypeDescription
    displayboolset to 1 to run in Display mode, 0 otherwise
    waitboolshould be equal to the display variable
    histosboolset to 1 to run in Histograms mode, 0 otherwise
    showHistosboolset to 1 to display the histograms at the end of execution
    ttreeboolset to 1 to run in TTree mode, 0 otherwise
  • Debugging

    VariableTypeDescription
    debugboolset to 1 to dump debug messages
  • Castor MC

    VariableTypeDescription
    isCastorMCboolset to 1 for simulated datasets (0 not implemented for now)
    det0RotfloatDET 0 rotation angle set in the simulation [deg]
    det1RotfloatDET 1 rotation angle set in the simulation [deg]
    det0Distfloatdistance of DET 0 center from MC reference frame origin in (x,y) plane [cm]
    det1Distfloatdistance of DET 1 center from MC reference frame origin in (x,y) plane [cm]
    det0Zfloatz coordinate of DET 0 center in MC reference frame [cm]
    det1Zfloatz coordinate of DET 1 center in MC reference frame [cm]
    useTrueDriftTimesbooluse true drift times for the fit (1), or smeared drift times (0)
  • Fit

    VariableTypeDescription
    minNHitsintminimum number of hits accepted in a collection
    maxNHitsintmaximum number of hits accepted in a collection
    maxPattRecIterintmaximum number of fit iterations for Pattern Recognition (PR)
    sigmaPRfloat3*sigmaPR [mm] set the threshold to reject hits after the PR
    maxVertFitIterintmaximum number of fit iterations for Vertical Fit (VF)
    sigmaVFfloat3*sigmaVF [mm] set the threshold to reject hits after the VF
    maxDriftTimeFitIterintmaximum number of fit iterations for the Drift Time Fit (DTF)
    sigmaDTFfloat3*sigmaDTF [mm] set the threshold to reject hits after the DTF
    maxCHi2MinimizationIterintmaximum number of iterations for the Chi2 minimization procedure in the DTF
    minDeltaChi2floatminimum value of the Chi2 variation between consecutive iterations needed to stop the Chi2 minimization procedure in the DTF
Preliminary settings: other input files

In order to analyze data, the following .txt files should be added in the /utils/ directory:

  • a file containing the t0 of each event with this format:

    [event ID] [t0 info] [t0 DET 0 in ns] [t0 DET 1 in ns]

    where [t0 info] is set to ext if a mean timer is present in that event, otherwise to min if the minimum of the drift times of that event must be used.

  • a file containing information on eventual noisy channels, with this format:

    [detector] [board ID] [channel ID] [SW layer ID] [SW tube ID]

    where [detector] could be either DET0 or DET1.

Other files in the /DTfitter/utils/ directory are:

  • Space-Time_Parameters.txt: it contains the parameters of the polynomial used to describe the relation between drift distance and the drift time. It should be updated any time a new dataset is analyzed.

  • ChannelMapTubes.txt: it contains the channel map, that has the following format:

    [board ID] [channel ID] [HW layer ID] [HW tube ID] [channel FW] [SW layer ID] [SW tube ID]
How to run
cd run
./runDT





  • No labels