Regain possibility to do MC truth handling for TPC digits manually#385
Regain possibility to do MC truth handling for TPC digits manually#385sawenzel merged 1 commit intoAliceO2Group:devfrom
Conversation
219df6b to
845360d
Compare
There was a problem hiding this comment.
Why not simply using a struct as the key?
struct MCID{
unsigned int eventId : 15; // 32k event Id possible
unsigned int trackId: 17; // 128K tracks possible
};
Also why using a map rather than a sorted vector with key and value in the same bitfield?
struct MCIDValue {
unsigned int eventId : 15; // 32k event Id possible
unsigned int trackId: 17; // 128K tracks possible
unsigned int occurences : 32; // 4G occurrences possible
}
std::vector<MCID> mMCID;this has the added value you can use less bits for the occurrences and should be almost two orders of magnitude more compact.
There was a problem hiding this comment.
What you say is correct and it has been discussed in similar form among the TPC developers already. However, this commit merely "reverts" to what was already available before ... just to debug and compare to the FairLinks. I will add your comments as future ideas.
* Needed in order to be able to test/debug/evaluate approaches based on FairLinks (solution based on compile time switches) * Small adjustment to TPC runscript: Offer possibility to use Box generator or GeneratorFromFile @authors: Andreas Matthis, Sandro Wenzel
845360d to
b0b1a01
Compare
wiechula
left a comment
There was a problem hiding this comment.
For me it is fine, please go ahead
* foundBC index added to EvSel table * foundFT0, foundFV0 and foundBC as index columns
Needed in order to be able to test/debug/evaluate
approaches based on FairLinks (solution based on compile time switches)
Small adjustment to TPC runscript: Offer
possibility to use Box generator or GeneratorFromFile
@authors: Andreas Matthis, Sandro Wenzel