-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checkpointer cannot serialize functions to disk with JLD. #141
Comments
If we cannot serialize functions (or structures of functions) to disk at all then we might have to force users to reinsert all functions when restoring from a checkpoint. We can do the FFT plans automatically but we have no idea what the e.g. forcing functions might be. But this is ugly and it'll be easy to make a mistake so I'd rather be able to serialize functions to disk. |
Helps avoid #141 when forcing functions aren't used.
|
|
Closing as it seems that serializing functions to disk in Julia is impossible (well, probably just difficult/unreliable). |
I agree that this issue should have been closed... but just to throw a wrench into things: |
Ah nice. Probably worth trying if we stick with serializing the full |
Also of note are |
I cannot get the checkpointing test running in PR #140 as JLD is not able to serialize the model to disk with forcing functions. We can go back to forcing arrays but we I think that's a bad idea as we should avoid increasing GPU memory usage.
I believe that JLD2.jl might be able to serialize functions to disk but it's not actively maintained anymore and their README says "If your tolerance for data loss is low, JLD may be a better choice at this time."
If we can fix this and figure out how to serialize functions to disk, then we may also be able to serialize the FFTW and CuFFT plans to disk (although we might still want to reconstruct them as in case the model is restored on a different computer with a different architecture).
Stacktrace:
The text was updated successfully, but these errors were encountered: