weird 1s or -1s diff margin for some trains in output table

[maelysLeratRosso]

What happened?

On this train, I require a margin, and add no requested time except for the departure time. So the calculated margin should be the same as the theoretical margin since no time constrains it. But I see a 1s ou -1s diff margin in some cases, which looks like a rounding problem ?

What did you expect to happen?

I expected the same margins and thus a 0s diff margin

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

Import this train on France infra and observe the first line

timetable (44).json

On which environments the bug occurs?

Dev (SNCF)

On which browser the bug occurs?

Google Chrome

OSRD version (top right corner Account button > Informations)

4ed89f0

[maelysLeratRosso]

Don't know if it's front or back so I label both front and core

[MacOS]

I would take a look at this if no one else would.

[clarani]

Thank you very much for your message @MacOS. You’re welcome to take a look if you’d like (you can assign the issue to yourself).

Based on the calculations, there may be a difference of up to 2 seconds between the requested value and the actual result, but this is considered acceptable. The frontend should be updated so that the table does not display margin differences of less than 2 seconds.
You can check the useOutputTableData hook, which prepares the table data.

Feel free to reach out if you have any questions! :)