Please describe the use case that requires this feature.
To replace the narrowly scoped and quite limited ctapipe-display-dl1 and be able to just use everything done in ctapipe-process, we should add a EventDisplay component, which could be an abstract interface to allow multiple implementations (e.g. matplotlib / qt or bokeh in the browser).
It should have two modes: going through the events manually (i.e. stopping the event loop until the user clicks "next") or just displaying events as they are processed.
Should have mutliple tabs for the different data levels:
[ ] Raw data exploration. Waveforms, dl1 image, etc.
[ ] Reconstruction, e.g. what @kosack started here: #2539
Should be invoked with ctapipe-process -i <path> --display for example.
Please describe the use case that requires this feature.
To replace the narrowly scoped and quite limited
ctapipe-display-dl1and be able to just use everything done inctapipe-process, we should add aEventDisplaycomponent, which could be an abstract interface to allow multiple implementations (e.g. matplotlib / qt or bokeh in the browser).It should have two modes: going through the events manually (i.e. stopping the event loop until the user clicks "next") or just displaying events as they are processed.
Should have mutliple tabs for the different data levels:
Should be invoked with
ctapipe-process -i <path> --displayfor example.