-
Notifications
You must be signed in to change notification settings - Fork 7
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
Memory issues when running event coincidence on merged LST-1 DL1 files #128
Comments
while I guess you can distinguish the merged file by having multiple subrun numbers, I am not sure if this is a proper approach. Maybe it would be better to check the number of events in the file because the actual memory limit should be directly related to that one. The error message might however include the information not to run over merged files |
I have found that it is possible to adapt the code to use only a limited number of lst events at a time. Looping over all events by slice of a pre-defined step. |
Last week Axel reported that he had some jobs for the event coincidence failing with a memory issue (too much memory requested). We found out the problem happened because the event coincidence was run over LST-1 merged DL1 files. In such a case, the number of events is too large when performing the coincidence, and it causes the script to exit with an error similar to:
Therefore, it would be ideal to check the input file and exit if it is a merged DL1 file.
The text was updated successfully, but these errors were encountered: