Just ran into (not for the first time) a disk completely filling up because users were unaware how full it was getting, and now (after making some space) the cryosparc database won’t start properly. The database issue I will try to figure out separately, but in general I think it would be very useful to:
Warn users when the disk where the current project resides starts getting full (with a user-settable threshold, say 0.5TB)
Add an option to automatically put the instance into admin mode (no new jobs) if there is less than a certain amount of disk space remaining.
Would be useful, although you keep your processing and database on the same mount? How large is the database?
I dodged something similar to this recently; a new postdoc started a motion correction run up on a system with [not enough space]… I spotted it when the drive had about 20GB left. As I really didn’t feel like making them waste the time to redo motion correction of the 13,000 micrographs which had already been completed, some rapid cleanup of other projects made just enough room for the motion correction job to complete.
Can’t say I was super happy, but all life is a learning process.
A “continue” option would be very useful for motion correction, too!
Agreed, we’ve already requested in the past the ability to set global defaults for certain options. I think the team are working on it.
Actually, upsampling 2 is quite useful, although it does catch some users by surprise. I’ve had a rush of samples recently which have hit physical Nyquist at our “normal” mag with me barely trying. It’s always fun to hit <1.8A from data which would top out at 1.9A. That said, if RBMC had the option with EER to resample the input, we could work at 4K and move to 8K if necessary…
That said, if RBMC had the option with EER to resample the input, we could work at 4K and move to 8K if necessary…