Closed merrygoat closed 3 months ago
From my testing, it looks like this occurs only when Expected particles
is set to 1 during the detection process, which is also backed by your logs:
[06/28 15:08:56] RodTracker.ui.loggerwidget INFO: (gp3, 500) Detected 8 rods. ... [06/28 15:09:08] RodTracker.ui.loggerwidget INFO: (gp3, 501) Detected 8 rods.
From the error message, it seems, that a loss of dimension occurs during the extraction of 3D rod position for the 3D display, which then leads to the displayed indexing error.
Ah - that is what I did wrong. Even though 1 is probably not a sensible input value, that seems to be resolved now.
Describe the bug When running particle detection an error dialog appears with IndexError. This does not seem to stop the particle detection process. The error can be triggered repeatedly by scrolling through the images during a detection.
To Reproduce Load test image set. In detection tab, "load default model". Set particles to 25. Press detect button. After some particles have been detected, use the arrow keys to navigate through images. Error dialog is shown.
Additional context This is something to do with rod tracker attempting to display the overlay of the detected particles. I am not sure if it is caused by attempting to display an overlay while that image is being processed or attempting to display an overlay on an image immediately after it is processed.
The error dialog is confusing as you would expect a modal error dialog box to indicate that a process has failed - however detection continues in the background. I guess that this is because the dialog is coming from the gui thread rather than the detection thread.
If you can't address the underlying issue, I would suggest changing this error to a warning or info level message as it does not affect the process of detection.
Logs