Tamas Vami
Tamas Vami
> how is it that the BDT requires MIP tracking nowadays? that's the "mip" in "segmip" :P I think our plan is to have: * package that makes the variables...
(sorry Danyi, I think we typed at the same time! [but at least we are saying the same thing :D ])
I ran a version where MIP tracking is set to -1 for the BDT input in both signal and bkg: https://github.com/LDMX-Software/ldmx-sw/actions/runs/11320865028 The results are not terrible, but clearly I need...
Here is the breakup below of how long things take. With this we'll really just decouple the MIP tracking i.e from `mip_tracking_setup` to `set_variables` and keep the rest as it...
We could try to have more functions it the EcalVeto, but w/o the tracking it's a 500 lines of code so it's not too bad. There is a lot of...
Idk maybe it's fine to do what you propose, let's come back to it after we took up the MIP tracking
Yes, this seems to be already in a good shape, will you PR it?
I think our approach to this is to have the ROOT update as discussed in https://github.com/LDMX-Software/docker/issues/102 After that's done, we should come back to this issue.
@tomeichlersmith just for cleanup, can you please delete the `1232-use-denv-in-ldmx-env` branch?
Hey @jpasc27 what's missing for this issue? I only see the trigger update connected to this, was there anything else? And is there anything else to be updated?