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

Keep track of the fail rate for each question #13

Open
EndBug opened this issue Apr 13, 2022 · 3 comments
Open

Keep track of the fail rate for each question #13

EndBug opened this issue Apr 13, 2022 · 3 comments
Labels
type: chore Code changes that neither fix bugs nor add features (refactoring, dependency chnages, ...)
Milestone

Comments

@EndBug
Copy link
Member

EndBug commented Apr 13, 2022

Proposal author: @Mattysal
It would be nice to have some stats on the most failed questions, in order to better focus on those topics.

@EndBug EndBug added the type: chore Code changes that neither fix bugs nor add features (refactoring, dependency chnages, ...) label Apr 13, 2022
@EndBug EndBug added this to the Future milestone Sep 27, 2022
@lorenzocorallo
Copy link
Contributor

Regarding this one, do we already have some sort of database to store such informations?
My idea is to add two counters for each question (using id reference), one storing how many times is shown and the other one storing how many times is answered wrong, so that we can calculate the error percentage.

@zagbc
Copy link
Contributor

zagbc commented Apr 29, 2023

Nope. Or not a real RDBMS, so far.

Please also take a look at the attached proposal, which is an extension of your nice idea.

These informations could be used to set the Project Team's priorities regarding development of freshman support materials.

I can assure you that we will discuss this improvement action in the near future ;)

Stats

@lorenzocorallo
Copy link
Contributor

Your proposal is great.
Our IT team should discuss on which DB to choose and how to run it.

The frontend part is just a call to the DB at the end, so it would not need much time.

I also thought to set a test score threshold (like 20%) to identify correctly done tests and avoid false positives in our data; in this way we also avoid dirtying the stats during our tests.

@lorenzocorallo lorenzocorallo changed the title chore: keep track of the fail rate for each question Keep track of the fail rate for each question Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore Code changes that neither fix bugs nor add features (refactoring, dependency chnages, ...)
Projects
None yet
Development

No branches or pull requests

3 participants