Closed Seesam24601 closed 1 week ago
Blocked by #3
One possible design consideration for both this issue and #8 is to only provide built-in functionality that is required by the model itself. Since both of these only determine prioritization, which is a user-defined problem, this make may sense to be a documented option or only necessary for using standard TERM LITE prioritization metrics, if they are built in.
Building off a the previous comment, I do not believe that this issue is relevant to the reproducing the core of TERM Lite or creating a demonstration test case. Thus I am closing this issue.
Like in #8, this should be an optional column whose behavior is handled by the prioritization function.