-
Notifications
You must be signed in to change notification settings - Fork 9
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
Impact Weighting - automatic lower bounds for Total impact #160
Comments
Yes that is interesting and I am wondering about the incentives that it would embody, basically not encouraging GDE's to spend the time updating their activity details. I need to spend some time designing an approach to automated data collection that is not a burden on the GDE's. |
I believe that if estimates used are strict lower bounds to what a user would enter manually (i.e. there's no way a user would be entering a lower value), then you definitely won't incentivise users to not update their information. It might slightly reduce the incentive for users to actually manually update their information - but I'm not sure if that's a significant detriment. |
You are right no doubt. New scoring came live today. Let's set what Galen's On Fri, 5 Dec 2014 17:23 timwintle notifications@github.com wrote:
|
(Thought while watching your talk..)
If the impact weightings are dramatically affected by having a total impact value at all, then a lower bound can be added for calculations, which would improve the accuracy of results where people have been able to enter activities..
For example for G+,
lower_estimate(total_impact) = max(plus_ones, reshares)
(Other bounds available for other tracking event types)
The text was updated successfully, but these errors were encountered: