Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Train schedule travel time isn't updated in timetable when adding margin #6695

Closed
SharglutDev opened this issue Feb 21, 2024 · 4 comments · Fixed by #6899
Closed

Train schedule travel time isn't updated in timetable when adding margin #6695

SharglutDev opened this issue Feb 21, 2024 · 4 comments · Fixed by #6899
Assignees
Labels
area:editoast Work on Editoast Service difficulty:good first issue Good for newcomers from:users Something reported directly by the users kind:bug Something isn't working module:operational-studies Multi-train simulation with structured studies management severity:minor Minor severity bug

Comments

@SharglutDev
Copy link
Contributor

SharglutDev commented Feb 21, 2024

What happened?

In a scenario, when adding margin to a train, the travel time of this train and the time arrival in the timetable aren't updated accordingly.

What did you expect to happen?

The travel time and arrival time should be updated when adding a margin.

How can we reproduce it (as minimally and precisely as possible)?

  1. Go to a scenario
  2. Toggle the timetable trains details by clicking on the eye icon at the top and check the travel time
  3. Modify a train and add some margins
  4. Check again the travel time and arrival time of the train, it hasn't changed

What operating system, browser and environment are you using?

  • Browser: Firefox v123
  • OS: macOS Sonoma
  • Env: Dev

OSRD version (top right corner Account button > Informations)

dev f7339f1

@SharglutDev SharglutDev added kind:bug Something isn't working area:front Work on Standard OSRD Interface modules severity:minor Minor severity bug module:operational-studies Multi-train simulation with structured studies management labels Feb 21, 2024
@axrolld
Copy link
Contributor

axrolld commented Feb 21, 2024

This is a bigger problem in this part of the project : we keep considering the fastest drive as the reference, which in my opinion should not be the case. I want to make sure this is actually the case, and if so create an issue accordingly :)

@axrolld axrolld changed the title Train schedule travel time isn't updated in timetable when adding margin WIP: Train schedule travel time isn't updated in timetable when adding margin Feb 21, 2024
@axrolld axrolld added the postponed Postponed task due to other priorities or waiting for dependencies label Feb 21, 2024
@SharglutDev SharglutDev changed the title WIP: Train schedule travel time isn't updated in timetable when adding margin Train schedule travel time isn't updated in timetable when adding margin Mar 13, 2024
@SharglutDev SharglutDev added the from:users Something reported directly by the users label Mar 13, 2024
@bgiuliana
Copy link
Contributor

I aggree with you. The reference should be the travel time including margins. In addition, being this modifications proposed by users, I suggest to fix it at least for the timetable part. We will check the other parts of the application later.

@SharglutDev SharglutDev self-assigned this Mar 13, 2024
@SharglutDev
Copy link
Contributor Author

Actually, it seems to be a back issue. The get timetable endpoint returns the arrival time based on the base simulation.

@SharglutDev SharglutDev added difficulty:good first issue Good for newcomers area:editoast Work on Editoast Service and removed postponed Postponed task due to other priorities or waiting for dependencies area:front Work on Standard OSRD Interface modules labels Mar 13, 2024
@SharglutDev SharglutDev removed their assignment Mar 14, 2024
@axrolld
Copy link
Contributor

axrolld commented Mar 14, 2024

I suggest fixing this also, if you think it's relevant to do it now:
image

The default should be ECO if some margin is added. And actually ECO isn't quite the right naming. Could we name it MARGIN ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:editoast Work on Editoast Service difficulty:good first issue Good for newcomers from:users Something reported directly by the users kind:bug Something isn't working module:operational-studies Multi-train simulation with structured studies management severity:minor Minor severity bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants