MRSP from TrackAtals to DMI

[Farhangi]

Hello @JakobGartner !

For the correct display of the "Speed profile discontinuity" on the DMI:

• either MSRPs(from TrackAtlas) includes the current section,
• or DMI should store the current MRSP.

[stefan-karg]

Dear Peyman,

Jakob is already working on a correction of this issue. There is currently a little bug in the calculation of the MRSP for the DMI. This will be resolved today.

[ghost]

When reducing the MRSP sections (merging sections with equal speed limits), Track Atlas kept the last section instead of the first. This lead to the speed profile apparently start in front of the train and/ or displaying wrong speed.

This has been corrected with the last commit

[BaseliyosJacob]

@Farhangi ,

in the design phase of the DMI we agree not to store any MRSP in the DMI Controller. All MRSP information will be stored on the Track Atlas and the DMI receives the "current speed profiles" from the track atlas, which will be stored until a new information is valid.

This storagefunction is already implementent. In this case the Track Atlas is always responsible for the correct Speed profile.

[JakobGartner]

This is done on TrackAtlas side

No change required on DMI side

On 23.11.2015, at 09:24, Baseliyos Jacob notifications@github.com wrote:

@Farhangi ,

in the design phase of the DMI we agree not to store any MRSP in the DMI Controller. All MRSP information will be stored on the Track Atlas and the DMI receives the "current speed profiles" from the track atlas, which will be stored until a new information is valid.

This storagefunction is already implementent. In this case the Track Atlas is always responsible for the correct Speed profile.

— Reply to this email directly or view it on GitHub.

[JakobGartner]

can't we close this?

[Farhangi]

Correction is available.