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

Some of the achievements do not behave as expected #1327

Open
robert-marik opened this issue Apr 15, 2021 · 3 comments
Open

Some of the achievements do not behave as expected #1327

robert-marik opened this issue Apr 15, 2021 · 3 comments

Comments

@robert-marik
Copy link
Contributor

robert-marik commented Apr 15, 2021

Some of the achievements do not behave as expected, so I think that we should keep the information somewhere. Many issues are fixed in 2.16 and the teachers who use achievements should consider to upgrade.

Some issues remained:

  • The achievements super_speed_math and speed_mather are obtained if the set is solved fast. However, the time gets reset when the user submits answer from another set. So if there are more than one set opened (which is often the case) and user switches between them, these achievements do not work as expected. I believe that it is required to track (save) the first submission for each set separately. However not sure if there is enough space in frozen_hash. There could be many sets with long ids.
    • Still open
  • Night owl and related achievements do not use the course timezone. The server timezone is used.
  • If you use UTF-8 characters in the achievement description or student names, you may have problems with import/export.
  • If the set where students learn to work with WeBWorK should not count to achievements, the documentation suggests to use the preable.at file. However, the answers still count to the total score.
@taniwallach
Copy link
Member

set_id can be up to 100 characters (80 in WW 2.15); longer names would fail to be recorded in the past_answers table, and trigger errors. Since there can me many sets, it certainly seems that frozen_hash as a varchar(1024) is to small to store data on many assignments. If this is an issue overall - it could potentially be made larger.

Another option might be to Maybe the coursename_setting column can be used to store the data you want for super_speed_math and speed_mather?

@taniwallach
Copy link
Member

The issues with super_speed_math and speed_mather need to be addressed in the future. The rest were fixed for WW 2.16.
Moving to a different project board for the rest.

@robert-marik
Copy link
Contributor Author

robert-marik commented Jul 9, 2021

Thank you for suggestions. I am not sure about the optimal method to resolve the problem. I would like to keep the data in the table related to achievements. Another option it to query past answers and find the oldest one in the current subset. But I am not sure if this is accessible from achievement evaluation environment. Anyway, since there have been many bugs in achievements for many years, apparently not many people use these features and there is no pressure to fix this minor issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants