It appears that WeBWorK rounds the scores sent via LTI to an LMS to the nearest integer.
This happens in line 175 of lib/WeBWorK/Authen/LTIAdvanced/SubmitGrade.pm:
$score = wwRound(2, $score);
While this appears consistent with how rounding is done elsewhere (cf #513) those instances of rounding are for display, rather than calculation. It seems to me that, for numbers which will be used in grade calculations, exactness is preferable, so that rounding occurs just one time when calculating and displaying grades to students through the LMS.
I believe LTI 1.3 allows sending exact scores (separate score & total score) but I am not familiar enough with the compatibility considerations involved in WW's choice to only report percentages. In any case, it seems like sending as many significant figures as the LTI standards allow would suffice. (I acknowledge that even the current rounding scheme almost surely has no effect on student grades, but I can see how it might set off some worry)
It appears that WeBWorK rounds the scores sent via LTI to an LMS to the nearest integer.
This happens in line 175 of lib/WeBWorK/Authen/LTIAdvanced/SubmitGrade.pm:
$score = wwRound(2, $score);While this appears consistent with how rounding is done elsewhere (cf #513) those instances of rounding are for display, rather than calculation. It seems to me that, for numbers which will be used in grade calculations, exactness is preferable, so that rounding occurs just one time when calculating and displaying grades to students through the LMS.
I believe LTI 1.3 allows sending exact scores (separate score & total score) but I am not familiar enough with the compatibility considerations involved in WW's choice to only report percentages. In any case, it seems like sending as many significant figures as the LTI standards allow would suffice. (I acknowledge that even the current rounding scheme almost surely has no effect on student grades, but I can see how it might set off some worry)