OpenRailAssociation / OpenRailAssociation/osrd

front: display block states on the map in the simulation results

Open
#3,744 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🖼️ design area:front component:signaling kind:feature-task
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?

#3473 dropped the display of route_occupancies on the map, since routes don't correspond to blocks anymore.

Why is this feature valuable?

We need to bring back a display of block states in a correct way regarding the new, more accurate signaling model.

Anything else people should know?

Projections have to be taken into account. The blocks that are simulated may not follow the path of the train if it differs from the current projection path. Or the backend could simulated and return both set of states.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing #3473 and the current simulation-results map behavior related to route_occupancies. Trace how projections and simulated block states are represented, then determine which states the map should display when a train's simulated path differs from its current projection path. Done means block states are shown correctly for these projection cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.