CbmRoot » Simulation

CbmMuchDigi and CbmRichDigi are also done.

It will not be possible to remove the TObject inheritance from CbmMvdDigi, since the MVD digitizer uses internally TClonesArrays very extensively. Making CbmMvdDigi a standalone object would require a major redesign of the entire MVD software. We will have to do that eventually, but I do not think that is feasible for the APR20 release.

CbmTrdDigi is also done (r15843).

I had to remove the classes

beamtime/trd/lib/CbmTrdSimpleDigitizer and
beamtime/trd/lib/CbmTrdAdvDigitizer

from the build. These classes do not only read digis, but produce them in TClonesArrays, so no easy and quick fix was possible. I did not go into the trouble of fixing them, since the entire beamtime directory is probably obsolete anyhow.

With r15844, also CbmTofDigi is not a TObject any longer.

The only difficulty in the reco tasks was found in CbmTofEventClusterizer, which is used for reconstruction of mCBM (Reconstruction for full CBM is done with CbmTofSimpleClusterizer). This class used internally TClonesArrays to store calibrated digis, alo of type CbmTofDigi. I have changed this to the usage of std::vector instead. I have no means to test it, though, with real data. The code is close to undebuggable.

Since the T0 digis are also described by the class CbmTofDigi, but not included (yet) in CbmDigiManager, I have introduced the use of std:vector explicitely for T0 in some tasks in fles/mcbm2018/tasks (CbmCheckEvents, CbmCheckTiming).

So, now all our digi classes are non-TObjects. This issue can thus be closed.

All reconstruction classes should by now work formally with both vector input and TClonesArray input. Of course, our digis cannot be stored in TClonesArrays any longer, so the TClonesArray option is obsolete. Yes, the unpackers have to produce output in this format.

I do not know of all analyis macros, of course.

The last class to be adapted was CbmMcbm2018EventBuilder. With that, I close this issue.