The model tracer can take multiple start and goal states. Currently, it returns a connections from one start state to one goal state. While this seems to be fine, it may not be the expected behavior. It makes sense that a trace is given if any goal state is reached, but with multiple start states, it could be the case that some do not reach any goal state. This is currently unclear.
See here.
If the user does not care if all start states lead to a goal state, they can simply ignore the additional lines, so we don't need additional functionality there.
Tasks:
Print a connection for EACH start state to ANY goal state for BOTH model tracing algorithms
In the 'no trace available' message, the corresponding start state also has to be mentioned
Print found traces BEFORE states for which none were found
The model tracer can take multiple start and goal states. Currently, it returns a connections from one start state to one goal state. While this seems to be fine, it may not be the expected behavior. It makes sense that a trace is given if any goal state is reached, but with multiple start states, it could be the case that some do not reach any goal state. This is currently unclear. See here.
If the user does not care if all start states lead to a goal state, they can simply ignore the additional lines, so we don't need additional functionality there.
Tasks: