CbmRoot » Simulation

Here the idea was to add a FairTask after running the simulation which is possible within FairRoot. In the Exec function of this task the user can do whatever is needed to decide if the event should be written to the output file or not. In case he want to skip the event he has simply to call FairMCApplication::SetSaveCurrentEvent(kFALSE).

To allow this also with CbmTransport it should be enough to allow to add FairTasks to the CbmTransport.

I attached some ample code to the issue which shows how such a Task should look like together with a transport macro in the old style without CbmTransport.

Thanks for the info. Yes, I was aware of that thanks to David. Adding a task is the simplest solution.

The design goes one step further, introducing a default filter class which allows to set cuts on the minimum number of data objects of a given type, without the user having to write a class.

For any more complicated event selection prescription, a class deriving from CbmMCEventFilter and re-implementing the method Bool_t SelectEvent() is required. The mother class already connects to the MC data branches. The data are accessible through GetData(ECbmDataType, index), the size of their arrays through GetNofData(ECbmDataType).

The functionality is implemented with r14714.

The default event filter allows to set cuts on the minimal number of MC objects (MCTrack, MCPoint) in the event. The respective method is

void CbmTransport::SetEventFilterMinNofData(ECbmDataType, Int_t)

If more advanced filtering logic is wanted, a class deriving from CbmMCEventFilter has to be created, which re-implements the virtual method Bool_t CbmMCEventFilter::SelectEvent() const. The user filter class has to be registered to CbmTransport by

void CbmTransport::SetEventFilter(std::unique_ptr<CbmMCEventFilter>& filter)

David, could you test this for your application (mCBM simulation)?

No feedback. I close the issue, hoping it works all right.