-
Notifications
You must be signed in to change notification settings - Fork 268
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
Neighbormatrix fails to compute for geometry with a single pixel #2316
Comments
Minimal example:
|
You see the error you posted with a matrix with 77 pixels? Are you sure? I get the exact same error only for 1 pixel in the CameraGeometry. |
Here a more complete log:
code:
It apparently crashes on the 25th event, which has this huge Masked CameraGeometry array. In case of good events, the event count is printed both before and after morphology_parameters() (as for event 23). This is the first event that makes the script crash... (Sorry, again) |
@Elisa-Visentin I see that in the stage1 tool, we pass the full geometry to the morphology parameter calculation. I need to check if that is required or just an accident, but could you try the same? Pass the full geometry, not the goemetry selected (only for the morphology parameters) |
By passing the full geometry (not masked) it works! |
@Elisa-Visentin Please stop apologizing 😉 You identified a valid issue and we need to fix that. At the very least, this is not properly documented but it still might be a bug that we need to fix! |
With a full geometry, even the warnings disappear; maybe this is due to scipy (csr_matrix). But adding a note in the docs could help (and solve the problem).
I must go back to exploit somebody else for questions/issues... 😅 |
Fix neighbor matrix for no pixels, fixes #2316
Discussed in #2309
Originally posted by Elisa-Visentin April 19, 2023
Hi,
Sorry for the banal question but... While computing morphology parameters (
morphology_parameters(...)
) on a set of images withctapipe 0.19.0
, some of the events make the script crash with the following error lineswhereas other events (same script, same input file) are well reconstructed or only return a warning
which needs this
if
to be executed.Maybe some events need a lot of memory to be processed? Or are there some 'anomalous' images on which the
morphology_parameters
algorithm fails? Other issues (dependencies...)?Thanks.
The text was updated successfully, but these errors were encountered: