-
Notifications
You must be signed in to change notification settings - Fork 29
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
Save to file after each event #58
Conversation
@peter-madigan for some reason I can't add you as a reviewer but I would appreciate if you could take a quick look. |
Unfortunately the sometimes-empty events of the official "ND-LAr+TMS" simulation seem to be causing a problem here:
|
Can you try now @chenel? |
Progress! I now get through the first 262 events of my ~10K event sample. Unfortunately I'm running out of memory now on my ~11GB VRAM GPU. :( I'm going to try on a machine with a better GPU (more VRAM), but I post this here just in case it is evidence something else might be wrong... |
sad panda. about 30% through file (event 2634/8581):
I don't see any other output for this particular event. |
Sorry for the slow response - I don't have my computer with me this week, but I'll take a look as soon as I'm back. |
@chenel can you send me the path of your input file? when it crashes, does the file contains the events simulated so far? |
(for the record, file was sent via Slack. there is an output file, which is generally healthy, but it's missing the |
Ok there was a missing check in the pixel finding algorithm. Now it should work, let me know if it doesn't. |
I'll set a test running. |
So close!
Did I miss updating something somehow? |
Oops, I forgot to open the file before writing a config, now it should work 🤞 |
Victory at last! Finished successfully and file seems to be healthy. 🎉 |
Those are trigger packets, not just event dividers, you can have more than one per event. I'll merge this and eventually investigate more. |
This PR changes the way we save the result of the simulation to file by doing it after each event, and not at the end of the full simulation. Fixes issue #57, but it's slightly less efficient, since it has to copy from the GPU memory after each event.