Skip to content

Traceability for progression algorithms #7

Description

@Schroedingberg

What problem does this solve?

As a user I might sometimes be surprised by a decision the algorithm makes.
I would like to be able to see a trace of how the decision for e g. Removing a set was made.

Proposed solution

The minimal solution is probably to be able to see the event history for an exercise.
That way I can at least see what feedback I have given in the past which may have led to a surprise.
That will allow me to give better feedback for improving the algorithm

Alternatives considered

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions