bryngemark
bryngemark
In my mind, PF needs to know how to do the stitching between objects at system boundaries. So it makes sense if the actual implementation of particle flow is responsible...
good catch, configurable input collection and pass names, and output collection names, should be standard for all processors in my opinion
@tvami @vdutta let's go over this in the sw dev on Oct 1.
hey @tillrue, i just started [a PR](https://github.com/LDMX-Software/ldmx-sw/pull/1856) with some work i did over summer. since you are anyway going to have to resolve conflicts, it's better to rebase to `trunk`...
Hi Sam, if your PR is ready for review (necessary before it gets merged), you need to pick at least two reviewers who will take a look and approve when...
> I have talked to Dr. James Oyang, @joyang8caltech, and he agreed to run some simulations using this geometry. Dr. Oyang, I forked a version of ldmx-sw into my github...
By the way @zwl0331, @joyang8caltech, the plastic geometry doesn't look right. We expect to have 24 bars in each plastics array, so they are equal height but staggered in _y_.
thanks @zwl0331 for sharing your config file! as you can see this was a great way to catch some issues with your validation procedure. in addition to what @tomeichlersmith has...
thanks @tvami, those are some good points. @zwl0331 how is this coming along?
@tvami LOL yes that _z_ distribution is telling. All interactions in the first possible instance!