The Support stat is a measurement of player altruism and contribution to the collective.
It is represented as a percentage, up to 2 decimal places.
The support stat is the mean of three sub-stats:
Learning Support
Culture Contribution
Reviewer Stat
Data Sources
Retrospective answers to questions
X contributed positively to our team culture = CULTURE_CONTRIB (1..7)
X supported me in learning my craft = LEARNING_SUPPORT (1..7)
Completed project reviews
No. of reviews is an indicator of support = NO_REVIEWS (int)
Ratio of reviews completed to (projects completed * 2) = REVIEW_RATIO (decimal)
Maximum REVIEW_RATIO for chapter = MAX_REVIEW_RATIO
Calculation
Culture Contribution
Find CULTURE_CONTRIB scores for each project
Weight by hours worked on project (more hours = greater weight)
Weight by recency of project (more recent = greater weight)
Aggregate all scores into mean, then convert to % (/ by 7)
Learning Support
Find LEARNING_SUPPORT scores for each project
Weight by hours worked on project (more hours = greater weight)
Weight by recency of project (more recent = greater weight)
Aggregate all scores into mean, then convert to % (/ by 7)
Review Stat
Find REVIEW_RATIO
Find MAX_REVIEW_RATIO
Compare REVIEW_RATIO to MAX_REVIEW_RATIO, convert to %
This is the Review Stat
To make the full Support stat, find the mean of the above three stats.
On weighting
The Learning Support and Culture Contribution stats should be weighted to ensure that these stats are balanced by the amt. of time the player spent on a project (so that scores in a 4-hour and a 100-hour contribution are not considered equal) as well as the recency of the project (so that recent changes are reflected boldly to the player, and early scores don't overly influence the aggregate).
I'm no statistician, so I'd love suggestions/feedback on how to do this best. My initial idea for weighting is:
Multiply each Likert score in proj by (no. of hours in project + cycle no. for player)
Sum the above for all projects
Divide result by total (hours + cycleNo) across all projects
@tannerwelsh, I'm going to remove this from #111 and this can be part of the next round of stats that we work on. Unless you think it's ready, in which case, please add it back to #111 and then move it into the To-Do lane with the rest of the stats stuff.
@tannerwelsh commented on Tue Jun 21 2016
The Support stat is a measurement of player altruism and contribution to the collective.
It is represented as a percentage, up to 2 decimal places.
The support stat is the mean of three sub-stats:
Data Sources
X contributed positively to our team culture
= CULTURE_CONTRIB (1..7)X supported me in learning my craft
= LEARNING_SUPPORT (1..7)Calculation
Culture Contribution
Learning Support
Review Stat
To make the full Support stat, find the mean of the above three stats.
On weighting
The Learning Support and Culture Contribution stats should be weighted to ensure that these stats are balanced by the amt. of time the player spent on a project (so that scores in a 4-hour and a 100-hour contribution are not considered equal) as well as the recency of the project (so that recent changes are reflected boldly to the player, and early scores don't overly influence the aggregate).
I'm no statistician, so I'd love suggestions/feedback on how to do this best. My initial idea for weighting is:
Example:
original: https://github.com/LearnersGuild/learning-os-software/issues/85
@tannerwelsh commented on Fri Jul 29 2016
IGNORE: NO LONGER VALID (just keeping for historical reference)
Example implementation of calculation:
@tannerwelsh commented on Fri Jul 08 2016
@shereefb I took a first stab at the calculation of Support Stat. What do you think?
@shereefb commented on Wed Jul 27 2016
Don't we also need to weigh this by the number of total dev hours for the project?
@tannerwelsh commented on Tue Jul 19 2016
@shereefb yup, that should go into this as well. Shouldn't be too hard to adjust the above to match, I just need to consider it a bit longer.
@jeffreywescott commented on Wed Jul 27 2016
@tannerwelsh, I'm going to remove this from #111 and this can be part of the next round of stats that we work on. Unless you think it's ready, in which case, please add it back to #111 and then move it into the To-Do lane with the rest of the stats stuff.
@tannerwelsh commented on Thu Jul 28 2016
Thanks @jeffreywescott - I need to figure out how to incorporate an hourly weight into this number, and then I'll bump it back up.
@tannerwelsh commented on Fri Jul 29 2016
@shereefb what do you think of the changes to the support calculation (now includes hours)? If you like it, please move to Backlog.
@shereefb commented on Wed Aug 03 2016
@prattsj I moved this back to Design/Spec. Still needs some work (from me) before it's ready for todo. Were you planning on working on it today?
@prattsj commented on Wed Aug 03 2016
@shereefb: ok. Need an answer on whether you want to hold player stats DMs until it's worked out or release without them.
@shereefb commented on Tue Aug 09 2016