-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Morris experiments may set parameters out of bounds #367
Labels
Comments
I tried to reproduce with the example from the library (Exploration.gaml) with the following modifications with no success. experiment batch_abstract type:batch virtual:true until:(time > end_cycle) {
init {is_batch <- true;}
parameter "Predator energy transfer:" var: predator_energy_transfer min: 0.0 max: 1.0;
parameter "Predator energy reproduce:" var: predator_energy_reproduce min: 0.0 max: 1.0;
}
experiment Morris parent: batch_abstract type: batch until:( time > 2 ) {
init {
assert predator_energy_transfer <= 1.0;
assert predator_energy_reproduce <= 1.0;
}
method morris outputs:[] sample:100 levels:4 report:"Results/morris.txt" results:"Results/morris_raw.csv";
} |
lesquoyb
added
😱 Bug
The issue reveals a bug in GAMA
About Batch
This issue concerns batch experiments
labels
Oct 30, 2024
chapuisk
added a commit
that referenced
this issue
Nov 1, 2024
Hey @ScriBanana, I dig a bit in the sampling method and "mistakes were made". The problem should be solve as soon as the PR #369 has been reviewed and accepted. |
Hi @chapuisk, |
lesquoyb
added a commit
that referenced
this issue
Nov 4, 2024
…-set-parameters-out-of-bounds Solves #367 by reimplementing morris sampling method following SALib implementation to avoid parameters getting out of bounds
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hi,
Describe the bug
Morris experiment sometimes sets parameters to values outside their assigned bounds. In particular, above 1.0 for a float with bounds 0.0 and 1.0. The parameter value in "Parameters to explore" gives the maximum value instead of the erroneous value taken by the parameter, as can be verified in the console or an assert statement, for example.
I have had no such issue with other exploration methods (Sobol or OFAT).
To Reproduce
And check the value of the failed parameter in the console.
The text was updated successfully, but these errors were encountered: