-
Notifications
You must be signed in to change notification settings - Fork 16
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
Develop #91
Merged
Merged
Develop #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… the backtracking dataset for calib_final_hits
Backtracking for prompt hits
…in yaml to change back
…coordinates e.g. pixel_xy, anode_z, and get_z_coordinate.
…_load_charge_geometry method.
…te_regions methods of proto_nd_flow/resources/geometry.py.
…o geometry_info flow dataset in proto_nd_flow.
…idation tests of method.
…to_nd_flow Geometry module.
…ounds, module_RO_bounds, max_drift_distance, and cathode_thickness attrs and remove drift_regions attr.
…thod in proto_nd_flow Geometry module.
…ts from [mm] to [cm].
…ng Geometry module testing infrastructure.
update the geometry script to match with the module0 one
Remove large initialised arrays
…ts_datasets Add io_group and io_channel to calib_prompt_hits and calib_final_hits datasets
…d in proto_nd_flow Geometry module.
…rge_geometry method in proto_nd_flow Geometry module.
…nto remote geometry resource charge fix feature branch.
…_hit_merging Feature/ehinkle require same iogroup hit merging
Feature triggerlogic
…coord_fix Feature/ehinkle geo resource charge coord fix
edhinkle
approved these changes
Dec 20, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the changes from develop
require a change to a parameter in the proto_nd_flow single module event display to reflect that the positional information in the raw_hits dataset is now in [cm] vs. [mm]. I will make this change after merging the PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.