OpenRailAssociation / OpenRailAssociation/osrd
stdcm: when no pathfinding is found, give precise reasons to help fixing the pathfinding
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 660
- Forks
- 87
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 269
Description
Who would benefit from this feature?
End users
What is this feature about?
- adding a more helpful message when pathfinding doesn't find a solution
Why is this feature valuable?
Here is a simple example. When trying to do a Miramas -> Perrigny with a rolling stock "15000 - BB 15000", the pathfinding fails to find a solution. But in reality, it's only a rolling stock problem because obviously, there are possible paths between Miramas and Perrigny. Maybe the message could be improve to list some possible options to try to find a path (change the rolling stock, change the CH of some Operational Point, etc...).
Anything else people should know?
No response
Contributor guide
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 locating the stdcm pathfinding entry point and the handling for cases where no solution is found. Determine how failures such as rolling stock or Operational Point CH constraints can be distinguished, and define the helpful reasons or options that the resulting message should report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100