Shouldn't handgraded answers be assumed "correct" inside a cascade?

Discussion
1

Currently you can put an <answer> with the handGraded attribute inside a <cascade> with no warnings or errors.
However, this means the users will always be “stuck” within that section of the cascade where the attribute occurs unless/until it gets graded, because that section of the cascade cannot achieve 100% credit until it gets done.

Proposed solution: I think it should be possible to do this, but that the <cascade> component should just assume the text answer is correct if anything is entered into the text box, and allow the student to progress once it is non-empty.

Or, Doenet should throw a big warning or error to the authors.

Thoughts??

Additionally, here’s my current workaround to using handGraded, but I think it’s a bit unweildy.

<p><answer name="reason1" type="text" showCorrectness="false" forceFullCheckWorkButton>
          <textInput name="reason1TextInput" expanded>
            <label>Describe how you know: </label>
          </textInput>
          <award><when>$reason1TextInput.valueChanged</when></award>
        </answer></p>
2

We just released a new dev version that fixes this. If an answer is marked handgraded, then a <cascade> and the calculation for the section title color both behave as though that hand-graded answer is correct as soon as the student submits a non-blank answer.

The actual credit achieved is still calculated with the hand-graded answer receiving no credit.

1 Like
3

Thanks!!!