Added event display for npz event files with endcaps

[ABlairJamieson]

Features:

• give geometry file, event file, and event to display as command line arguments
• if files not give, open file dialogs to select the geometry file or event file
• three main windows: Charge, Time, or Charge vs Time selected by pressing button
• button for next event
• text entry to set event number
• button to go to next event (or event set in text entry)
• button and text entry to change z-axis range
• toolbar to zoom and pan in plot

It runs a bit slow, but works.

[ABlairJamieson]

I added a 3d display as well now.

[calum-macdonald33]

@ABlairJamieson would it be possible to retool this to accept the h5 file formats we use in training? It seems straightforward, though we might need to add the 'digi_hits_pmt' variable somehow.

[ABlairJamieson]

Anyone going to merge this in?

[pdeperio]

was previous comment by Calum addressed? @calum-macdonald33 @nickwp anything else required before merging?

[nickwp]

While it would be nice if this could use the h5 format as Calum suggested, only the npz format actually contains the truth information for showing particle tracks, so changing format would limit the features already included. So I think it's fine to merge now and in future could be nice to add functionality for (limited) display of events from h5 files.

[pdeperio]

does this need to be ported to the new https://github.com/WatChMaL/WatChMaL framework?

[ABlairJamieson]

Hi Guys, I think a useful first step for me and Sidney would be to write the h5 format event display as well. It would be useful for checking that the files we build with multiple rings are okay. The updated version could be merged in once ready (in a few weeks?). Blair

…

On Fri, Oct 16, 2020 at 1:40 PM Nick Prouse ***@***.***> wrote: External: This email comes from outside UWinnipeg. Please verify the sender and always use caution with any requests, links, or attachments. While it would be nice if this could use the h5 format as Calum suggested, only the npz format actually contains the truth information for showing particle tracks, so changing format would limit the features already included. So I think it's fine to merge now and in future could be nice to add functionality for (limited) display of events from h5 files. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBZJVLSFBAZDKRR2WRR26LSLCHHZANCNFSM4OBAVR4A> .

-- /*********************************************************************** * Blair Jamieson (he/him/his) email: <bl.jamieson@uwinnipeg.ca> * * Associate Professor, Chair phone: 204-786-9216 * * Department of Physics address: 515 Portage Ave (3L24) * * University of Winnipeg Winnipeg, MB R3B 2E9 * ***********************************************************************/

[nickwp]

Sounds good. Feel free to take a look here to see how we're loading h5 file data in our ML framework, in case you want to reuse this code:
https://github.com/WatChMaL/WatChMaL/blob/master/watchmal/dataset/h5_dataset.py