This directory contains reference results of the case study and a checker script which can be used to verify those and potential new result. - simulink-run-* are simulink simulation - lsmc_run-nort-* are functional (non-realtime) simulation with SchedMCore BEWARE: the property (P1,P2,P3,P4) computation depends on the scenario so that user must chose the appropriate 'flight-mode' of the script in order to compute the corresponding properties. The script itself cannot guesse whether if the bar result represents VerticalSpeed, AirSpeed or LevelChange scenario. Remember that the ROSACE case study OK criterion are: P2 (overshoot) should be less than 10% P4 (steady steady error) should be less than 5% One can check the properties of the results like this: $ ./check_result.py --check-flight-mode VerticalSpeed simulink-run-scenario1-results.csv Checking for Vertical Speed control... Properties for Vz output P1 (settling time ) = 8.22 s P2 (overshoot ) = 4.71922808971343 % P3 (rise time ) = 5.085000000000001 s P4 (steady state error ) = 0.8269464235113589 % There are three Simulink scenarios: 1. simulink-run-scenario1-results.csv is a VerticalSpeed control scenario Verification command: $ ./check_result.py --check-flight-mode=VerticalSpeed --enable-graph simulink-run-scenario1-results.csv 2. simulink-run-scenario2-results.csv is an AirSpeed control scenario Verification command: $ ./check_result.py --check-flight-mode=AirSpeed --enable-graph simulink-run-scenario2-results.csv 3. simulink-run-scenario3-results.csv is a LevelChange control scenario Verification command: $ ./check_result.py --enable-graph simulink-run-scenario3-results.csv There are 6 scenarios from Prelude implementation: all are LevelChange control scenarii. 1. lsmc_run-nort-results-assemblage_v1.txt 2. lsmc_run-nort-results-assemblage_v2.txt 3. lsmc_run-nort-results-assemblage_v3.txt 4. lsmc_run-nort-results-assemblage_v41.txt 5. lsmc_run-nort-results-assemblage_v4.txt 6. lsmc_run-nort-results-assemblage_v5.txt Verification command for each is: ./check_result.py --enable-graph They must be compliant with simulink-run-scenario3-results.csv behavior.