Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test report 11.12.2015 - Speed reduction flag is not consistent with planning area speed reduction #987

Open
BaseliyosJacob opened this issue Dec 11, 2015 · 3 comments

Comments

@BaseliyosJacob
Copy link
Contributor

Speed reduction flag is not consistent with planning area speed reduction.
@JakobGartner @ShuangjiaoCao

image

image

@JakobGartner
Copy link
Contributor

From TrackAtlas point of view, there is only one output going to DMI containing speed profile information.

If there are differences in their interpretation, the source cannot be in TrackAtlas (the only data relevant to speed profiles emitted by TrackAtlas is the MRSP profile)

I assume that the flag and the planning area are both working on the MRSP info? Or is one of them using info from SDM?

On 11 Dec 2015, at 16:44, Baseliyos Jacob [email protected] wrote:

Speed reduction flag is not consistent with planning area speed reduction.
@JakobGartner https://github.com/JakobGartner @ShuangjiaoCao https://github.com/ShuangjiaoCao
https://cloud.githubusercontent.com/assets/3975810/11747967/4731b7c2-a026-11e5-9847-3c78beef14a5.png
https://cloud.githubusercontent.com/assets/3975810/11747978/5276b13c-a026-11e5-8a03-53cb44ffabb6.png

Reply to this email directly or view it on GitHub #987.

@BaseliyosJacob
Copy link
Contributor Author

We were a little bit surprise about the difference of the position on the DMI and the Loc_Abs position in the data from track atlas to DMI.

But @ShuangjiaoCao will check at monday again the files to the DMI t o be sure there is no issue in the controller. Can you please check your data as well?

Thank you very much

@JakobGartner
Copy link
Contributor

yes I am checking.

Are we using the same algorithm for determination of the position?

On 11 Dec 2015, at 17:30, Baseliyos Jacob [email protected] wrote:

We were a little bit surprise about the difference of the position on the DMI and the Loc_Abs position in the data from track atlas to DMI.

But @ShuangjiaoCao https://github.com/ShuangjiaoCao will check at monday again the files to the DMI t o be sure there is no issue in the controller. Can you please check your data as well?

Thank you very much


Reply to this email directly or view it on GitHub #987 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants