Braking Curves Testmodel

[MarcBehrens]

Task: Develop Braking Curves Test- / Functionalmodel and generate tests to test braking curves.

Workscope: Setup of environment:

• [x] Agree on a common (reduced) set of parameters to consider first for modelling @alexn84 SP:1
• [x] Mapping in- and output-variables of model to EFS for checking (Interface how to speak to model) @svitlana SP: 3

Hint: Analysis of parameters should be done on basis of the ERA sheet: http://www.era.europa.eu/Core-Activities/ERTMS/Pages/Braking-Curves-Simulation-Tool.aspx

Modelling reduced to EBD- Curve:

• [x] SysML static model for braking curves (code representation - describing input and output of system) @alexn84 SP: 13
• [ ] SysML behavioural model for braking curves (code representation - describing input and output of system) @alexn84 SP:34
• [ ] RT- Tester testmodel for braking curves @cecilebraun #68

First verification:

• [ ] Use common interface (in- and output- parameters) with RT-Tester and generate test scenarios @cecilebraun
• [ ] Check Braking Curves model on reduced scenario with EFS (Support by @svitlana)
• [ ] Debugging the different findings

Further development/ verification:

• [ ] Identify properties to be verified by the braking curves model
• [ ] Provide Braking Curves Parameter usable for VDE 8.2 @BaseliyosJacob
• [ ] Develop scenario to test braking curves
• [ ] Test braking curves

@fgola @alexn84 @benjaminbeichler @stanpinte @cecilebraun @UweSteinkeFromSiemens

[stanpinteTheSignallingCompany]

Dear Marc,

This small email to inform you we have completed implementation of braking curves model in augiust 2012, and already successfully validated our model against ERA reference spreadsheet.

All of this is available as of today in ERTMSFormalSpecs repository, under EUPL license.

http://www.ertmssolutions.com/files/UsingERTMSFormalSpecsToModelBrakingCurves.pdf

Very kind regards

Stan

[MarcBehrens]

The first subtask has been completed, thank you @BenjaminBeichler.

@svitlana, is it possible for you to continue this task by mapping the incoming and outgoing variables to your EFS braking simulation.

[Svitlana-Lukicheva]

@MarcBehrens

Of course, I'll start it next week.

[BerndHekele]

EFS plans to work on the issue in week 38. Feedback awaited.

[stanpinteTheSignallingCompany]

@BerndHekele Dear Bernd, we at ERTMS Solutions are currently having a sprint with some new modellers, requiring a lot of small changes in the ERTMSFormalSpecs toolchain, improving modelling productivity and user-friendliness.

Can we delay up to week 42 the work on the Braking curves question?

Moreover, at that time we shall be more advanced in terms of BL3 3.3.0 support (See https://github.com/openETCS/ERTMSFormalSpecs/issues/5), which is needed to do this issue.

Thanks in advance for your feedback,

Very kind regards

Stan

[BerndHekele]

Dear Stan, this implies we will have late results from the comparison with EFS available for the Evaluation of the first level validation milestone. This is not so much an issue for the validation plan, Besides the final result I do not see to much of a dependency with other subtasks in the task. But, I see more disadvantages for EFS in the competition.

Maybe, you or Svitlana can participate in the next grooming meeting to check on the impacts (Wednesday's).

Best Regards Bernd

[stanpinteTheSignallingCompany]

Dear Bernd,

Thanks for confirming these delays shall not be impacting other subtasks.

I checked with Baseliyos here and it seems allright.

Very kind regards

Stan

[MarcBehrens]

Review 2nd October 2013: First draft of SysML braking curves planned @alexn84

[alexn84]

First steps with Papyrus/SysML and the SaDM (Speed and Distance Monitoring) Reason for creating this model:

• Exploring Papyrus / SysML
• to get an Overview over the architecture/structure of Chapter 3.13 of the Subset 26 (Speed and Distnance Monitoring)

Next steps are: working on the subtask that is mentioned above, that means detailed editing/SysML-modelling of the EBD-Curve

Upload: https://github.com/openETCS/validation/tree/master/VnVUserStories/VnVUserStoryURO/05-Work/SpeedAndDistanceMonitoring%40SysML

I would be very grateful for suggestions

[MarcBehrens]

@LaurentFerier agreed to provide 6 scenarios used for verifivation of the models based on the ERA spreadsheet.

[MarcBehrens]

Coverage on the brakging curves parameters provided by @LaurentFerier

[LaurentFerier]

Please note that this is related to version 3.2.0 of subset-026. We are currently working on revision 3.3.0

[Svitlana-Lukicheva]

@MarcBehrens

Dear Mark, the scenarios are ready, could you please tell me where we could upload them?

[BerndHekele]

@LaurentFerier , @Svitlana-Lukicheva , can you start a new ERTMS Solutions folder in the validation path with this infomration? You can see the how-to in the wiki

Bernd

[Svitlana-Lukicheva]

@BerndHekele , can you please provide the link to the how-to in the wiki? Sorry, I cannot find it.

[MarcBehrens]

@Svitlana-Lukicheva you can find the fresh How-To here: https://github.com/openETCS/validation/wiki/How-to-contribute-to-validation

[LaurentFerier]

Braking curves scenario have been placed in VnVUserStories\VnVUserStoryERTMSSolutions\05-Work\Braking curves scenarios (see commit bede981c4d474ad9e39db2dcd596e179e2ef6cc8)

[MarcBehrens]

Thank you Laurent for providing the scenarios for validation.

Next step would be to show evidence that the different model comply to the scenario output applying the scenario input.

[BerndHekele]

Wrong scenario chosen. In order to be able to compare the results the model should be extended (later).

[LaurentFerier]

Hi Bernd, can you tell us more about your comment ?

• Why is the scenario wrong ?
• Where should be model be extended ?
• Is it due to the differences between version 3.2.0 and 3.3.0 ?

[BerndHekele]

Of course. The problem is not related to the version of the standards but to the parameters used in the model. @alexn84 , can you please add the details.

[BenjaminBeichler]

Hi Laurent,

I made this comment, because we adapted the subset of the modelling aspects from WP7 (resp. WP2) (https://github.com/openETCS/requirements/blob/master/D2.5/D2.5%20Methods%20and%20tools%20benchmarking%20methodology.pdf).

In my memory in the model-evaluation Wiki only gammar-trains were mentioned. This is the reason why we made this restriction in the document https://github.com/openETCS/validation/blob/master/VnVUserStories/VnVUserStoryURO/05-Work/BrakingCurves/BrakingCurveParameters.pdf

[LaurentFerier]

Hi Benjamin,

We provided two scenarios about gamma trains. Could you begin your tests with those, and consider them as HIGH_PRIORITY as described in https://github.com/openETCS/requirements/blob/master/D2.5/D2.5%20Methods%20and%20tools%20benchmarking%20methodology.pdf section 4.1.3 ?

Lower priorities can then be taken into account using the other sheets we provided. Would that fit your needs ?

[BenjaminBeichler]

I found only one file with a gammar-train scenario in the VnV-Userstories directory. Its not the Problem to use this, but we could currently only produce results for one testcase.

Another impediment is, that the excel-sheets are not really handy for data exchange. I don't know whether other workpackages already define better suitable formats for data-exchange. I would suppose something like in XML, like the test-Interface, described by DLR. I will open a new Issue for that.

[LaurentFerier]

You are right, we only provided one gamma train.

About XML files, you will find in https://github.com/openETCS/ERTMSFormalSpecs/tree/master/ErtmsFormalSpecs/doc/specs/braking%20curves%20verification/TestFrames the corresponding documents in XML format.

You can use the XLS sheet located there https://github.com/openETCS/validation/blob/master/VnVUserStories/VnVUserStoryERTMSSolutions/05-Work/Braking%20curves%20scenarios/DecelerationCurvesComputationVariables.xlsx to understand the meaning of each variable used in the tests

[MarcBehrens]

@laurent any updates on the report on braking curves verification?