...
Get all administrative things out of the way. Read the Introduction and the Technical Information chapters and set Set up your working environment. Do this carefully! You do not want to waste time with this kind of stuff later on.
To get yourself running create a stash account and check out the git repository of the railway project (summer term 20142017). Remember that you need a valid ssh key to work with stash. Add your public key to your stash/confluence account.
...
- Technical Documentation: http://www.informatik.uni-kiel.de/~railway/
- Railway Lecture Summary: http://rtsys.informatik.uni-kiel.de/~rt-teach/ws11/v-synch/lectures/lecture05a-handout4.pdf (slides 24-48)
- Kickoff Talk: Slides
Tasks - DEADLINE 22.04.2014
...
- Kickoff Talk (2014): Slides
Tasks
T1A1: Important Thoughts
Write down in own words Make sure you know why the railway installation is a) a real-time system, b) an embedded system, and c) a safety-critical system.
...
Since you have already checked out the project's repository, you also downloaded the c interface of the railway installation. Look inside the railway folder inside your local repository clone. You will find the example controller presented at the kickoff meeting the RailwayControllerC folder. Use this stub to create your own railway controller.
...
Before writing the c code make a plan how to achieve the task. Which tracks and point switches must be set when. Write down your plan briefly and program your controller. Eventually, test your controller with the simulation environment and the modelGUI.
...
Subsequent to fixing superflous bugs (in A2), what can you observe? Write down all things that differ from your initial expectations and explain why the railway/simulation did behave in a different way. Additionally list all differences that you expect to exist between the simulation and the real model railway. Therefore inspect the railway documentation and experiment with the simulation (sources).