doloresgarcia / tracking_dc Goto Github PK

The runIDEAtrackerDigitizer needs to be changed to add this relation

Do you see sometimes simHit (or equivalently digi hit if it is easier for you to check) that have the same cellID ? This would also be possible because I think (hope) ddsim does this gathering of simHit into one contribution kind of locally or within a single mother history, otherwise, in the drift chamber, we would have simHit 2 meters away from each other that get combined together

We are working on implementing a dedicated sensitive action for drift chamber in ddsim (we are still using the one for silicon trackers) but it will take time

Need to produce an energy distribution plot per pid

Now we store parents to check if there are hits from the parents and merge.
But it is a bit complicated but "I have the impression that ddsim is gathering all Geant4 simHit from a given sensitive volume into one simHit whose position is a weighted average and energy is the sum of energy. But if a particle decays inside this volume and create new ones, a choice has to be made on to which particle to attach the hit

the behavior can be changed but in the other scenario, we will have many simHit per cell (and hence many digis, at least with the current code assuming one simHit per cell) and we are not ready (at all) to digest such scenarios which require a detailed drift chamber digitizer "

is this possible for you to manually reassign a different id in case of the V?

Another option would be:
Before to go for complicated manual V finding algorithm, I'd propose to see what happens with the ddsim option: --action.tracker Geant4TrackerAction