Even more linking consistency errors on track

openETCS / modeling

WP3 Top Level Project: to cover all tasks related with modeling

31 stars 42 forks source link

Even more linking consistency errors on track #926

Closed UweSteinkeFromSiemens closed 8 years ago

UweSteinkeFromSiemens commented 8 years ago

While traveling along the track, the following linking consistency errors occur:

BG 389: BGpassedInUnexpectedDirection, afterwards linkedBGMissed (= not found until the end of the expectation window).
BG 0: announced between BG 400 and 401, then later linkedBGMissed (I'm not sure, if this is not an unintended zombie BG)
BG 397 linkedBGMissed, then passedBG_foundNotWhereExpected
BGs 402, 403, 404, 405 passedBG_foundNotWhereExpected, then linkedBGMissed

The track requires to be adjusted, since more consistency errors are to be expected ahead otherwise.

BerndHekele commented 8 years ago

I will follow-up on this issue. @JakobGartner : the correction of BG 0 in the linking data is not on Github yet.

BerndHekele commented 8 years ago

You find the BG 0 in the following constants: LRBG371_P005. I did not see any other.

JakobGartner commented 8 years ago

This is done.

Again, this is wrong already in the recorded JRU data.

It is possible that this correction may also correct the following references (as they are incremental)

I wait for the next report for looking deeper.

It is unlikely that “so many” linking refs are wrong independently

On 19 Nov 2015, at 09:08, Bernd Hekele notifications@github.com wrote:

You find the BG 0 in the following constants: LRBG371_P005. I did not see any other.

— Reply to this email directly or view it on GitHub https://github.com/openETCS/modeling/issues/926#issuecomment-157984872.

BerndHekele commented 8 years ago

Update after integration of corrections:

BG389 is passed in wrong direction (Linking is nominal, track is reverse)
BG397 misplaced (nominal 1600988):
BG403 (nominal 1885952):

JakobGartner commented 8 years ago

We will check.

According to our XREF document with repositioned/ corrected BGs

On 19 Nov 2015, at 18:07, Bernd Hekele notifications@github.com wrote:

Update after integration of corrections:

BG389 is passed in wrong direction (Linking is nominal, track is reverse)

This should be nominal. We check the linking data

BG397 misplaced (nominal 1600988): https://cloud.githubusercontent.com/assets/3288918/11276992/b33b935a-8ee4-11e5-97b3-a0b19f280234.png

The calculated pos (abs) should be around 15992

BG403 (nominal 1885952): https://cloud.githubusercontent.com/assets/3288918/11277329/6faee57c-8ee6-11e5-865a-26ade800b419.png The calculated pos (abs) should be around 18943

we will review the linking data.

— Reply to this email directly or view it on GitHub https://github.com/openETCS/modeling/issues/926#issuecomment-158120900.

BerndHekele commented 8 years ago

Can you provide a correction for BG397 in the track-atlas please, Jakob.

BerndHekele commented 8 years ago

I did not see any problems in the past. I close this issue.