Feedback wanted: Intuitive scoring for just-in-time sets
メンテナーはふだん 4 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
The proposal concerns the jitar_problem_adjusted_status routine in lib/WeBWorK/Utils.pm, where child-problem weights are summed into $childScore. Read that routine and the just-in-time set grading logic first, then decide how a new scoring mode would sit beside the current one. Done would mean a maintainer-agreed design, since the thread has no decision and the issue has been open about four years.
索引モデルが issue の本文から書いたものです。
説明
Problem
The current grading algorithm for just-in-time problem sets is rather unintuitive in my opinion, since for child problems it abuses the meaning of the value field to store some factor which - when considering all child problems which count towards the parent - results in a weight. Also, the points for a child problem shown to the student do not correspond to the actually achievable points if I'm not mistaken.
Solution
It would be better in my opinion if the value field retained its meaning (maximum points to reach for the child problem). The relevant jitar_problem_adjusted_status routine in /lib/WeBWorK/Utils.pm could simply proceed as follows when computing the status of a parent problem:
- Gather the weighted sum of all subproblems (as is currently done and saved in
$childScore) - If this weighted sum is greater than the value of the parent, return one as the status (i.e. when the values of all child problems counting towards the parent problem add up to something at least as large as the value of the parent problem, the score is capped)
- Otherwise divide the weighted sum by the parent problem's value and return the maximum of the result and the parent problem's current status.
Instead of the capping in step two, one could simply consider the case where child problems can yield more points than the parent when combined as illegal and throw an error when the user tries to import or save such a set, but this would unfortunately break backwards compatibility (although I'm sure that everybody will switch to the new algorithm...).
Advantages
In addition to being much more intuitive for the end user, this would also enable to apply penalties when a student reaches the child problems after not being able to solve the parent. With the current algorithm, I see no alternative to the insertion of a dummy child problem (always counted as false).
Instead of the capping in step two, it would be better to consider the case where child problems can yield more points than the parent when combined as illegal and throw an error when the user tries to import or save such a set. However, this would break backwards compatibility.
Implementation
I intend to add another routine for the adjusted status to Utils.pm and then offer either a checkbox labelled “use alternative jit scoring” or a dropdown “scoring algorithm for jit sets” with the current algorithm as default to keep backwards compatibility.
Before implementing this, I'd be thankful for some feedback, in particular whether this has a chance to be included in the main tree as I don't want to maintain a local fork.
- 主要言語
- Perl
- スター
- 164
- フォーク
- 167
- 平均マージ
- 6日 7時間
- マージ済み PR(30日)
- 27
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
openwebwork/webwork2 のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
openwebwork/webwork2#3295 ·
メンテナーはふだん 4 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
openwebwork/webwork2#3290 ·
メンテナーはふだん 4 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 62/100
openwebwork/webwork2#2997 ·
メンテナーはふだん 4 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 56/100
openwebwork/webwork2#3276 ·
メンテナーはふだん 4 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 52/100
openwebwork/webwork2#3272 · コメント 6 件 ·
メンテナーはふだん 4 日以内に返信
openwebwork/webwork2 の issue をすべて見る
似ている issue
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules listオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
Type: Bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
inverse-inc/packetfence#9707 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
RotherOSS/otobo#6457 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ email対応中かも @sisodiaumang が今日担当しました。 オープン🏭 producer platform - spam
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
openfoodfacts/openfoodfacts-server#15447 ·
メンテナーはふだん 1 日以内に返信
-
Harden argument handling in deploy-contract.sh対応中かも @Asta-wizard が 1 日前に担当しました。 オープンStellar Wave
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
Feyisara2108/stellargive#1377 · コメント 3 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信