Alexey dev issue404: Addresses a number of situations with data savings when one of the optics fails #174
Conversation
…situation when Exp. aborted by clicking 'STOP' in early stage (not completed)...
There was a problem hiding this comment.
When an optics type (RI or IP) fails in either R&D or GMP, the user is correctly notified of the failure.
For R&D: After importing the data, the user is informed that the successfully collected optics data was saved, while data from the failed optics was not saved.
- Run ID: MartinR_IF-Fail_R-D_Test-3_13JAN25-run2235
- Log file: /rmartin/ultrascan3_tests/IF-Fail_R-D_Test-3_13JAN25
For GMP: After importing the data, the user is notified that although the successfully collected optics data was saved (and the failed optics data was not), the run will not be processed further within the GMP framework due to the optics type failure.
- Run ID: MartinR_IF-Fail_GMP_Test-3_13JAN25-run2234
- Log file: /rmartin/ultrascan3_tests/IF-Fail_GMP_Test-3_13JAN25
In cases where the 'STOP' sequence is initiated from the DA GUI during the ‘Live Update Stage’, the program correctly identifies the optics type failure and presents the user with the option to either ignore or save the data from the aborted run.
R&D:
- Run ID: MartinR_IF-Fail_R-D_Stop_PF-1_16JAN25-run2239
- Log File: /rmartin/ultrascan3_tests/IF-Fail_R-D_Stop_PF-1_16JAN25
GMP:
- Run ID: MartinR_IF-Fail_GMP_Stop_PF-2_16JAN25-run2240
- Log File: /rmartin/ultrascan3_tests/IF-Fail_GMP_Stop_PF-2_16JAN25
These fixes successfully address the issues that prompted the ticket. Both the R&D and GMP programs exhibit the correct and expected behavior.
Tested.