Wiki source code of WS23/24 (Rail)

Version 5.1 by Alexander Schulz-Rosengarten on 2023/06/16 10:55
Show last authors
1 (% class="bodytext" style="text-align: left;" %)
2 The purpose of this seminar is to independently and scientifically work on a topic of embedded real-time systems and related. In this case with a focus on the railway domain and safety-critical systems. The goal is to summarize the topic in an oral presentation and a written elaboration in form of a paper. Another purpose of this seminar is to practice working in structured and time-driven workflows (e.g. for conferences or workshops). Moreover, both of these aspects are a good preparation for working on your thesis. We have many theses regarding these topics available; contact us if you are interested in that.
3
4 (% class="bodytext" style="text-align: left;" %)
5 This seminar is a bachelor and master module at the same time. Compared to the bachelor seminar, we expect that master students include more related work and therefore write a longer paper and hold a longer presentation (see below).
6
7 (% style="text-align: left;" %)
8 == Prerequisites ==
9
10 This is a seminar with a topic quite new for our working group, so there are no lectures required for this seminar.
11
12 (% style="text-align: left;" %)
13 We recommend the attendance of the lecture "**Scientific Working**" (Inf-WissArb: Wissenschaftliches Arbeiten) held by (% style="color: rgb(23,43,77);" %)Prof. Peters.
14
15 (% style="text-align: left;" %)
16 (% style="color: rgb(23,43,77);" %)Finally, there is the infamous "Vortragsvortrag" by Christoph Daniel Schulze. Sadly, he is not at RTSYS anymore to give that talk in person. However, he kindly started to prepare this [[sequence of videos>>url:https://www.youtube.com/playlist?list=PLjRqbgPHrKwC3uUQBRzKtnRH1vrNY9ehK||shape="rect"]] that should get the gist across as well.
17
18 (% style="text-align: left;" %)
19 == Lecturers ==
20
21 (% class="bodytext" style="text-align: left;" %)
22 Reinhard von Hanxleden ([[rvh@informatik.uni-kiel.de>>mailto:rvh@informatik.uni-kiel.de||shape="rect"]]) 
23 Niklas Rentz ([[nre@informatik.uni-kiel.de>>mailto:nre@informatik.uni-kiel.de||shape="rect"]])
24 Alexander Schulz-Rosengarten ([[als@informatik.uni-kiel.de>>mailto:als@informatik.uni-kiel.de||shape="rect"]])
25
26 (% style="text-align: left;" %)
27 == Topics ==
28
29 {{expand}}
30 (% class="bodytext" style="text-align: left;" %)
31 You may choose from one of the following papers. The scope, complexity and required knowledge for these papers roughly divides them into topics for bachelor students and for master students. However, bachelor students that take great interest in a master students topic may also choose from those. 
32
33 (% class="bodytext" %)
34 The papers are assigned via //first-come-first-serve//. Already taken papers are marked. Please send an email to Niklas ([[nre@informatik.uni-kiel.de>>mailto:nre@informatik.uni-kiel.de||shape="rect"]]) in order to reserve a paper.
35
36 (% class="bodytext" %)
37 Many of the links do only work in the university network. Through the usage of a [[VPN>>url:https://www.rz.uni-kiel.de/de/angebote/vpn||shape="rect"]] or a remote session to the [[terminal server>>url:https://www.inf.uni-kiel.de/de/service/technik-service/dienste||shape="rect"]], those are also accessible from home. If any problems occur feel free to contact us.
38
39 (% style="color: rgb(23,43,77);" %)
40 === Bachelor Recommendations ===
41
42 (% style="color: rgb(23,43,77);" %)
43 === Master Recommendations ===
44
45 Peleska, Jan, Anne E. Haxthausen, and Thierry Lecomte. "[[Standardisation considerations for autonomous train control.>>url:https://link.springer.com/chapter/10.1007/978-3-031-19762-8_22||shape="rect"]]" Leveraging Applications of Formal Methods, Verification and Validation. Practice: 11th International Symposium, ISoLA 2022, Rhodes, Greece, October 22–30, 2022, Proceedings, Part IV. Cham: Springer Nature Switzerland, 2022.
46
47 Basile, D., ter Beek, M.H., Legay, A. (2020). [[Strategy Synthesis for Autonomous Driving in a Moving Block Railway System with Uppaal Stratego>>url:https://link.springer.com/chapter/10.1007/978-3-030-50086-3_1||shape="rect"]]. In: Gotsman, A., Sokolova, A. (eds) Formal Techniques for Distributed Objects, Components, and Systems. FORTE 2020. Lecture Notes in Computer Science(), vol 12136. Springer, Cham. [[https:~~/~~/doi.org/10.1007/978-3-030-50086-3_1>>url:https://doi.org/10.1007/978-3-030-50086-3_1||shape="rect"]]
48 {{/expand}}
49
50 == Schedule ==
51
52 {{expand}}
53 Note: The dates are not final yet, to be discussed during the kickoff meeting.
54
55 (% class="fixed-table wrapped" %)
56 |=(((
57 Date
58 )))|=(((
59 Milestone
60 )))
61 |(((
62 TBA
63 )))|(((
64 First Meeting/**Kick-Off **with a Latex and EasyChair introduction. The meeting will take place in room 11.1114/11.1115 in CAP4.
65 )))
66 |(% colspan="1" %)(% colspan="1" %)
67 (((
68 TBA 23:59
69 )))|(% colspan="1" %)(% colspan="1" %)
70 (((
71 Deadline for topic selection (via email to Niklas)
72 )))
73 |(((
74 TBA 23:59
75 )))|(((
76 Deadline of the first draft in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]]. This includes abstract, introduction, outline, notes for chapter contents and an overview list of bibliography for related work.
77 )))
78 |(% colspan="1" %)(% colspan="1" %)
79 (((
80 (% style="color: rgb(23,43,77);" %)In the week after above (TBA), individual dates
81 )))|(% colspan="1" %)(% colspan="1" %)
82 (((
83 Individual feedback dates.
84 )))
85 |(% colspan="1" %)(% colspan="1" %)
86 (((
87 TBA 23:59
88 )))|(% colspan="1" %)(% colspan="1" %)
89 (((
90 Deadline of the first full version (submission update in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])
91 )))
92 |(% colspan="1" %)(% colspan="1" %)
93 (((
94 (% style="color: rgb(23,43,77);" %)In the week after above (TBA), individual dates
95 )))|(% colspan="1" %)(% colspan="1" %)
96 (((
97 Individual feedback dates.
98 )))
99 |(% colspan="1" %)(% colspan="1" %)
100 (((
101 TBA 23:59
102 )))|(% colspan="1" %)(% colspan="1" %)
103 (((
104 Deadline of the review version (submission update in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]]) and admission to program committee (invitation via email)
105 )))
106 |(% colspan="1" %)(% colspan="1" %)
107 (((
108 subsequently
109 )))|(% colspan="1" %)(% colspan="1" %)
110 (((
111 Review assignment (via email)**
112 **
113 )))
114 |(% colspan="1" %)(% colspan="1" %)
115 (((
116 TBA 23:59
117 )))|(% colspan="1" %)(% colspan="1" %)
118 (((
119 Deadline reviews (in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])**
120 **
121 )))
122 |(% colspan="1" %)(% colspan="1" %)
123 (((
124 subsequently (TBA)
125 )))|(% colspan="1" %)(% colspan="1" %)
126 (((
127 Individual feedback dates on presentation slides.
128
129 The slides need to be available online or sent to the advisor beforehand (as PDF).
130 )))
131 |(% colspan="1" %)(% colspan="1" %)
132 (((
133 TBA 23:59
134 )))|(% colspan="1" %)(% colspan="1" %)
135 (((
136 Deadline final version (submission update in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])
137 )))
138 |(% colspan="1" %)(% colspan="1" %)
139 (((
140 TBA, all day
141 )))|(% colspan="1" %)(% colspan="1" %)
142 (((
143 Final presentations
144 )))
145
146 == The Final Presentations ==
147
148 The presentation of the prepared topic is held during a block seminar at TBA. The attendance at the seminar day is mandatory. Every attending person receives the proceedings of the current semester.
149 {{/expand}}
150
151 == Milestones and Grading ==
152
153 {{expand}}
154 (% style="margin-top: 30.0px;color: rgb(23,43,77);" %)
155 == Papers, Talks, Review ==
156
157 This seminar includes creating a paper, a talk, and two reviews.
158
159 (% style="color: rgb(23,43,77);" %)
160 === Paper ===
161
162 The paper should provide an overview of the chosen topic. It should be written in a style that late bachelor student can understand it. The paper should be 6 (master) or 4 (bachelor) pages long (including bibliography), not more not less, and it should use the ACM LaTeX-style (more details below). We advise you to read the [[writing advice>>doc:RTSYS.Writing and Grading Theses||shape="rect"]] for writing a thesis. You can write your paper either in English or German.
163
164 (% style="color: rgb(23,43,77);" %)
165 === Talk ===
166
167 The talk should be 40 minutes (master) or 25 minutes (bachelor) long. This is followed by 5 minutes of questions. The slides should contain page numbers to allow the participants to ask specific questions after the talk. It would be great to include a short tool demo if your topic includes some concrete implementation.
168
169 You can freely choose your presentation tool. Therefore, for the individual dates on the presentation slides it would be best to to use your own computer. If the slides are provided as PDF beforehand, a different computer could be used.
170
171 Especially when using online tools, note that the block seminar might take place in Falckenstein and that there is no WLAN access. Therefore, the presentations must allow to be held offline.
172
173 The talk can be held in English or German.
174
175 (% style="color: rgb(23,43,77);" %)
176 === Review ===
177
178 A review consist of two parts:
179
180 1. General comments (what do you like/ not like regarding content, structure, and readability) as well as general suggestions to improve the paper
181 1. In detail remarks and corrections
182
183 The first part of the review should be at least half an A4 page long. It should be written in full text and not only consist of notes. The review content should be similar to the review you get during the individual dates, however, it should be more in detail and with a clear focus on content, structure, and readability of the paper.
184
185 It is not possible to add files in the EasyChair review form. Therefore, it is not possible to add an annotated pdf as detailed correction.
186
187 Some example reviews from a previous semester to understand the form (not necessarily with the best grades) can be found in here: [[1>>attach:review1.txt]] [[2>>attach:review2.txt]] [[3>>attach:review3.txt]] [[4>>attach:review4.txt]] [[5>>attach:review5.txt]].
188
189 The reviews are assigned after the review-version deadline and are based on the submitted version of the papers.
190
191 (% style="color: rgb(23,43,77);" %)
192 == Grades ==
193
194 This seminar is graded. The grade is based on each milestone (the different versions of the paper, the reviews, the slides, the talk). For each milestone quality, timing (see dates) are graded. Missed deadline may cause you to fail the seminar.
195 {{/expand}}
196
197 == Technical Details ==
198
199 {{expand}}
200 (% style="margin-top: 30.0px;color: rgb(23,43,77);" %)
201 === LaTeX ===
202
203 Your papers should be created with LaTeX and have to be in the provided ACM style. You can find all necessary files in this [[archive>>attach:SS20 (Layout)@paper-template.zip]], including an example document that includes helpful LaTeX-hints to start with. Copy all files in some folder and begin to write your paper. The style is an adjusted version of the official ACM style. Please use the style provided here and not the official one.
204
205 LaTeX can create a bibliography (it includes scientific publications, which are referenced to prove statements) too. The example includes a file named {{code language="none"}}myrefs.bib{{/code}}, which holds the references. ACM provides a short overview with [[examples>>url:https://www.acm.org/publications/authors/bibtex-formatting||shape="rect"]] of bibliography entries.
206
207 While writing your paper keep the following in mind:
208
209 * (((
210 Think about whether you want to write your paper in German or English and make use to use the corresponding ACM-style.
211
212 \\
213 )))
214 * If you use graphics from your original paper, you should not just add a screenshot of the pdf your paper. Try to use the image from the original paper by exporting them, including the pdf directly ({{code language="none"}}\inlcudegraphics[page=... trim=...]{*.pdf}{{/code}}), or by recreating the image by yourself (ideally as a vector graphic). This way you should get a result that is not pixelated or at least not worse than the original.
215 * A paper always consists of an introduction, at least one main chapter, and a conclusion.
216
217 (% style="color: rgb(23,43,77);" %)
218 === EasyChair Tutorial ===
219
220 You can find our seminar in EasyChair: **[[Link>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]]**
221
222 {{expand title="Klicke hier zum ausklappen..."}}
223 \\
224
225 [[doc:RTSYS.EasyChair Student Tutorial]]
226
227 {{include/}}
228 {{/expand}}
229 {{/expand}}
230
231 === (% style="font-size: 20.0px;font-weight: normal;letter-spacing: -0.008em;" %)Resources(%%) ===
232
233 {{expand}}
234 (% style="margin-top: 10.0px;" %)
235 In general, it is advised to look for related work in the university network since you will get access to many online libraries. We the following search engines and web pages:
236
237 * Google Scholar: [[http:~~/~~/scholar.google.de/>>url:http://scholar.google.de/||shape="rect" class="external-link"]]
238 * dblp: [[http:~~/~~/dblp.uni-trier.de/>>url:http://dblp.uni-trier.de/||shape="rect"]]
239 * CiteSeer: [[http:~~/~~/citeseer.ist.psu.edu/>>url:http://citeseer.ist.psu.edu/||shape="rect" class="external-link"]]
240 * IEEE-Xplore: [[http:~~/~~/ieeexplore.ieee.org/Xplore/dynhome.jsp>>url:http://ieeexplore.ieee.org/Xplore/dynhome.jsp||shape="rect" class="external-link"]]
241 * ACM Digital Library: [[http:~~/~~/portal.acm.org/dl.cfm>>url:http://portal.acm.org/dl.cfm||shape="rect" class="external-link"]]
242 * Universitätsbibliothek Digitale Medien: [[http:~~/~~/www.uni-kiel.de/ub/emedien/index.html>>url:http://www.uni-kiel.de/ub/emedien/index.html||shape="rect"]]
243 {{/expand}}

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage