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.

Sign up for GitHub

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

Feature/ehinkle eventdisplay #81

Merged
merged 11 commits into from
Oct 19, 2023
Merged

Feature/ehinkle eventdisplay #81

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
28d4a4e
Adding single module event displays.
Sep 22, 2023
799ba4d
Adding Jupyter notebooks showing how to use single module event displ…
Sep 22, 2023
303aed9
Creating README.md
edhinkle Sep 22, 2023
4d99b0d
Updating event display example notebooks.
Sep 22, 2023
fbb7550
Adding README to remote.
Sep 22, 2023
950b5c2
Updating README with link to original code.
Sep 22, 2023
a346082
Save minor modifications to proto_nd_flow single module event display.
Sep 27, 2023
14929f6
Update event_display README with online location of Module 1 charge o…
Oct 3, 2023
1e89d05
Allow tracklet plotting in proto_nd_flow event display with calib_fin…
Oct 5, 2023
e4c9d64
Add capability to plot tracklets dataset created from calib_prompt_hits.
Oct 6, 2023
4929458
Final changes to proto_nd_flow tracklet display notebook.
Oct 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions event_display/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Flow File Event Displays

## Single Module Event Displays

### Overview

There are currently two Python-based event displays available for visualizing single module data and simulation files run through flow. The event displays are version-specific, with one intended for use on files run through `module0_flow` and one for use on files run through `proto_nd_flow`. The source code for each event display is available in the corresponding subdirectory, e.g. `event_display/proto_nd_flow`, and is adapted from [this older event display script](https://github.com/larpix/larpix-v2-testing-scripts/blob/master/event-display/module0_evd.py). The event displays here are set up to run inside Jupyter notebooks, and examples of such usage are also given in the corresponding subdirectories. The examples involve using files stored on NERSC, so if the notebooks are run outside of NERSC, you will need to download both the flow file you would like to visualize and a module geometry file.

### File Locations

In general, single module data files can be found [in this file system.](https://portal.nersc.gov/project/dune/data/) For the examples provided in the associated notebooks, the following files are used:

- [Module 1 geometry file](https://portal.nersc.gov/project/dune/data/Module1/TPC12/module1_layout-2.3.16.yaml)
- [Module 1 data file run through `module0_flow` (charge only)](https://portal.nersc.gov/project/dune/data/Module1/reco/charge_only/events_2022_02_09_17_23_09_CET.gz.h5)
- [Module 1 data file run through `proto_nd_flow` (charge only)](https://portal.nersc.gov/project/dune/data/Module1/TPC12/reflow-test/packet_2022_02_09_17_23_09_CET.module1_flow.h5)

Additional Module 1 charge-only data files run through `module0_flow` can be found [here](https://portal.nersc.gov/project/dune/data/Module1/reco/charge_only/), and additional Module 1 charge-only data files run through `proto_nd_flow` can be found [here](https://portal.nersc.gov/project/dune/data/Module1/TPC12/reflow-test/).
Loading