Wiki source code of SS20 (Layout)

Version 20.1 by Soeren Domroes on 2023/07/07 05:41

version	line-number	content
1.1	1	(((
18.1	2	{{note}}
11.1	3	(% class="moz-quote-pre" %)
19.1	4	Although, there are no lectures with attendance at the CAU the following applies: this seminar will take place and start online on the 7th of April at 3 pm with the kick-off meeting. The kick-off meeting takes place at [[https:~~/~~/mediaportal01.rz.uni-kiel.de/b/sun-ctr-dq4>>url:https://mediaportal01.rz.uni-kiel.de/b/sun-ctr-dq4\|\|shape="rect"]].
11.1	5
	6	(% class="moz-quote-pre" %)
16.1	7	A seminar needs less interaction than a lecture. All scheduled individual meetings can take place online.
9.1	8	{{/note}}
	9
1.1	10	(% class="bodytext" style="text-align: left;" %)
16.1	11	The purpose of this seminar is to independently scientifically work on a layout algorithm topi. 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.
9.1	12
	13	(% class="bodytext" style="text-align: left;" %)
16.1	14	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).
1.1	15
	16	{{section}}
	17	{{column width="49%"}}
3.1	18	[[image:attach:image2016-7-7 15:43:29.png]]
1.1	19	{{/column}}
	20
	21	{{column width="49%"}}
3.1	22	[[image:attach:image2016-7-7 15:43:25.png]]
1.1	23	{{/column}}
	24	{{/section}}
	25
	26	(% style="text-align: left;" %)
16.1	27	= Imprtant Dates =
1.1	28
	29	(% class="wrapped" %)
10.1	30	\|=(% style="text-align: right;" colspan="1" %)(% style="text-align: right;" colspan="1" %)
1.1	31	(((
16.1	32	Requirements
10.1	33	)))\|(% colspan="1" %)(% colspan="1" %)
	34	(((
	35	//Wissenschaftliches Arbeiten// von Prof. Peters
1.1	36	)))
	37	\|=(% style="text-align: right;" %)(% style="text-align: right;" %)
	38	(((
16.1	39	Lecturers
1.1	40	)))\|(((
	41	Reinhard von Hanxleden (rvh@informatik.uni-kiel.de)
	42	Christoph Daniel Schulze (cds@informatik.uni-kiel.de)
	43	Sören Domrös (sdo@informatik.uni-kiel.de)
	44	)))
	45	\|=(% style="text-align: right;" %)(% style="text-align: right;" %)
	46	(((
16.1	47	Block seminar day
1.1	48	)))\|(((
3.1	49	TBD
1.1	50	)))
	51
16.1	52	= Topics =
1.1	53
	54	{{expand title="Klick mich, um Dinge zu sehen"}}
	55	(% class="bodytext" style="text-align: left;" %)
16.1	56	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.
1.1	57
	58	(% class="bodytext" style="text-align: left;" %)
16.1	59	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.
1.1	60
	61	{{note}}
16.1	62	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.
1.1	63	{{/note}}
	64
4.1	65	== Aesthetics and Perception ==
1.1	66
	67	Lloyd, Rodgers, and Roberts. "Metro map colour-coding: effect on usability in route tracing." In International conference on Theory and Application of Diagrams, pp. 411-428. Springer, 2018. [[PDF>>url:https://www.researchgate.net/profile/Peter_Lloyd14/publication/324279056_Metro_Map_Colour-Coding_Effect_on_Usability_in_Route_Tracing/links/5ac94b090f7e9bcd519751ae/Metro-Map-Colour-Coding-Effect-on-Usability-in-Route-Tracing.pdf\|\|shape="rect"]]
	68
	69	Burns, Carberry, Elzer, and Chester. "Automatically recognizing intended messages in grouped bar charts." In //International Conference on Theory and Application of Diagrams//, pp. 8-22. Springer, 2012. [[PDF>>url:https://www.researchgate.net/profile/Stephanie_Schwartz9/publication/262169666_Automatically_Recognizing_Intended_Messages_in_Grouped_Bar_Charts/links/550882ff0cf26ff55f82ccee.pdf\|\|shape="rect"]]
	70
4.1	71	== Human Computer Interaction ==
1.1	72
4.1	73	Pietriga. "A Toolkit for Addressing HCI Issues in Visual Language Environments." In //IEEE Symposium on Visual Languages and Human-Centric Computing// (VL/HCC), pp.145–152. 2015. [[PDF>>url:https://ieeexplore.ieee.org/iel5/10093/32326/01509498.pdf\|\|shape="rect"]]
	74
	75	Green, Petre. "Usability Analysis of Visual Programming Environments - A Cognitive Dimensions Framework." In //Journal of Visual Languages and Computing//, pp. 131–174, Issue 7–2. 1996. [[Seite mit PDF>>url:https://www.sciencedirect.com/science/article/pii/S1045926X96900099\|\|shape="rect"]]
	76
5.1	77	Pourali, Atlee. "A Focus+Context Approach to Alleviate Cognitive Challenges of Editing and Debugging UML Models." In //ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems (MODELS)//, pp. 183–193. 2019. [[PDF>>url:https://ieeexplore.ieee.org/iel7/8894013/8906890/08906900.pdf\|\|shape="rect"]]
4.1	78
8.1	79	(% style="color: rgb(165,173,186);" %)Moscovich, Chevalier, Henry, Pietriga, Fekete. "Topology-Aware Navigation in Large Networks." In //Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI)//, pp. 2319–2328. 2009.(%%) (vergeben) [[PDF>>url:https://hal.inria.fr/inria-00373679/document\|\|shape="rect"]]
5.1	80
	81	Frisch, Dachselt. "Off-Screen visualization techniques for class diagrams." In //Proceedings of the 5th International Symposium on Software Visualization//, pp. 163–172. 2010. [[PDF>>url:https://www.researchgate.net/profile/Raimund_Dachselt/publication/220955887_Off-screen_visualization_techniques_for_class_diagrams/links/0fcfd50abd0eba0db2000000.pdf\|\|shape="rect"]]
	82
1.1	83	== Graph Drawing ==
	84
	85	Chevalier and Safro. "Comparison of coarsening schemes for multilevel graph partitioning." In //International Conference on Learning and Intelligent Optimization//, pp. 191-205. Springer, 2009. [[PDF>>url:http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.531.2924&rep=rep1&type=pdf\|\|shape="rect"]]
	86
	87	Athenstädt, Hartmann, and Nöllenburg. "Simultaneous embeddability of two partitions." In //International Symposium on Graph Drawing//, pp. 64-75. Springer, 2014. [[PDF>>url:https://arxiv.org/pdf/1408.6019\|\|shape="rect"]]
	88
	89	== Euler Diagrams ==
	90
	91	Bottoni, Costagliola, and Fish. "Euler diagram encodings." In //International Conference on Theory and Application of Diagrams//, pp. 148-162. Springer, 2012. [[PDF>>url:https://s3.amazonaws.com/academia.edu.documents/45649653/Euler_diagram_encodings20160515-26490-1rvpanx.pdf?AWSAccessKeyId=AKIAIWOWYYGZ2Y53UL3A&Expires=1532097323&Signature=0mp3Nn2fRT4GGNbTTcWS%2F3gWwR8%3D&response-content-disposition=inline%3B%20filename%3DEuler_Diagram_Encodings.pdf\|\|shape="rect"]]
	92
	93	Chapman, Stapleton, Rodgers, Micallef, and Blake. "Visualizing sets: an empirical comparison of diagram types." In //International Conference on Theory and Application of Diagrams//, pp. 146-160. Springer, 2014. [[PDF>>url:http://eprints.brighton.ac.uk/13703/1/diagrams2014%20Visualizing%20DataREVISED.pdf\|\|shape="rect"]]
	94
	95	== Other Types of Diagrams ==
	96
3.1	97	Erwig and Smeltzer. "Variational Pictures." In //International Conference on Theory and Application of Diagrams//, pp. 55-70. Springer, 2018. [[Seite mit PDF>>doc:SS20 Eingeschränkt sichtbare Paper]]
1.1	98	{{/expand}}
	99
18.1	100	= Schedule =
1.1	101
	102	{{expand title="Klick mich, um Dinge zu sehen"}}
16.1	103	== Dates in the semester ==
1.1	104
16.1	105	(% class="wrapped relative-table" style="width: 52.6894%;" %)
1.1	106	\|=(((
10.1	107	Datum
1.1	108	)))\|=(((
10.1	109	Meilenstein
1.1	110	)))
	111	\|(((
16.1	112	Tue., 07.04., 23:59
1.1	113	)))\|(((
16.1	114	Deadline for topic
	115	//By e-mail to Sören//
1.1	116	)))
	117	\|(((
16.1	118	Tue., 07.04., 15:00
1.1	119	)))\|(((
16.1	120	Kick-off
	121	//The kick-off will take place online. We will send you the corresponding link.//
1.1	122	)))
	123	\|(((
16.1	124	Tue., 28.04., 08:00
1.1	125	)))\|(((
16.1	126	Deadline of the first draft in EasyChair
20.1	127	//Content: abstract, introduction, outline, notes for chapter contents, bibliography//
1.1	128	)))
	129	\|(% colspan="1" %)(% colspan="1" %)
	130	(((
16.1	131	Tue., 28.04., individual dates
1.1	132	)))\|(% colspan="1" %)(% colspan="1" %)
	133	(((
16.1	134	Individual dates
	135	//Online, as discussed with advisor
	136	//
1.1	137	)))
	138	\|(% colspan="1" %)(% colspan="1" %)
	139	(((
16.1	140	Tue., 19.05., 08:00
1.1	141	)))\|(% colspan="1" %)(% colspan="1" %)
	142	(((
16.1	143	Deadline of the first full version
11.1	144	//Submission-Update in EasyChair//
1.1	145	)))
	146	\|(% colspan="1" %)(% colspan="1" %)
	147	(((
20.1	148	Tue., 19.05., individual dates
1.1	149	)))\|(% colspan="1" %)(% colspan="1" %)
	150	(((
16.1	151	Individual dates
	152	//Online, as discussed with advisor//
1.1	153	)))
	154	\|(% colspan="1" %)(% colspan="1" %)
	155	(((
16.1	156	Tue., 02.06., 08:00 Uhr
1.1	157	)))\|(% colspan="1" %)(% colspan="1" %)
	158	(((
16.1	159	Deadline of the review version
11.1	160	//Submission-Update in EasyChair//
1.1	161	)))
	162	\|(% colspan="1" %)(% colspan="1" %)
	163	(((
16.1	164	subsequently
1.1	165	)))\|(% colspan="1" %)(% colspan="1" %)
	166	(((
16.1	167	Review assignment
	168	//By e-mail//**
1.1	169	**
	170	)))
	171	\|(% colspan="1" %)(% colspan="1" %)
	172	(((
16.1	173	Tue., 09.06., 08:00 Uhr
1.1	174	)))\|(% colspan="1" %)(% colspan="1" %)
	175	(((
16.1	176	Deadline reviews
11.1	177	//In EasyChair//
1.1	178	)))
	179	\|(% colspan="1" %)(% colspan="1" %)
	180	(((
	181	tbd
	182	)))\|(% colspan="1" %)(% colspan="1" %)
	183	(((
16.1	184	Talk on how to do talks/presentations (the talk-talk)?
1.1	185	)))
	186	\|(% colspan="1" %)(% colspan="1" %)
	187	(((
16.1	188	Tue., 23.06., individual dates
1.1	189	)))\|(% colspan="1" %)(% colspan="1" %)
	190	(((
16.1	191	Individual dates for presentation slides
	192	//Online, as discussed with advisor. he slides have to be available online or have been sent beforehand via e-mail.//**
1.1	193	**
	194	)))
	195	\|(% colspan="1" %)(% colspan="1" %)
	196	(((
16.1	197	Tue., 07.07., 08:00
1.1	198	)))\|(% colspan="1" %)(% colspan="1" %)
	199	(((
16.1	200	Deadline final version
11.1	201	//Submission-Update in EasyChair//**
1.1	202	**
	203	)))
	204	\|(% colspan="1" %)(% colspan="1" %)
	205	(((
3.1	206	tbd
1.1	207	)))\|(% colspan="1" %)(% colspan="1" %)
	208	(((
16.1	209	Presentations
1.1	210	)))
	211
16.1	212	== The Final Presentations ==
1.1	213
16.1	214	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.
1.1	215	{{/expand}}
	216
18.1	217	= Schedule and Grading =
1.1	218
	219	{{expand title="Klick mich, um Dinge zu sehen"}}
16.1	220	== Papers, Talks, Review ==
1.1	221
16.1	222	This seminar includes the creation of a paper, a talk, and two reviews.
1.1	223
16.1	224	=== Paper ===
1.1	225
16.1	226	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.
1.1	227
16.1	228	=== Talk ===
1.1	229
16.1	230	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.\\
1.1	231
16.1	232	You can freely choose your presentation tool. The talk can be held in English or German.
12.1	233
1.1	234	=== Review ===
	235
16.1	236	A review consist of two parts:
1.1	237
16.1	238	1. General comments (what do you like / not like regarding content, structure, and readability) as well as general suggestions to improve the paper
	239	1. In detail remarks and corrections
1.1	240
16.1	241	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.
12.1	242
16.1	243	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.
12.1	244
16.1	245	The reviews are assigned after the review-version deadline and are based on the submitted version of the papers.
1.1	246
16.1	247	== Grades ==
1.1	248
16.1	249	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.
1.1	250	{{/expand}}
	251
17.1	252	= Technical Details =
1.1	253
	254	{{expand title="Klick mich, um Dinge zu sehen"}}
	255	== LaTeX ==
	256
16.1	257	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.
1.1	258
16.1	259	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.
1.1	260
16.1	261	While writing your paper keep the following in mind:
1.1	262
16.1	263	* Think about whether you want to write your paper in German or English and make use to use the corresponding ACM-style.
	264	* 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.
	265	* A paper always consists of an introduction, at least one main chapter, and a conclusion.
1.1	266
	267	== EasyChair Tutorial ==
	268
16.1	269	You can find our seminar in EasyChair [[here>>url:https://easychair.org/my/conference?conf=kielrtsyssem20ss\|\|shape="rect"]].
1.1	270
	271	[[doc:RTSYS.EasyChair Student Tutorial]]
	272
	273	{{include/}}
	274	{{/expand}}
	275
17.1	276	= Ressources =
1.1	277
	278	{{expand title="Klick mich, um Dinge zu sehen"}}
16.1	279	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:
1.1	280
	281	* Google Scholar: [[http:~~/~~/scholar.google.de/>>url:http://scholar.google.de/\|\|shape="rect" class="external-link"]]
	282	* dblp: [[http:~~/~~/dblp.uni-trier.de/>>url:http://dblp.uni-trier.de/\|\|shape="rect"]]
	283	* CiteSeer: [[http:~~/~~/citeseer.ist.psu.edu/>>url:http://citeseer.ist.psu.edu/\|\|shape="rect" class="external-link"]]
	284	* IEEE-Xplore: [[http:~~/~~/ieeexplore.ieee.org/Xplore/dynhome.jsp>>url:http://ieeexplore.ieee.org/Xplore/dynhome.jsp\|\|shape="rect" class="external-link"]]
	285	* ACM Digital Library: [[http:~~/~~/portal.acm.org/dl.cfm>>url:http://portal.acm.org/dl.cfm\|\|shape="rect" class="external-link"]]
	286	* 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"]]
	287	{{/expand}}
	288
	289	\\
	290	)))
	291
	292	(% style="display: none;" %)
	293	(((
	294	555
	295	)))
	296
	297	(% style="display: none;" %)
	298	(((
	299	610
	300	)))
	301
	302	(% style="display: none;" %)
	303	(((
	304	410
	305	)))
	306
	307	(% style="display: none;" %)
	308	(((
	309	547
	310	)))
	311
	312	(% style="display: none;" %)
	313	(((
	314	983
	315	)))
	316
	317	(% style="display: none;" %)
	318	(((
	319	150
	320	)))
	321
	322	(% style="display: none;" %)
	323	(((
	324	329
	325	)))

Wiki source code of SS20 (Layout)

Navigation

Quick Links