You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the use case that requires this feature.
At the moment, the ctapipe-train-... tools use TableLoader.read_telescope_events to load all telescope events for a given telescope type in one go.
This potentially uses large amounts of memory given that we
Apply quality criteria that will throw away a significant percentage of the events
Only use a subset of the available columns
Sub-sample events if n_events or n_signal / n_background are configured.
Describe the solution you'd like
Load data in smaller chunks, applying the event selection and column selection for each chunk and then merge chunks into the needed big training table to reduce overall memory usage.
The text was updated successfully, but these errors were encountered:
For the quality criteria: pytables has efficient filtering (table.where()) that could also be used to filter events before creating the astropy tables and even before chunking, but that would require some lower-level changes to how data are read and I'm not sure the added complexity is worth it.
Please describe the use case that requires this feature.
At the moment, the
ctapipe-train-...
tools useTableLoader.read_telescope_events
to load all telescope events for a given telescope type in one go.This potentially uses large amounts of memory given that we
n_events
orn_signal
/n_background
are configured.Describe the solution you'd like
Load data in smaller chunks, applying the event selection and column selection for each chunk and then merge chunks into the needed big training table to reduce overall memory usage.
The text was updated successfully, but these errors were encountered: