Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

larndsim truth information not updated #216

Open
YifanC opened this issue Mar 15, 2024 · 4 comments
Open

larndsim truth information not updated #216

YifanC opened this issue Mar 15, 2024 · 4 comments

Comments

@YifanC
Copy link
Collaborator

YifanC commented Mar 15, 2024

Brooke reported that in segments dataset, pixel_plane, n_electrons, n_photons are not updated. This is due to a mistake that when we filled the truth information, we didn't use the dataset passed to the simulation with the updated information. This should be fixed in the next iteration of MR5.

@YifanC
Copy link
Collaborator Author

YifanC commented May 9, 2024

If we only pass a subset of the segments, ndlar_flow will complain here: https://github.com/DUNE/ndlar_flow/blob/18a2e26f67cbfc8e00898ec99eb0a5bd3476044a/src/proto_nd_flow/reco/charge/raw_event_generator.py#L470
The fix should be updated along side with the flow fix.

@YifanC
Copy link
Collaborator Author

YifanC commented May 9, 2024

We should also understand why 2x2 active volume selection removes segments and why module active volume selection further removes segments.

@YifanC
Copy link
Collaborator Author

YifanC commented May 30, 2024

Using the first 50events of MR5 00999 file for a test:
In total there are 44873 segments, and 44863 of these are in the larnd defined active volume.
with larndsim commit ebaa36c and ndlar_flow commit 909fbe6, the total number of segments is consistent in larndsim and flow. The maximum of the prompt hit backtracked segment_id in flow is 44833 and in larndsim is 44833. The numbers match, and the hotfix is okay.
Attempting to remove the hotfix with larndsim commit d28f888 and ndlar_flow commit 909fbe6. The number of segments in both larndsim and flow are 44863. Flow didn't trip at the place where I stated above in raw_event_generator. However, if you look at packet/ prompt hit backtracked segment_id, the maximum from larndsim is 44778, while the maximum from flow is 44833. Clearly there's a problem even flow doesn't complain...

@YifanC
Copy link
Collaborator Author

YifanC commented May 31, 2024

https://github.com/DUNE/ndlar_flow/blob/1ff5456cb04d3b2e4ced50dacc358310f9f31191/src/proto_nd_flow/reco/charge/raw_event_generator.py#L456
This shows we use the segment id in packet assn as indices for the reference between packets and segments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant