Closed Farhangi closed 8 years ago
I am sorry Peyman, I really have problems understanding your issue. First up, I have noticed some inconsistency here as well for quite some time. And I also see SDM as potential root cause. But can you please explain briefly the correct expected behaviour? The description in my section 3.9 is not too exhaustive about this. Cheers !
---- Peyman Farhangi schrieb ----
@Rainer-Lampatzer @T12z @ShuangjiaoCao
at km 4811
CSG is disappearing red/yellow/white 
— Reply to this email directly or view it on GitHub.
@T12z Image 1 comes everytime when CSG changes from red to orange. (for a very short time) I guess the problem was in PacketDynamic.v_intervention. As image 2 shows, the Intervention Speed is now becomming -1, which makes the CSG disappeared...
I suspect a diverging behaviour between DMI and brake calculation. From SDM's point of view, after braking, v_perm and v_interv rise again - this correct by the specified calculations. But it was asked, that v_perm and v_interv do not rise within same TSM. But since all speed limits rised -- just not on DMI -- no intervention is shown. So far unconfirmed suspicions. Same issue points towards different sized warning gauge sectors. Root issue: the right way to prevent TSM-speeds from rising is not specified in the SRS. And the current quick-fix seems to carry a few caveats. I am afraid this will need more thought to do it right.
From TrackAtlas point of view, DMI and SDM receive exactly the same data, with the exception that the data for SDM are not truncated at EOA. Might this difference contribute to the problem?
above mentioned quick-fix was removed together with brake-build-up trimming
@Rainer-Lampatzer @T12z @ShuangjiaoCao
at km 4811
CSG is disappearing red/yellow/white