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.
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.