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
{{ message }}
Repository navigation
Flag bootstrapping argument to be changed to allow parameter uncertainty #329
As a brief follow up and documenting of ideas at meeting 2026-01-27, we noted that:
Paramters.bootstrapAll is false by default
This needs enabled for multiruns to bootstrap for parameter uncertainty
The user may not know that this is the case (missing from documentation)
Possible small changes to better handle this:
Add in bootstrapping to wiki
Parameter bootstrapAll could be de-finalised and made modifiable in config file and CLI args (via multirun class)
For multiruns the parameter could be set to true (and left as-is for GUI runs)
OR, could set a warning flag in console in multiruns to alert the user that no bootstrapping is ideal for development environment but this should be enabled for valid statistical outputs
A few possible changes which can easily be made. Can discuss ongoing!
@matteorichiardi@dav-sonn This is the issue that was just discussed in today's meeting regarding bootstrapping - it is still listed as in progress on the SimPaths development board, so I didn't think opening a new issue seemed appropriate.
The current state of the code is that bootstrapAll is always true, in other words bootstrapping is always on, even for single runs. I don't know if this was intended or not, but from today's discussion I gather it's likely not.
I recall that we previously discussed a few possible solutions in a development meeting, including:
Making bootstrapping configurable, either through a CLI argument or the config YAML file
Making bootstrapping-on the default for multiruns only, but keeping bootstrapping-off as the default for single runs
The latter might be the most straightforward - e.g. by adding a static method Parameters.setBootstrapAll analogous to the existing Parameters.setTrainingFlag, which can be called in SimPathsStart and SimPathsMultiRun to set different values (the final keyword would need to be removed from the bootstrapAll declaration).
Activity
igelstorm commentedon Oct 27, 2026
@matteorichiardi @dav-sonn This is the issue that was just discussed in today's meeting regarding bootstrapping - it is still listed as in progress on the SimPaths development board, so I didn't think opening a new issue seemed appropriate.
The current state of the code is that
bootstrapAllis alwaystrue, in other words bootstrapping is always on, even for single runs. I don't know if this was intended or not, but from today's discussion I gather it's likely not.I recall that we previously discussed a few possible solutions in a development meeting, including:
The latter might be the most straightforward - e.g. by adding a static method
Parameters.setBootstrapAllanalogous to the existingParameters.setTrainingFlag, which can be called inSimPathsStartandSimPathsMultiRunto set different values (thefinalkeyword would need to be removed from thebootstrapAlldeclaration).andrewbaxter439 commentedon Oct 27, 2026
A suggested approach implemented in #549