Opened 7 years ago

Last modified 6 years ago

#799 assigned enhancement

Warn users if they are asking DREAM for too many samples

Reported by: pkienzle Owned by: ajj
Priority: major Milestone: SasView 5.0.0
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing


Users are confused about the difference between "Samples", "Steps" and "Burn-in Steps" in DREAM. They are increasing #samples to unreasonable levels instead of using burn-in. This can cause the user inteface to fail after DREAM has spent days collecting samples when it tries to create plots with ridiculous numbers of samples.


Samples is the number of samples to save. From this we can derive #steps = #samples/(#pars*#pop) + 1.

If steps is greater than zero then samples is ignored.

Total number of steps is #burn + #steps.

On completion, all but the final steps are saved, so even if you hit stop before burn is complete you still get #steps*#pop*#pars samples (or less if fewer than #steps iterations have passed before you hit stop).

To do

(1) Make sure the explanation is clear in the documentation, tool tips and help

(2) Warn users if they are asking for more than 1M samples, or maybe limit users to 1M samples unless they are running from the command line.


(1) Revise inputs:

Samples: #samples used for stats; does not change iterations
Steps: #iterations to run; if running a fit without changing the model, use resume so that it collects more data points without having to go through a burn-in period

(2) Show minimum steps required to collect the desired number of samples

Change History (3)

comment:1 Changed 7 years ago by butler

  • Owner set to ajj
  • Status changed from new to assigned

Andrew to see if he can get into bumps and make the string change to GUI — Paul K can help guide

comment:2 Changed 7 years ago by butler

  • Milestone changed from SasView 4.1.0 to SasView 4.2.0

As discussed at Tuesday meeting Andrew will not have time to work on this for release 4.1 so moving to 4.2

comment:3 Changed 6 years ago by butler

  • Milestone changed from SasView 4.2.0 to SasView 5.0.0
Note: See TracTickets for help on using tickets.