Skip to content
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

It's annoying that a question's maximum score can't be determined without running it #1070

Open
christianp opened this issue Dec 19, 2023 · 0 comments
Labels
Difficult! Issues that will take a long time to implement, or involve big breaking changes Needs thinking about

Comments

@christianp
Copy link
Member

The maximum score available for any of the multiple choice part types is determined by looking at the marking matrix.

In real use, the maximum score should be the same for every student, so it should be possible to determine it from the question definition, without generating an instance of the question.

Fairly often, a multiple choice part has the "marks" field for each choice filled in with an expression like award(1, scenario=N). It's not straightforward to read the maximum possible value out of these expressions.

There is a maxMarks property of the m_n_2 and m_n_x part types which is unset by default. We could insist on this being set, but that would break a lot of existing questions.

I can't see a way of resolving this. It might just be a design mistake that we have to live with.

@christianp christianp added Needs thinking about Difficult! Issues that will take a long time to implement, or involve big breaking changes labels Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficult! Issues that will take a long time to implement, or involve big breaking changes Needs thinking about
Projects
None yet
Development

No branches or pull requests

1 participant