You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When core returns a successful stdcm response, only the actual train speeds are included. We could have a speed chat with as much information as in the standalone module.
Why is this feature valuable?
It would be much easier to see at first glance where the engineering allowances are located. It's normally hard to tell and near impossible when the MRSP gets complex.
Anything else people should know?
It would be easy to implement on the back-end side of things, but I don't know about the front-end side, I don't even know if there's anything to do there.
The train should not be duplicated in the space-time chart.
The text was updated successfully, but these errors were encountered:
Who would benefit from this feature?
Both
What is this feature about?
When core returns a successful stdcm response, only the actual train speeds are included. We could have a speed chat with as much information as in the standalone module.
Why is this feature valuable?
It would be much easier to see at first glance where the engineering allowances are located. It's normally hard to tell and near impossible when the MRSP gets complex.
Anything else people should know?
It would be easy to implement on the back-end side of things, but I don't know about the front-end side, I don't even know if there's anything to do there.
The train should not be duplicated in the space-time chart.
The text was updated successfully, but these errors were encountered: