This was discussed at our June 22 meeting, and is not an issue specific to floability, but I'll post here so we can find a solution.
Notebooks with long execution times
Some workflows can take >8 hours (in this case, the physics-lfv backpack with extra data). It's likely that the ssh session used to launch floability will close before the vine jobs have completed. When this happens, progress will be lost as the Jupyter notebook state is not saved.
This was discussed at our June 22 meeting, and is not an issue specific to floability, but I'll post here so we can find a solution.
Notebooks with long execution times
Some workflows can take >8 hours (in this case, the physics-lfv backpack with extra data). It's likely that the ssh session used to launch floability will close before the vine jobs have completed. When this happens, progress will be lost as the Jupyter notebook state is not saved.