OpenRailAssociation / OpenRailAssociation/osrd
Separate universal signalling systems and the ones requiring specific embedded hardware + handle retrocompatibility
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 660
- Forks
- 87
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 269
Description
Description and goal
Currently BAL, BAPR, TVM300, and TVM430 are modeled the same way. However there's a significant difference between those systems : BAL and BAPR work passively with every rolling stock authorized to drive on the French railway network, while TVM requires specific hardware within the rolling stock in order to be able to drive.
The goal is to adapt the signalization model, differenciating systems universals for a given network, and others requiring specific hardware, which can be edited in the RS editor.
Also we need to allow retrocompatibility between systems, as it's the case with TVM430 and TVM300.
Acceptance criteria
- Rolling stocks compatible with TVM 430 can drive on TVM 300 lines.
- other criterias TBD
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 tracing the signalization model and the rolling-stock editor described in the issue. Identify where BAL, BAPR, TVM300, and TVM430 compatibility is represented, then review the TVM430-on-TVM300 acceptance criterion. The work is done when the model distinguishes universal systems from hardware-dependent ones and the stated retrocompatibility behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100