In the same way that running with save_predictions=False can be useful to avoid filling up database space, it would be useful to add optional behavior to delete model objects (maybe matrices as well?) from disk after they're done being used to save space avoid disk full issues during large, exploratory runs.
The main downside here, of course, is making it more expensive to resume an experiment after a crash mid-run, but it might be a reasonable trade-off.
In the same way that running with
save_predictions=Falsecan be useful to avoid filling up database space, it would be useful to add optional behavior to delete model objects (maybe matrices as well?) from disk after they're done being used to save space avoid disk full issues during large, exploratory runs.The main downside here, of course, is making it more expensive to resume an experiment after a crash mid-run, but it might be a reasonable trade-off.