You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// normalize all values against total weight and assign values
constextents=arr.extents(row_totals);
data.forEach((d,i)=>{
config.data[i]['weighted sum']=(
(d.score-extents[0])/
(extents[1]-extents[0])
).toString();
});
Whereas the norm parameter only controls normalization of the input data normalization.
In my opinion the default behavior should be to normalize neither, because it isn't something that I as a user would expect when I call a "weightedSum" operation. At the very least there should be an option to disable both forms of normalization
Edit: Just noticed there's the additional "score" property that isn't normalized. I guess that does what I want, but still think this behavior is strange
The text was updated successfully, but these errors were encountered:
Thanks for your request! It's been awhile since I've worked on this project and I don't have much time to maintain it at this point. However, if you'd like to submit a quick pull request, I'd be happy to review it and get something merged.
Hopefully the "score" property has been working for you in the meantime!
I would like to have a weighted sum without any normalization, but that doesn't seem to be possible.
As can be seen here, normalization is still applied to the weighted sum range at the end:
parasol-es/src/api/weightedSum.js
Lines 48 to 55 in 31fcdae
Whereas the norm parameter only controls normalization of the input data normalization.
In my opinion the default behavior should be to normalize neither, because it isn't something that I as a user would expect when I call a "weightedSum" operation. At the very least there should be an option to disable both forms of normalization
Edit: Just noticed there's the additional "score" property that isn't normalized. I guess that does what I want, but still think this behavior is strange
The text was updated successfully, but these errors were encountered: