run.sh: make full geant track history available to EICrecon

[veprbl]

Few reasons for doing this:

1. This is consistent with what users have set by default (and what is debugged for)
2. Should not cause a significant intermediate file bloat
3. We need this if we want to start enabling associations not with just status=1 particles

[Chao1009]

Agreed.

[wdconinc]

Can you quantify 2? That relies on our definition of the tracking volume, right? How securely is that associated with something that is never going to be a calorimeter? I want to avoid two scenarios, which may not apply now but maybe in the future:

• npsim should not start storing all optical photons in the DIRC and RICH detectors.
• Changes in calorimeter or tracking definitions, for example around the first layer of the BIC, should not lead to shower particles being stored.

Also related to @rahmans1 adding average event size and cumulative size on disk as one of the performance metrics we track for simulation production campaign datasets.

[wdconinc]

@rahmans1 Can you look into the CI failure here too? I think it's not parsing the epic version correctly.

[veprbl]

With 1TeV cut

6.9M	dis_cc_1TeV/sim.edm4hep.root

without any cut

7.6M	dis_cc_none/sim.edm4hep.root

without any cut, tracking region extends everywhere

16M	dis_cc_none_everything/sim.edm4hep.root