Skip to content

Latest commit

 

History

History
203 lines (142 loc) · 7.18 KB

fitting_option.rst

File metadata and controls

203 lines (142 loc) · 7.18 KB

Fitting Options

Options that control the benchmarking process are set here.

Software (software)

Software is used to select the fitting software to benchmark, this should be a newline-separated list. Available options are:

Default software options are scipy and scipy_ls

[FITTING]
software: bumps
          dfo
          minuit
          scipy
          scipy_ls
          scipy_go

Warning

Software must be listed to be here to be run. Any minimizers set in :ref:`minimizer_option` will not be run if the software is not also present in this list.

Number of minimizer runs (num_runs)

Sets the number of runs to average each fit over.

Default is 5

[FITTING]
num_runs: 5

Algorithm type (algorithm_type)

This is used to select what type of algorithm is used within a specific software. For a full list of available minimizers for each algorithm type, see :ref:`minimizer_types`. The options are:

Default is all

[FITTING]
algorithm_type: all

Warning

Choosing an option other than all may deselect certain minimizers set in the options file

Jacobian method (jac_method)

This sets the Jacobian used. Choosing multiple options via a new line seperated list will result in all combinations being benchmarked. Current Jacobian methods are:

Default is default

[FITTING]
jac_method: scipy

Warning

Currently analytic Jacobians are only available for problems that use the cutest and NIST parsers.

Hessian method (hes_method)

This sets the Hessian used. Choosing multiple options via a new line seperated list will result in all combinations being benchmarked. Current Hessian methods are:

Default is default

[FITTING]
hes_method: default

Warning

Currently analytic Hessians are only available for problems that use the cutest and NIST parsers.

Cost function (cost_func_type)

This sets the cost functions to be used for the given data. Choosing multiple options via a new line seperated list will result in all combinations being benchmarked. Currently supported cost functions are:

Default is weighted_nlls

[FITTING]
cost_func_type: weighted_nlls

Maximum Runtime (max_runtime)

This sets the maximum runtime a minimizer has to solve one benchmark problem num_runs number of times, where num_runs is another option a user can set. If the minimizer is still running after the maximum time has elapsed, then this result will be skipped and FitBenchmarking will move on to the next minimizer / benchmark dataset combination. The main purpose of this option is to get to result tables quicker by limit the runtime.

max_runtime is set by specifying a number in unit of seconds. Please note that depending on platform the time specified with max_runtime may not match entirely with the absolute run-times specified in tables. Hence you may have to experiment a bit with this option to get the cutoff you want.

Default is 600 seconds

[FITTING]
max_runtime: 600