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.

Sign up for GitHub

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

Jump to bottom

Add support for training data & statistical answer classification #207

Closed
BenHenning opened this issue Oct 6, 2019 · 3 comments · Fixed by #4928
Closed

Add support for training data & statistical answer classification #207

BenHenning opened this issue Oct 6, 2019 · 3 comments · Fixed by #4928
Assignees
@seanlip
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

See https://github.com/oppia/oppia/blob/edb62f/core/templates/dev/head/pages/exploration-player-page/services/answer-classification.service.ts for context. We should add support for training data & statistical classification for answers.
@BenHenning BenHenning added this to the Backlog milestone Jun 23, 2020
@Broppia Broppia added issue_type_feature Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 29, 2022
@BenHenning
Copy link
Member Author

Neither of these are needed right now, and we can revisit this if statistical classification is needed in the future.

@BenHenning BenHenning closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
@BenHenning BenHenning added the Z-ibt Temporary label for Ben to keep track of issues he's triaged. label Sep 16, 2022
@github-actions github-actions bot reopened this Sep 16, 2022
@github-actions
Copy link

The issue is reopened because of the following unresolved TODOs:

oppia-android/domain/src/main/java/org/oppia/android/domain/classify/AnswerClassificationController.kt

Line 38 in f99fa1d

// TODO(#207): Add support for additional classification types.

@BenHenning
Copy link
Member Author

The AI here is to remove that TODO and close this issue.

@BenHenning BenHenning removed this from the Backlog milestone Sep 16, 2022
@seanlip seanlip self-assigned this Mar 29, 2023
@seanlip seanlip mentioned this issue Mar 29, 2023
Merged
6 tasks
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_type_enhancement labels Mar 29, 2023
Uticodes pushed a commit to Uticodes/oppia-android that referenced this issue Apr 4, 2023
@seanlip @Uticodes
Fix oppia#248, oppia#501, oppia#179, oppia#762, oppia#207: Remove obs…
9a747f5 
…olete TODOs. (oppia#4928)

## Explanation

Fixes oppia#248
Fixes oppia#501
Fixes oppia#179
Fixes oppia#762
Fixes oppia#207

This PR removes some obsolete TODOs so that the corresponding issues on
GitHub can be properly closed.

## Essential Checklist
<!-- Please tick the relevant boxes by putting an "x" in them. -->
- [x] The PR title and explanation each start with "Fix #bugnum: " (If
this PR fixes part of an issue, prefix the title with "Fix part of
#bugnum: ...".)
- [x] Any changes to
[scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets)
files have their rationale included in the PR explanation.
- [x] The PR follows the [style
guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide).
- [x] The PR does not contain any unnecessary code changes from Android
Studio
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)).
- [x] The PR is made from a branch that's **not** called "develop" and
is up-to-date with "develop".
- [x] The PR is **assigned** to the appropriate reviewers
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@seanlip seanlip

Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #248, #501, #179, #762, #207: Remove obsolete TODOs. oppia/oppia-android
3 participants
@seanlip @BenHenning @Broppia