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
In the acquisition job processor, the function that moves around the acq file does not work as expected.
The acq is moved to the done folder even if an error happens during the pxCov or binMov calculation, because the acq-moving function is only triggered if the processCurrentAcq function exits (i.e. only for non-caught errors). It would be better to use the onCleanup object just for the user-abort case (Ctrl-C) and otherwise keep track if errors were caught. If there were errors, the acq file should be moved to the error folder, not to the done folder. The acq file should even be moved to error if Ctrl+C was pressed but a "real" error had happened previously during processing, so that the user is alerted to the fact that there was an error.
The text was updated successfully, but these errors were encountered:
In the acquisition job processor, the function that moves around the acq file does not work as expected.
The acq is moved to the done folder even if an error happens during the pxCov or binMov calculation, because the acq-moving function is only triggered if the processCurrentAcq function exits (i.e. only for non-caught errors). It would be better to use the onCleanup object just for the user-abort case (Ctrl-C) and otherwise keep track if errors were caught. If there were errors, the acq file should be moved to the error folder, not to the done folder. The acq file should even be moved to error if Ctrl+C was pressed but a "real" error had happened previously during processing, so that the user is alerted to the fact that there was an error.
The text was updated successfully, but these errors were encountered: