Make inference object serializable #617
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #476
Saving the inference object was always a bit messy. But
dill
used to work.I just tried and could no longer save the inference object with dill. The workaround in this PR is to set the non-serializable objects to
None
before saving. This allows to save the inference object withpickle
. These modifications lead to the following two changes in behaviour:.train(..., retrain_from_scratch=True)
does not work after loading..train()
method, it generates a new tensorboard summary writer (instead of appending to the current one).