Standardize Task Cost Matrix
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
There is no standard or reasonable input validation for cost matrices right now. This leads to bad matrices such as “yes”, “adam”, or “1”.
We need to define what a valid cost matrix looks like, and add input validation for new tasks with cost matrices.
We might want to convert or delete old tasks with cost matrices (depending on how interpretable they are).
This might be most convenient to process when working on task 2.0, but can be done independently.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the task 2.0 work and the task-creation path to find where cost matrices are accepted. Define the valid matrix shape and validation behavior, then add coverage for new task submissions; handling existing tasks is a separate decision noted in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100