Wiki source code of 2023/24 Railway Technology

Last modified by Soeren Domroes on 2025/01/30 12:00
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:#172b4d" %)Prof. Peters.
14
15 (% style="text-align: left;" %)
16 (% style="color:#172b4d" %)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 (% class="bodytext" style="text-align: left;" %)
30 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.  
31
32 (% class="bodytext" %)
33 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.
34
35 (% class="bodytext" %)
36 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.
37
38 (% style="color: rgb(23,43,77);" %)
39 === Bachelor Recommendations ===
40
41 **[assigned]** Bloomfield, R. E., Bendele, M., Bishop, P. G., Stroud, R. and Tonks, S. (2016). [[The risk assessment of ERTMS-based railway systems from a cyber security perspective: Methodology and lessons learned.>>url:https://openaccess.city.ac.uk/id/eprint/15105/8/||shape="rect"]] Paper presented at the First International Conference, RSSRail 2016, 28-30 Jun 2016, Paris, France
42
43 **[assigned]** Shafiullah, GM., A. Gyasi-Agyei, and P. Wolfs. “[[Survey of Wireless Communications Applications in the Railway Industry.>>url:https://researchportal.murdoch.edu.au/esploro/outputs/conferencePaper/Survey-of-wireless-communications-applications-in/991005544952607891||shape="rect"]]” Murdoch University, 2007. Web.
44
45 **[assigned] **Velha, P., Nannipieri, T., Signorini, A., Morosi, M., Solazzi, M., Barone, F., ... & Di Pasquale, F. (2019). [[Monitoring large railways infrastructures using hybrid optical fibers sensor systems>>url:https://ieeexplore.ieee.org/document/8894046||shape="rect"]]. //IEEE Transactions on Intelligent Transportation Systems//, //21//(12), 5177-5188.
46
47 Bougacha, R., Wakrime, A. A., Kallel, S., Ayed, R. B., & Dutilleul, S. C. (2019, May). [[A Model-based Approach for the Modeling and the Verification of Railway Signaling System>>url:https://www.scitepress.org/Papers/2019/77284/77284.pdf||shape="rect"]]. In //ENASE// (pp. 367-376).
48
49 P. Sun, S. Collart-dutilleul and P. Bon, "[[A model pattern of railway interlocking system by Petri nets>>url:https://ieeexplore.ieee.org/document/7223292||shape="rect"]]," 2015 International Conference on Models and Technologies for Intelligent Transportation Systems (MT-ITS), Budapest, Hungary, 2015, pp. 442-449, doi: 10.1109/MTITS.2015.7223292.
50
51 **[assigned]** D. Giglio and N. Sacco, "[[A Petri net model for analysis, optimisation, and control of railway networks and train schedules,>>url:https://ieeexplore.ieee.org/document/7795949||shape="rect"]]" 2016 IEEE 19th International Conference on Intelligent Transportation Systems (ITSC), Rio de Janeiro, Brazil, 2016, pp. 2442-2449, doi: 10.1109/ITSC.2016.7795949.
52 \\**[assigned] **A. Consilvio, A. Di Febbraro and N. Sacco, "[[A modular model to schedule predictive railway maintenance operations>>url:https://ieeexplore.ieee.org/document/7223290||shape="rect"]]," 2015 International Conference on Models and Technologies for Intelligent Transportation Systems (MT-ITS), Budapest, Hungary, 2015, pp. 426-433, doi: 10.1109/MTITS.2015.7223290.
53
54 **[assigned] **W. Carvajal-Carreño, A. P. Cucala García, A. Fernández-Cardador and L. Söder, "[[Efficient driving algorithms for non-disturbed and disturbed trains with the CBTC signalling system,>>url:https://ieeexplore.ieee.org/document/7223289||shape="rect"]]" 2015 International Conference on Models and Technologies for Intelligent Transportation Systems (MT-ITS), Budapest, Hungary, 2015, pp. 418-425, doi: 10.1109/MTITS.2015.7223289.
55
56 **[assigned] **S. Wandelt, Z. Wang and X. Sun, "[[Worldwide Railway Skeleton Network: Extraction Methodology and Preliminary Analysis>>url:https://ieeexplore.ieee.org/document/7786825||shape="rect"]]," in //IEEE Transactions on Intelligent Transportation Systems//, vol. 18, no. 8, pp. 2206-2216, Aug. 2017, doi: 10.1109/TITS.2016.2632998.
57
58 **[assigned] **J. Cosic, C. Schlehuber and D. Morog, "[[Digital Forensic Investigation Process in Railway Environment,>>url:https://ieeexplore.ieee.org/document/9432658||shape="rect"]]" 2021 11th IFIP International Conference on New Technologies, Mobility and Security (NTMS), Paris, France, 2021, pp. 1-6, doi: 10.1109/NTMS49979.2021.9432658.
59
60 **[assigned]** M. Franke et al., "[[Towards holistic autonomous obstacle detection in railways by complementing of on-board vision with UAV-based object localization,>>url:https://ieeexplore.ieee.org/document/9981156||shape="rect"]]" 2022 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS), Kyoto, Japan, 2022, pp. 7012-7019, doi: 10.1109/IROS47612.2022.9981156.
61
62 **[assigned] **H. Song, S. Gao, Y. Li, L. Liu and H. Dong, "[[Train-Centric Communication Based Autonomous Train Control System>>url:https://ieeexplore.ieee.org/document/9834134||shape="rect"]]," in IEEE Transactions on Intelligent Vehicles, vol. 8, no. 1, pp. 721-731, Jan. 2023, doi: 10.1109/TIV.2022.3192476.
63
64 Hertel, B.; Pagenkopf, J.; König, J. "[[Challenges in the (Re-)Connection of Peripheral Areas to the Rail Network from a Rolling Stock Perspective: The Case of Germany.>>https://www.mdpi.com/2624-8921/5/3/63]]" Vehicles 2023, //5//, pp. 1138-1148. https:~/~/doi.org/10.3390/vehicles5030063
65
66 There are more bachelor recommendations that are not publicly available on the [[subpage for non-public papers>>doc:Seminars.Archive.WS2324 (Railway Technology).WS2324 (Railway Technology) - Non-public Papers.WebHome]], to view them please log in with your LDAP credentials.
67
68 (% style="color: rgb(23,43,77);" %)
69 === Master Recommendations ===
70
71 Ferlin, A., Qiu, S., Bon, P., Sallak, M., Dutilleul, S. C., Schön, W., & Cherfi-Boulanger, Z. (2018). [[An automated method for the study of human reliability in railway supervision systems>>url:https://ieeexplore.ieee.org/document/8283579||shape="rect"]]. //IEEE Transactions on Intelligent Transportation Systems//, //19//(10), 3360-3375.
72
73 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.
74
75 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"]]
76
77 G. Krummenacher, C. S. Ong, S. Koller, S. Kobayashi and J. M. Buhmann, "[[Wheel Defect Detection With Machine Learning>>url:https://ieeexplore.ieee.org/document/8006280||shape="rect"]]," in //IEEE Transactions on Intelligent Transportation Systems//, vol. 19, no. 4, pp. 1176-1187, April 2018, doi: 10.1109/TITS.2017.2720721.
78
79 Anne E. Haxthausen, Jan Peleska, and Sebastian Kinder. 2011. [[A formal approach for the construction and verification of railway control systems.>>url:https://dl.acm.org/doi/10.1007/s00165-009-0143-6||shape="rect"]] Form. Asp. Comput. 23, 2 (Mar 2011), 191–219. [[https:~~/~~/doi.org/10.1007/s00165-009-0143-6>>url:https://doi.org/10.1007/s00165-009-0143-6||shape="rect"]]
80
81 (% style="color:#222222" %)**[assigned] **Yue, Yixiang, et al. "[[Integrated train timetabling and rolling stock scheduling model based on time‐dependent demand for urban rail transit>>url:https://onlinelibrary.wiley.com/doi/10.1111/mice.12300||shape="rect"]]." (% style="text-align:left" %)//Computer‐Aided Civil and Infrastructure Engineering//(% style="color:#222222" %) 32.10 (2017): 856-873.
82
83 (% style="color:#000000" %)**[assigned] **Markus Heinrich, Tsvetoslava Vateva-Gurova, Tolga Arul, Stefan Katzenbeisser, Neeraj Suri, Henk Birkholz, Andreas Fuchs, Christoph Krauß, Maria Zhdanova, Don Kuzhiyelil, Sergey Tverdyshev, Christian Schlehuber, "[[Security Requirements Engineering in Safety-Critical Railway Signalling Networks>>url:https://www.hindawi.com/journals/scn/2019/8348925/||shape="rect"]]", (%%)//Security and Communication Networks//(% style="color:#000000" %), vol. 2019, Article ID 8348925, 14 pages, 2019. [[https:~~/~~/doi.org/10.1155/2019/8348925>>url:https://doi.org/10.1155/2019/8348925||shape="rect"]]
84
85 **[assigned] **L. Yang, K. Li and Z. Gao, "[[Train Timetable Problem on a Single-Line Railway With Fuzzy Passenger Demand>>url:https://ieeexplore.ieee.org/document/4505360||shape="rect"]]," in IEEE Transactions on Fuzzy Systems, vol. 17, no. 3, pp. 617-629, June 2009, doi: 10.1109/TFUZZ.2008.924198.
86
87 There are more master recommendations that are not publicly available on the [[subpage for non-public papers>>doc:Seminars.Archive.WS2324 (Railway Technology).WS2324 (Railway Technology) - Non-public Papers.WebHome]], to view them please log in with your LDAP credentials.
88
89
90 == Schedule ==
91
92 Note: The dates are not final yet, to be discussed during the kickoff meeting.
93
94 (% class="fixed-table wrapped" %)
95 |=(((
96 Date
97 )))|=(((
98 Milestone
99 )))
100 |(((
101 Tue. 24.10.23, 10:00
102 )))|(((
103 First Meeting/**Kick-Off**. The meeting will take place in room 11.1114/11.1115 in CAP4.
104 )))
105 |(% colspan="1" %)(% colspan="1" %)
106 (((
107 Tue. 24.10.23, 23:59
108 )))|(% colspan="1" %)(% colspan="1" %)
109 (((
110 Deadline for topic selection (via email to Niklas)
111 )))
112 |(((
113 Mon., 13.11.23, 23:59
114 )))|(((
115 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.
116 )))
117 |(% colspan="1" %)(% colspan="1" %)
118 (((
119 (% style="color:#172b4d" %)In the week of above (Wed./Fri.), individual dates
120 )))|(% colspan="1" %)(% colspan="1" %)
121 (((
122 Individual feedback dates.
123 )))
124 |(% colspan="1" %)(% colspan="1" %)
125 (((
126 Mon., 11.12.23 23:59
127 )))|(% colspan="1" %)(% colspan="1" %)
128 (((
129 Deadline of the first full version (submission update in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])
130 )))
131 |(% colspan="1" %)(% colspan="1" %)
132 (((
133 (% style="color:#172b4d" %)In the week of above (Wed./Fri.), individual dates
134 )))|(% colspan="1" %)(% colspan="1" %)
135 (((
136 Individual feedback dates.
137 )))
138 |(% colspan="1" %)(% colspan="1" %)
139 (((
140 Fri., 22.12.23 23:59
141 )))|(% colspan="1" %)(% colspan="1" %)
142 (((
143 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)
144 )))
145 |(% colspan="1" %)(% colspan="1" %)
146 (((
147 subsequently, Mo., 08.01.24
148 )))|(% colspan="1" %)(% colspan="1" %)
149 (((
150 Review assignment (via email from us)
151 )))
152 |(% colspan="1" %)(% colspan="1" %)
153 (((
154 Mo., 15.01.24 23:59
155 )))|(% colspan="1" %)(% colspan="1" %)
156 (((
157 Deadline reviews (in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])
158 )))
159 |(% colspan="1" %)(% colspan="1" %)
160 (((
161 subsequently (31.01.23/02.02.24)
162 )))|(% colspan="1" %)(% colspan="1" %)
163 (((
164 Individual feedback dates on presentation slides.
165
166 You may send the slides to the advisor beforehand (as PDF).
167 )))
168 |(% colspan="1" %)(% colspan="1" %)
169 (((
170 07.02.24 23:59
171 )))|(% colspan="1" %)(% colspan="1" %)
172 (((
173 Deadline final version (submission update in [[EasyChair>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]])
174 )))
175 |(% colspan="1" %)(% colspan="1" %)
176 (((
177 10.02.24, all day
178 )))|(% colspan="1" %)(% colspan="1" %)
179 (((
180 Final presentations
181 )))
182
183 == The Final Presentations ==
184
185 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.
186
187 === Agenda ===
188
189 You may find the agenda as a PDF [[here>>attach:agenda_anonym.pdf]].
190
191 == Milestones and Grading ==
192
193 (% style="margin-top: 30.0px;color: rgb(23,43,77);" %)
194 == Papers, Talks, Review ==
195
196 This seminar includes creating a paper, a talk, and two reviews.
197
198 (% style="color: rgb(23,43,77);" %)
199 === Paper ===
200
201 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:Theses.Writing and Grading Theses.WebHome||shape="rect"]] for writing a thesis. You can write your paper either in English or German.
202
203 (% style="color: rgb(23,43,77);" %)
204 === Talk ===
205
206 The talk should be 30 minutes (master) or 20 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.
207
208 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.
209
210 Especially when using online tools, note that the block seminar might take place in Falckenstein and that there is no Wifi access. Therefore, the presentations must allow to be held offline.
211
212 The talk can be held in English or German.
213
214 (% style="color: rgb(23,43,77);" %)
215 === Review ===
216
217 A review consist of two parts:
218
219 1. General comments (what do you like/ not like regarding content, structure, and readability) as well as general suggestions to improve the paper
220 1. In detail remarks and corrections
221
222 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.
223
224 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.
225
226 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]].
227
228 The reviews are assigned after the review-version deadline and are based on the submitted version of the papers.
229
230 (% style="color: rgb(23,43,77);" %)
231 == Grades ==
232
233 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.
234
235 == Technical Details ==
236
237 (% style="margin-top: 30.0px;color: rgb(23,43,77);" %)
238 === LaTeX ===
239
240 Your papers should be created with LaTeX and have to be in the provided ACM style. You can find all necessary files in this [[zip archive>>https://cloud.rz.uni-kiel.de/index.php/s/PpmFxJtxYqF2GaX]], 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.
241
242 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.
243
244 While writing your paper keep the following in mind:
245
246 * (((
247 Think about whether you want to write your paper in German or English and make use to use the corresponding ACM-style.
248
249
250 )))
251 * 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.
252 * A paper always consists of an introduction, at least one main chapter, and a conclusion.
253
254 (% style="color: rgb(23,43,77);" %)
255 === EasyChair Tutorial ===
256
257 You can find our seminar in EasyChair: **[[Link>>url:https://easychair.org/conferences/?conf=kielrtsyssem23ws||shape="rect"]]**
258
259
260 [[EasyChair Tutorial for Students>>doc:Seminars.EasyChair Tutorial.WebHome]]
261
262 === (% style="font-size:20.0px; font-weight:normal; letter-spacing:-0.008em" %)Resources(%%) ===
263
264 (% style="margin-top: 10.0px;" %)
265 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:
266
267 * Google Scholar: [[http:~~/~~/scholar.google.de/>>url:http://scholar.google.de/||shape="rect" class="external-link"]]
268 * dblp: [[http:~~/~~/dblp.uni-trier.de/>>url:http://dblp.uni-trier.de/||shape="rect"]]
269 * CiteSeer: [[http:~~/~~/citeseer.ist.psu.edu/>>url:http://citeseer.ist.psu.edu/||shape="rect" class="external-link"]]
270 * IEEE-Xplore: [[http:~~/~~/ieeexplore.ieee.org/Xplore/dynhome.jsp>>url:http://ieeexplore.ieee.org/Xplore/dynhome.jsp||shape="rect" class="external-link"]]
271 * ACM Digital Library: [[http:~~/~~/portal.acm.org/dl.cfm>>url:http://portal.acm.org/dl.cfm||shape="rect" class="external-link"]]
272 * 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"]]

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage