You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the testbeam data analysis development, we used a separate path for hit and cluster reconstruction (with producers called TestBeamHitProducer... etc) compared to in the usual LDMX simulations. It would be great to make one producer work for both cases. The real difference is that there are quality flags set in data, and potentially some other info that we need to propagate. There is also no truth info like the beam electron fraction of the hit energy deposition. If the isData_ boolean gets set properly, we could likely deal with theses minor differences in a single producer for hits and clusters, respectively. This will help getting us ready for data taking, too.
The text was updated successfully, but these errors were encountered:
In the testbeam data analysis development, we used a separate path for hit and cluster reconstruction (with producers called
TestBeamHitProducer...
etc) compared to in the usual LDMX simulations. It would be great to make one producer work for both cases. The real difference is that there are quality flags set in data, and potentially some other info that we need to propagate. There is also no truth info like the beam electron fraction of the hit energy deposition. If the isData_ boolean gets set properly, we could likely deal with theses minor differences in a single producer for hits and clusters, respectively. This will help getting us ready for data taking, too.The text was updated successfully, but these errors were encountered: