Re: TPM2 enable and disable rows

From: Christian Holm Christensen (cholm@hehi03.nbi.dk)
Date: Fri Oct 12 2001 - 06:44:30 EDT

  • Next message: Peter H. L. Christiansen: "BRAT-2-1-10"

    Hi Jens et al, 
    
    On Thu, 11 Oct 2001 14:39:36 -0400
    Jens Ivar Jordre <jens@fi.uib.no> wrote
    concerning "TPM2 enable and disable rows":
    > Howdy brahmsers.
    > 
    > Due to low effiency at the back of TPM2 FEE cards covering rows 19-20
    > were moved to rows 17-18. This operation was done today. The last data
    > run with the old setting is thus 5276. What remains is to handle this
    > properly in software.
    > 
    > Since most of the data collected this year is with rows 19-20
    > instrumented, one should probably leave the DetectorParameters.txt file
    >      as it is. Therefore there are at least two ways of handling this in
    > applications/scripts.
    > 
    > 1.  After calling
    >       params->SetDbParameterFileName("DetectorParameters.txt");
    >       (or something more complex involving options and/or BrPathManager)
    
    You do not need the BrPathManager in this case.  The
    BrParametersDbManager first tries to open <file> in current dir, or if
    <file> is a full path, that file.  If that failes, then it uses the
    BrPathManager to get the directory where such files are installed,
    which is <prefix>/share/brat/params (or something like that anyway). 
    
    >       one can enable and disable rows with
    >       BrDetectorParamsTPC* tpm2Par = (BrDetectorParamsTPC*)
    >             params->GetDetectorParameters("BrDetectorParamsTPC", "TPM2");
    >       tpm2Par->SetRowActive(17);
    >       tpm2Par->SetRowActive(18);
    >       tpm2Par->SetRowInActive(19);
    >       tpm2Par->SetRowInActive(20);
    > 
    > 2.  Make a tiny script that does this. The session will then be like:
    >       params->SetDbParameterFileName("DetectorParameters.txt");
    >       gROOT->Macro("TPM2ParamsAfter20011011.C");
    > 
    > By putting this small macro into say brat/scripts, on has easy
    > reference to it via BrPathManager::GetScriptDir(). Any objection to
    > doing it this way? 
    
    Hmm.  Make sure you install the script in the regular script directory
    (see scripts/Makefile.am - it's straight forward). 
    
    All that said, I believe that such things as active elements, ladida,
    should be in the geometry/calibration database.  I believe Peter is
    working on something like that for the TPCs. Why don't you consult
    him? 
    
    Yours, 
    
    Christian Holm Christensen -------------------------------------------
    Address: Sankt Hansgade 23, 1. th.           Phone:  (+45) 35 35 96 91 
             DK-2200 Copenhagen N                Cell:   (+45) 28 82 16 23
             Denmark                             Office: (+45) 353  25 305 
    Email:   cholm@nbi.dk                        Web:    www.nbi.dk/~cholm
    



    This archive was generated by hypermail 2b30 : Fri Oct 12 2001 - 06:44:58 EDT