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: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
7
7
[Unreleased]
8
8
### Added
9
9
### Changed
10
+
- Show the ETA and expected number of iterations when sampling.
10
11
- When restoring the sampler with the pool, use an updated value of `queue_size` based on the pool size
11
12
- Use `chunksize=1` for the dynesty pool, as that is better behaved for `queue_size > nthreads` and unequal durations of function evaluations
12
13
- When starting dynesty with a multiprocessing pool, dynesty now tries to use the `_processes` keyword to determine how many CPUs are available. This should reduce the need for manual `queue_size` specification
13
14
### Fixed
15
+
- Previously when restoring a saved sampler and starting running the it/s speeds shown in the progress bar were incorrect, because they did not take into account the previously evaluated iterations.
Copy file name to clipboardExpand all lines: docs/source/faq.rst
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -261,6 +261,11 @@ with (3) a large number of varying live points can make the stopping criteria
261
261
difficult to evaluate quickly. See
262
262
:ref:`Nested Sampling Errors` for additional details.
263
263
264
+
**When fitting, the estimated time of sampling varies a lot from iteration to
265
+
iteration**
266
+
267
+
This is normal. There is no way to accurately know how many iterations of nested sampling will be needed and how long it will take. The estimate of total time is particularly uncertaintain in the beginning of the sampling. The time can also jump significantly every time a new location of the in the posterior with a particularly high log(l) value is discovered.
0 commit comments