WS21/22 (Layout)

(((

(% class="bodytext" style="text-align: left;" %)

The purpose of this seminar is to independently scientifically work on a layout algorithm topic. 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 good preparation for working on your thesis. We have many theses regarding these topics available; contact us if you are interested in that.

4

5

(% class="bodytext" style="text-align: left;" %)

6

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 papers and therefore write a longer paper and hold a longer presentation (see below).

[[image:attach:image2016-7-7 15:43:29.png]]

[[image:attach:image2016-7-7 15:43:25.png]]

(% style="text-align: left;" %)

19

= Imprtant Dates =

20

21

(% class="wrapped" %)

22

|=(% style="text-align: right;" colspan="1" %)(% style="text-align: right;" colspan="1" %)

23

(((

24

Requirements

25

)))|(% colspan="1" %)(% colspan="1" %)

26

(((

27

//Wissenschaftliches Arbeiten// von Prof. Peters

28

)))

29

|=(% style="text-align: right;" %)(% style="text-align: right;" %)

(((

Lecturers

)))|(((

Reinhard von Hanxleden (rvh@informatik.uni-kiel.de)

34

Sören Domrös (sdo@informatik.uni-kiel.de)

35

)))

36

|=(% style="text-align: right;" %)(% style="text-align: right;" %)

(((

Block seminar day

)))|(((

1. March

)))

= Topics =

(% class="bodytext" style="text-align: left;" %)

47

You may choose one of the following papers from the different topics. The papers marked with a are the ones that we deemed more important.

48

49

(% class="bodytext" style="text-align: left;" %)

50

The papers are assigned via //first-come-first-serve//. Already taken papers are marked. Many of the links do only work in the university network. If any problems occur feel free to contact us.

51

52

53

Some papers are not freely available. These papers are linked in an internal page in our wiki. You can log in with your Ifi-account. If any problems occur contact cds.

== TBD ==

= Schedule =

== Dates in the semester ==

63

64

(% class="wrapped relative-table" style="width: 52.6894%;" %)

|=(((

Datum

)))|=(((

Meilenstein

)))

|(((

Kickoff day at evening TBD

)))|(((

Deadline for topic

)))

|(((

Mo., 25.10., 12:00

)))|(((

Kick-off

//The kick-off will take place online. We will send you the corresponding link.//

80

)))

81

|(((

82

TBD ~~Three weeks later

83

)))|(((

84

Deadline of the first draft in EasyChair

85

//Content: abstract, introduction, outline, notes for chapter contents, bibliography//

86

)))

87

|(% colspan="1" %)(% colspan="1" %)

88

(((

89

In week of above

90

)))|(% colspan="1" %)(% colspan="1" %)

91

(((

92

Individual dates

93

//Online, as discussed with advisor

94

//

95

)))

96

|(% colspan="1" %)(% colspan="1" %)

97

(((

98

TBD ~~Three weeks later

99

)))|(% colspan="1" %)(% colspan="1" %)

100

(((

101

Deadline of the first full version

102

//Submission-Update in EasyChair//

103

)))

104

|(% colspan="1" %)(% colspan="1" %)

105

(((

106

In week of above

107

)))|(% colspan="1" %)(% colspan="1" %)

108

(((

109

Individual dates

110

//Online, as discussed with advisor//

111

)))

112

|(% colspan="1" %)(% colspan="1" %)

113

(((

114

TBD ~~Two weeks later

115

)))|(% colspan="1" %)(% colspan="1" %)

116

(((

117

Deadline of the review version

118

//Submission-Update in EasyChair//

119

)))

120

|(% colspan="1" %)(% colspan="1" %)

121

(((

122

subsequently

123

)))|(% colspan="1" %)(% colspan="1" %)

(((

Review assignment

//By e-mail//**

**

)))

|(% colspan="1" %)(% colspan="1" %)

130

(((

131

TBD ~~One week later

132

)))|(% colspan="1" %)(% colspan="1" %)

(((

Deadline reviews

//In EasyChair//

)))

|(% colspan="1" %)(% colspan="1" %)

138

(((

139

tbd

140

)))|(% colspan="1" %)(% colspan="1" %)

141

(((

142

Talk on how to do talks/presentations (the talk-talk)?

143

)))

144

|(% colspan="1" %)(% colspan="1" %)

145

(((

146

TBD ~~Two weeks later

147

)))|(% colspan="1" %)(% colspan="1" %)

148

(((

149

Individual dates for presentation slides

150

//Online, as discussed with advisor. The slides have to be available online or have been sent beforehand via e-mail.//**

151

**

152

)))

153

|(% colspan="1" %)(% colspan="1" %)

154

(((

155

TBD ~~Two weeks later

156

)))|(% colspan="1" %)(% colspan="1" %)

157

(((

158

Deadline final version

159

//Submission-Update in EasyChair//**

160

**

161

)))

162

|(% colspan="1" %)(% colspan="1" %)

163

(((

164

TBD

165

)))|(% colspan="1" %)(% colspan="1" %)

(((

Presentations

)))

== The Final Presentations ==

171

172

Currently, it is unclear how the talks will take place. This will be influenced by the development of the pandemic. We can think of recorded videos or a live conference or other alternatives. We expect to be able to make a decision at the end of Mai.

173

174

175

= Schedule and Grading =

176

177

178

== Papers, Talks, Review ==

179

180

This seminar includes the creation of a paper, a talk, and two reviews.

=== Paper ===

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, 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.

=== Talk ===

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.\\

189

190

You can freely choose your presentation tool. The talk can be held in English or German.

=== Review ===

A review consist of two parts:

195

196

1. General comments (what do you like / not like regarding content, structure, and readability) as well as general suggestions to improve the paper

197

1. In detail remarks and corrections

198

199

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.

200

201

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.

202

203

The reviews are assigned after the review-version deadline and are based on the submitted version of the papers.

== Grades ==

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. You may fail the seminar because of missed deadlines.

208

209

210

= Technical Details =

== LaTeX ==

Your papers should be created using LaTeX and have to be in the ACM style. You can find all necessary files in this [[archive>>attach: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.

216

217

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.

218

219

While writing your paper keep the following in mind:

220

221

* Think about whether you want to write your paper in German or English and make use to use the corresponding ACM-style.

222

* Graphics from your original paper should not just be screenshotted and added to your paper. Ideally, you create your own graphic (ideally as a vector graphic) to have good quality graphics.

223

* A paper always consists of an introduction, at least one main chapter, and a conclusion.

224

225

== EasyChair Tutorial ==

226

227

You can find our seminar in EasyChair [[here>>url:https://easychair.org/my/conference?conf=kielrtsyssem20ss||shape="rect"]].

228

229

[[doc:RTSYS.EasyChair Student Tutorial]]

= Ressources =

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:

238

239

* Google Scholar: [[http:~~/~~/scholar.google.de/>>url:http://scholar.google.de/||shape="rect" class="external-link"]]

240

* dblp: [[http:~~/~~/dblp.uni-trier.de/>>url:http://dblp.uni-trier.de/||shape="rect"]]

241

* CiteSeer: [[http:~~/~~/citeseer.ist.psu.edu/>>url:http://citeseer.ist.psu.edu/||shape="rect" class="external-link"]]

242

* IEEE-Xplore: [[http:~~/~~/ieeexplore.ieee.org/Xplore/dynhome.jsp>>url:http://ieeexplore.ieee.org/Xplore/dynhome.jsp||shape="rect" class="external-link"]]

243

* ACM Digital Library: [[http:~~/~~/portal.acm.org/dl.cfm>>url:http://portal.acm.org/dl.cfm||shape="rect" class="external-link"]]

244

* 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"]]

\\

)))

(% style="display: none;" %)

251

(((

252