openETCS / modeling

WP3 Top Level Project: to cover all tasks related with modeling
31 stars 42 forks source link

Test report #919

Closed Farhangi closed 8 years ago

Farhangi commented 8 years ago

3602 m: image 4359 m flag speed chang target at speed zero

image

LRBG: 362 4982 m jumping speed indicator image

LRBG: 362
5014 m

image

image

5317 m image

5801 m and 7603 m 8800 jumping gradiant profile

26589 m

pasp is not consist image

BG 424 26872 m

jumping speed gauge

LRBG 426 27301 m

image

image

31185 m

no PIM and no Over speed warning

image

BG 443 RBC connection is not closed

image

stefan-karg commented 8 years ago

@ 4359 m (flag speed chang target at speed zero): Problem will be solved by a change in the TrackAtlas. DMI-Controller module is ok.

stefan-karg commented 8 years ago

@ LRBG: 362 4982 m jumping speed indicator

@T12z Can you please have a look at this problem? After tracing the behaviour through the model, for me it looks like a wrong behaviour in the SDM module, since the data from the track atlas looks fine.

T12z commented 8 years ago

moin @stefan-karg , this is what SimCtrl has to say about this:

sdm-target-log

the jumping of EoA->SvL->EoA is exactly what I think you mean. Sorry, out of time looking at this tonight in detail (aka debugging the model), may even quite be squeezy tomorrow. Anyways, see that SvL is double the distance of EoA? Could a bug be when importing / converting the targets from TA, but why would it disappear shortly after? I am reeeeally in doubt of an SDM problem, even though it could always be.

T12z commented 8 years ago

see other issue, doubling is interface issue, toggling between EoA/SvL happens close to EoA when identical to DP. (SvL curve is steeper but has more safety offset)

Farhangi commented 8 years ago

Speed profile discontinuity is fixed (speed decrease and increase) and (target at speed zero) will be displayed.

stefan-karg commented 8 years ago

@T12z Thanks for the correction, I don't see any jumping any more.

T12z commented 8 years ago

@Farhangi was what I fixed the root of this issue? I go and close it then