> Dear Djamel,
please could you send me BrTofSaveModule.
Yours Michael
> Hi all,
>
> I would like to inform people that I've updated the tof software.
> Several new classes were created for the calibration:
>
> BrTofCalibrationPackage <--- container (for the 3 detectors)
> BrTofCalibrationModule <--- container (for 1 single detector)
> BrTofPedestalModule
> BrTofAdcGainModule
> BrTofTdcOffsetModule
> BrTofSlewingModule
>
> BrTofSaveCalModule <--- module to save / commit calibration
> (this might sound useless but we
> can discuss it after people check it)
>
> BrTofCalibration <--- parameter element class
>
> The dialog with the DB (via parameter element and runinfo managers) is
> done in the package class.
> All you have to use is the package class. Nothing else should be used (the
> other classes are internal to this package) since the class package allows
> the user to turn on 1, 2 or 3 detectors and set the calibration type
> (SetTof1On(), SetTof2On(), SetTofwOn() and SetProcess("<calibration type>")
>
> I made these classes in the spirit of the brat standard (a module does one
> action on input data and returns data).
> I use a configuration file TofCalibConfig.C to calibrate what I need.
> To use it, one has only to type
>
> TestMainModule TofCalibConfig.C + some options
> (TestMainModule TofCalibConfig.C --help for some help)
>
> I had to deal with "philophical problems" regarding the parameter
> revisions. But I'll give more details in a note with description and
> results I get (I'll hopefully finish this weekd end).
>
> To be honest, I haven't tried yet the tdc offset and the slewing since I
> need some reduced data files (with global tracks) and the ones I have here
> cannot be read because of a streamer problem (I guess we should update our
> files or maybe fix the streamer). But it's on it's way.
>
> If no one disagrees, I'll commit at least the main stuff + pedestal and
> adcgain modules tomorrow.
>
> One last thought: while I was updating all that, I realized how important
> it was to converge towards some standard and automatic procedure. So, to
> second Christian's voice, I strongly recommand we use the main module thing.
> Another thing is the calibration procedure itself. I hope some people will
> check the validity of the procedure, especially for the timing (the most
> tricky one). As far as I know, it should be improved.
>
> Things to come (need some tests once tdc offset and slewing are ok):
> BrTofHitModule <--- for hit reconstruction
> BrTofHit <--- simple data object (very similar to BrCalTof)
>
> BrTofPidModule <--- simple module for track-tof PID
>
> Other things to come (but afterwards)
> BrC1DigModule <--- C1 digitization module
> BrC1PidModule <--- to complete the track-tof PID in FFS
>
> Last but not least: if no one is working on, I'll try to write the same
> kind of calibration classes for the beam-beam counters.
>
> That's all folks :)
>
> Ciao
> Djam
>
> --
> Djamel Ouerdane ------------------------------------------o
> | Niels Bohr Intstitute | Home: |
> | Blegdamsvej 17, DK-2100 Ø | Jagtvej 141 2D, |
> | Fax: +45 35 32 50 16 | DK-2200 Copenhagen N |
> | Tel: +45 35 32 52 69 | +45 35 86 19 74 |
> | http://www.nbi.dk/~ouerdane |
> | ouerdane@nbi.dk |
> o---------------------------------------------------------o
This archive was generated by hypermail 2b29 : Tue May 29 2001 - 14:46:04 EDT