New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Always on param math changes #8

Open

atiselsts wants to merge 1 commit into feature/params-always-never from feature/always-on-param-math

Owner

atiselsts commented Aug 23, 2021

When optimizing a model with always-on parameters, the parameters are included in the ranges as usual.

The problem: for example, if there are 2 always-on parameters, and the parameter selection strategry is configured as:

"parameters": [{
	"type": "exhaustive",
	"range": [1, 2]
}]

then only one optimization job will be created. If there are 3 always-on parameters, then with the above config no jobs will be created.

This PR changes this behavior to effectively use this dynamic parameter selection range instead:

 range: [1 + number_of_always_on_parameters, 2 + number_of_always_on_parameters]


          update the strategy to count parameters differently when always on pa…

f6ccbcb

…rameters are present

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet