-
Notifications
You must be signed in to change notification settings - Fork 14
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
Scaling up: weight for the suitability index can be set to 0 #324
Comments
I'm in favor of keeping the possibility for weight of zero: when you have a complex scaleup model with several suitability index, you may want to test alternatives results by skipping out one of the index. By indicating zero or its weight, this will do and avoids the need to re-enter it later on. Also, with the forthcoming Docker version (and later the command-line version of AccessMod), we'll be able to do parameter space exploration for uncertainty and sensitivity analyses, and the possibility of having wights of zero might be important there. |
Skipping one of the index is currently done by unchecking it in the "select" column of the suitability factors table and I think that this makes more sense than setting a weight to "0". In any case, we should have only one way to do this. If you still want to go for the possibility to set the weight to 0 then we will need to:
|
coming back to this old issue we should keep the possibility to use "0", and should indeed have the possibility to change the weights directly in the suitability factor table. |
Current Behavior
You can set the weight to 0 for any of the suitability index
Expected Behavior
The weight can only be set between 1 and 10
Possible Solution
Limit the weight to values between 1 and 10
Steps to Reproduce
You get an error message (see screenshot below) but you should not even be able to specify 0 in the first place
Detailed Description
None
The text was updated successfully, but these errors were encountered: