Hi Fabian-san,
we ran into a strange problem with PACEtomo and wanted to ask if you have seen something similar before.
I have a question about "checkDewar = True" state.
When we stop a running PACEtomo acquisition and then try to restart it (using the recovery option), SerialEM shows the error in the attached screenshot and the script aborts.
This error:
• does not occur for a completely new PACEtomo run, and
• disappears when we disable the Dewar Refilling Manager script in SerialEM.
We did a bit more testing and found that the error also disappears when we set
checkDewar = False
in the PACEtomo settings.
In other words, the error seems to occur only when:
1. we try to recover a stopped PACEtomo run, and
2. both the Dewar Refilling Manager and PACEtomo’s checkDewar logic are active.
This makes us suspect that there might be a conflict between PACEtomo’s dewar-related handling
(checkDewar, cryoARM, coldFEG / checkFilling()) and the Dewar Refilling Manager script, especially around LongOperation / dewar state handling.
Do you have any recommendations for using PACEtomo together with the Dewar Refilling Manager?
For example, would you suggest always setting checkDewar = False (and maybe cryoARM = False, coldFEG = False) when an external Dewar manager is running, or is there a better way to combine both?
Best wishes,
Hi Fabian-san,
we ran into a strange problem with PACEtomo and wanted to ask if you have seen something similar before.
I have a question about "checkDewar = True" state.
When we stop a running PACEtomo acquisition and then try to restart it (using the recovery option), SerialEM shows the error in the attached screenshot and the script aborts.
This error:
• does not occur for a completely new PACEtomo run, and
• disappears when we disable the Dewar Refilling Manager script in SerialEM.
We did a bit more testing and found that the error also disappears when we set
checkDewar = False
in the PACEtomo settings.
In other words, the error seems to occur only when:
1. we try to recover a stopped PACEtomo run, and
2. both the Dewar Refilling Manager and PACEtomo’s checkDewar logic are active.
This makes us suspect that there might be a conflict between PACEtomo’s dewar-related handling
(checkDewar, cryoARM, coldFEG / checkFilling()) and the Dewar Refilling Manager script, especially around LongOperation / dewar state handling.
Do you have any recommendations for using PACEtomo together with the Dewar Refilling Manager?
For example, would you suggest always setting checkDewar = False (and maybe cryoARM = False, coldFEG = False) when an external Dewar manager is running, or is there a better way to combine both?
Best wishes,