GENIE interface working well, possible to write easy event selections

LM: what about the interaction stage? i.e. vertex level or post FSI?

DG: no, is there a variable that does this?

SD: there is a code called "ist" which gives the state of the particle in the interaction. When you generate GENIE you get GHEP ststaus file, in the output there is a collumn which has thinngs like FM, LM etc, there is also a label called ist, and that corresponds to the state of the interaction. I think it is important to propagate.

DG: i see. When we propagate particles in the detector we only select final state variables, from other states we only get the neutrino flavor and energy. 

SD: I think we still want to keep all the truth info for the particle, even if it doesn't interface with the detector simulation. We should keep as much as possible from the GHEP record, it will be useful in the future for reweighting and deeper studies. 

DG: ok, i will think about introducing an extra tree. That should be easy. 

LM: are those all the interaction processes? The list seems a bit incomplete

DG: this is the full list. 

LM: How is the information on particle kinematics stored?

DG: you can use this with the product_pdg information. 

SD: we want to be able to access the true particle kinematics further downstream. When we want to look at this further downstream we want to be able to access the full 4 vectors of all final state particles. 

DG: we do propagate the MC truth for the event, this is just for propagating a subset of events to the simulation

SD: oh i see! 

DG: but I do think adding some kinematics as selection criteria, like momentum of FS particles.

Luca:

LM: is this ready to run on LXPLUS? Can Anna begin running it?

DG: haven't tested on lxplus. Should be easy. Luca has some output. I will install it on lxplus and should be very easy to run. I will provide also an example script for the batch submission. you should be subscried to np-comp