-
Notifications
You must be signed in to change notification settings - Fork 20
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
Modified metrics should impact score #4
Comments
I think I do not understand correctly how modified env metric is supposed to be used.
|
This may be overly simplistic, but the way I think of it is:
etc. In other words, Modified versions of the Base Metrics completely override the value set for that Base Metric. And as Jono said, MSI and MSA may have to be handled differently (although conceptually the same way) because there are additional values (S) that do not exist in the SI and SA base metrics. |
I think I understand now. I used the following code instead: // All other environmental metrics just overwrite base score values,
// so if they’re not defined just use the base score value.
if(Object.keys(this.selectedValues).includes("M" + metric)) {
modified_selected = this.selectedValues["M" + metric]
if(modified_selected != "X" && modified_selected != "S") {
return value == modified_selected
}
} |
I hope this issues is fixed by 5aa9724 . In case it is not, please let me know. |
When the env metrics are used to modify a base metric value, the score should be calculated as if the env metric is the value.
Note that the following scores, [1] and [2] should have the same output, but in fact [1] and [3] have the same output.
Perhaps something like this added to
checkMetric(metric, value)
for each modified env metric (except MSA and MSI, which are going to need to be special cases because of the way that MSA is the only place Safety can be selected)Lines 124-126 makes sense, but I think it needs something more to account for the env inputs effected the computed score. Perhaps
Sorry, I don't speak javascript very well, but I hope this is intelligible to a human at least.
For MSA and MSI, it it may need to be checked separately, since "S" won't be a legal SA or SI value. Or the macrovector lookup can change to account for this.
The text was updated successfully, but these errors were encountered: