strange score if I use grader and then submit

[Alex-Jordan]

I noticed a few odd things while playing with the problem grader just now. In a course, set up a new assignment (I used the Student Orientation) and set the dates so that it is open. Now go to problem 1, and show the grader. Enter 50%, and click Save. Now click "Problem 1" in the left navigation panel to reload the problem.

Now that I have 50% for the exercise, I would expect to see that down in the #score_summary, but I don't. I haven't looked but I assume it's because I haven't attempted the exercise yet. If that's right, it should be easy to change. But next is where things get weird. Leave the answer blank, and click Submit. Now the score summary says I have 67%. Indeed, that is my score if I look elsewhere, like in Grades.

I repeated this on a different exercise with 5 answer blanks, again using the grader to give myself 50%. Then I correctly answered two questions before clicking Submit, so I should have 40% for that submission. But again my final score is set tat 67%. Or if use like 10% when setting my own score, clicking Submit with all empty answers makes 13% as the final score.

[drgrice1]

I am not seeing everything that you are seeing. I do see that the score is not shown in the #score_summary until there is an attempt on the exercise. But I am not seeing the 67% after submitting an answer. If I follow your instructions, then the 50% appears in the Grades (even without a submission), but after the submission with an empty answer the #score_summary also shows 50%. I tried it with a problem with 3 answers, and 50% is still shown. I also tested with the student orientation set.

[Alex-Jordan]

OK, I see this behavior if I check out main. Maybe relevant that I pulled including all the main hotfixes.

I don't see it with develop. I don't see it with the 2.20 tags.

Have you tried it on main? If not, I will keep digging.

[drgrice1]

I originally tested with develop. However, I tested again now with main (with all hotfixes), and I still don't see the odd scores.

[Alex-Jordan]

Alright, I'll start probing config settings.

[Alex-Jordan]

OK, I have to stop now for local home stuff. But it's something to do with having a reduced scoring date. The last things I did that brought back the bad behavior are put these in simple.conf:

$pg{ansEvalDefaults}{enableReducedScoring} = 1;
$LTISendGradesEarlyThreshold = '0.7';

which did not bring back the bad behavior. But then for the set, set Reduced Scoring Enabled to "yes". And then the bad behavior returned.

This is on main, but now I don't have reason to suspect it won't also happen with develop. I'd keep looking tonight but I have to shut down computer stuff :)

[drgrice1]

I do see the problem with reduced scoring enabled for the set. This has nothing to do with whether the student has answered the problem or not. Start with problem that the user has answered, but received 0 points for that answer, change the grade to 50% using the problem grader, the user then submits an answer that should also receive 0 points, and the student's score gets changed to 67% (assuming $pg{ansEvalDefaults}{reducedScoringValue} is 0.75).

The issue is that the unreduced score that is computed when the status is 0.5 and the sub_status is 0 is 0.5/0.75 = 0.67 (rounding to two decimal places of course). So that is what is passed to PG as the recorded score, and since the student receives 0 points which is less, that is what comes back as the recorded score also.

I am looking into what to do about this.