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

Rating deployed instances #154

Open
hgeorgsch opened this issue Oct 24, 2019 · 2 comments
Open

Rating deployed instances #154

hgeorgsch opened this issue Oct 24, 2019 · 2 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@hgeorgsch
Copy link
Contributor

CAPQuiz rates questions. For question types such as STACK the question is parameterised, and a question is really a class of random instances. This has a couple of potentially negative consequences.

  1. All instances of the same question have the same rating, even if they may have different difficulty.
  2. When parameterised questions are used together with unique questions, instances of the parameterised question come up less frequently than instances of the unique question.

There is no obvious and clear-cut solution to this problem, and every solution is likely to have negative side-effects, but alternatives should be identified and discussed. In particular,

  1. is it possible to rate instances instead of questions? Could this be made optional when setting up the question set?
  2. is it possible to take the number of instances into account in the matchmaking routine, so that questions with many instances come up with higher probability?
@hgeorgsch hgeorgsch added the enhancement New feature or request label Oct 24, 2019
@hgeorgsch
Copy link
Contributor Author

This will take some research and won't easily be fixed.
A feasibility analysis would be useful though.

@hgeorgsch hgeorgsch added wontfix This will not be worked on and removed can wait labels Sep 22, 2020
@hgeorgsch
Copy link
Contributor Author

This only affects a narrow use case. With CAPQuiz we normally want a large number of variants, which creates performance issues with STACK. We have therefore resorted to instantiating questions on the fly, with nothing pregenerated, and in this case instances cannot be graded.

Therefore, we won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant