You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/quickstart.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -655,7 +655,7 @@ If you used the pool in the sampler and you want to use the pool after restoring
655
655
sampler.run_nested(resume=True)
656
656
657
657
You should be careful when restoring the sampler on machine with different number of CPUs when using a pool.
658
-
We will try to update the queue_size based on what is the pool size.
658
+
We will still use the original queue_size unless it was 1 before.
659
659
660
660
The checkpointing may be helpful if you are running dynesty on HPC with a queue system that has a limit on a wall-time that your jobs can run.
661
661
There is a however an important reminder that should *NOT* use checkpointing for persistence. I.e. if you want to save the results of the sampling, you should save samples, weights or the results object, rather than the whole nested sampling object (as checkpointing does). The reason for this is that the checkpoint files are not guaranteed to be compatible between dynesty versions (even minor ones).
0 commit comments