<
From version < 45.1 >
edited by ssm
on 2014/12/30 18:32
To version < 95.1 >
edited by Reinhard von Hanxleden
on 2018/04/11 10:16
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ssm
1 +XWiki.rvh
Content
... ... @@ -1,111 +1,85 @@
1 -Here's a selection of possible bachelor and master topics. If you're interested in one of them, don't hesitate to contact us! We'll sit down, have tea, and talk about what we great things we could do together.
1 +Hier eine Themenübersicht, gefolgt von etwas detaillierteren Darstellungen. Generell sind Themenvariationen möglich, und auch selbst definierte Themen aus dem Bereich Echtzeitsysteme/Eingebettete Systeme nnen gerne besprochen werden. Ein weiterer Weg, um in kompakter Form einen Einblick in aktuelle Themen der Arbeitsgruppe zu bekommen, ist die Teilnahme an dem regelmäßig zu Semesterende bzw. in der vorlesungsfreien Zeit angebotenen Oberseminar.
2 2  
3 -**On this Page**
3 +**Hinweis**: Es ist Studierenden ausdrücklich empfohlen, sich frühzeitig bei den verschiedenen Arbeitsgruppen über mögliche Themen der Abschlussarbeit zu informieren. WWW-Seiten wie diese hier sind ein guter erster Anlaufpunkt, und es ist eine gute Idee, sich vor einem Gespräch mit einem potenziellen Betreuer (Professor, Assistenten ~-~- generell die Dozenten von Lehrveranstaltungen) über mögliche Themen einen Blick auf diese Seiten zu werfen. Es ist jedoch erfahrungsgemäß schwierig, auf solchen Seiten vollständige und aktuelle Informationen bereitzustellen; sie sollten daher eher als grober Indikator der jeweils möglichen Themenfelder dienen denn als konkrete Ausschreibungen. Um zu erfahren, welche Themen konkret verfügbar sind, zu dem angestrebten Zeitrahmen, sollte man auf jeden Fall die Dozenten konsultieren.
4 4  
5 +Die möglichen Themen sind im Folgenden thematisch gruppiert. Die Zahlen vor der Themenbeschreibung stehen für Prioritäten. Je kleiner die Zahl, desto wichtiger ist uns das Thema.
5 5  
7 += Outline =
6 6  
7 -{{toc/}}
8 8  
9 -= Graph Layout =
10 10  
11 -**Advisors:** Ulf Rüegg, Christoph Daniel Schulze.
11 +{{toc exclude="Outline"/}}
12 12  
13 -* **Tight Packing of Connected Components** (Bachelor)
14 -Different connected components of a graph are often laid out separately and combined again afterwards. This combination step often produces too much whitespace. Research relevant 2D packing literature and implement a better solution.
15 -{{jira columns="key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution" id="KIELER JIRA" serverId="2851bd34-0bf1-3f02-ab12-7d77ccab0fae" key="KIPRA-1262"}}KIPRA-1262{{/jira}}\\
16 -* **{{jira columns="key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution" id="KIELER JIRA" serverId="2851bd34-0bf1-3f02-ab12-7d77ccab0fae" key="KIPRA-1031"}}KIPRA-1031{{/jira}}Integrate KIML with JGraph** (Bachelor)
17 -Provide automatic layout through KIML for the JGraph diagram library and develop a simple JGraph-based graph editor to test the integration with.\\
18 -* **{{jira showSummary="true" columns="key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution" id="KIELER JIRA" serverId="2851bd34-0bf1-3f02-ab12-7d77ccab0fae" key="KIPRA-1214"}}KIPRA-1214{{/jira}}Improved Edge Label Placement** (Bachelor)
19 -Our layout algorithm already supports the placement of edge labels. However, there's still room for improvement...
20 -* **Layering Algorithms** (Bachelor, Master)
21 -Implement an alternative algorithm for the layer assignment problem used in the layer-based approach to graph layout. The focus of the algorithm could the consideration of the number of edge crossings, a given aspect ratio, or overall compactness.
22 -* **Node Placement With a Focus on Compactness** (Master)
23 -Node placement algorithms often try to draw as many edges as straight lines as possible. However, that usually results in less compact diagrams. The focus of this topic would be to devise or adapt a node placement algorithm that tries to strike a balance between straightness and compactness.
24 -* **Compound Graph Layout** (Master)
25 -Design and implement new concepts for computing layer-based layouts of compound graphs. The main focus shall be on //maintainability//: ensuring that the implementation can be kept working over the years. The main area to be considered here is the crossing minimization phase.
26 -* **Force Based Drawing with Port Constraints** (Master)
27 -Develop methods for integrating port constraints in force-based drawing approaches. The resulting node placement shall be evaluated using an edge router such as [[libavoid>>url:http://www.adaptagrams.org/||shape="rect"]] on the model library of [[Ptolemy>>url:http://ptolemy.eecs.berkeley.edu/||shape="rect"]].
28 -* **Combining Forces and Layers** (Master)**
29 -**Design and implement a layout algorithm that combines the force-based and the layer-based approaches. The first three phases of the layer-based approach shall be replaced by a node distribution computed with a force-based approach.
13 += Automatic Graph Layout =
30 30  
15 +**Advisors:** Christoph Daniel Schulze, Reinhard von Hanxleden.
16 +
17 +Ein sehr wichtiger Teil des KIELER Projekts is das automatische Layout von Diagrammen. Hierfür gibt es bereits Werkzeuge, die gute Algorithmen enthalten, so dass viele Diagramme bereits jetzt übersichtlich und automatisiert angeordnet werden können (siehe z.B. [[Graphviz>>url:http://www.graphviz.org/||shape="rect" class="external-link"]]). Für einige besondere Arten von Diagrammen sind diese allgemeinen Algorithmen jedoch nicht geeignet, da zusätzliche Anforderungen an das Layout erfüllt werden müssen. Außerdem ist häufig die technische Anbindung vorhandener Algorithmen umständlich. Nutzer müssen sich mit der Funktionsweise der Algorithmen beschäftigen, um sie für ihre Anwendung optimal konfigurieren zu können.
18 +
19 +Wir verfolgen drei Themenbereiche, die zusammen solche Probleme lösen und den Nutzen von automatischem Layout erhöhen sollen:
20 +
21 +//» Algorithmen-Entwicklung.// Wir implementieren vorhandene Ansätze zum Layout von Graphen in Java und binden sie in das KIELER Framework ein. Der Schwerpunkt liegt auf dem Entwurf von Erweiterungen, die spezielle Anforderungen unterstützen, z.B. für Datenfluss-Diagramme. Dies ist gut für alle geeignet, die sich gerne mit Graphentheorie, effizienten Algorithmen oder kombinatorischer Optimierung beschäftigen.
22 +
23 +//» Meta Layout.// Hierunter verstehen wir ein abstraktes Layout, welches im Gegensatz zum konkreten Layout nicht durch (x,y) Koordinaten definiert ist, sondern den Nutzern verschiedene Schnittstellen bietet, um auf schnelle und einfache Weise die Layout-Algorithmen zu konfigurieren. Die große Herausforderung liegt dabei in der Entwicklung von Abstraktionsebenen, die den Nutzer möglichst direkt zu einem guten Layout führen und trotzdem flexibel genug sind.
24 +
25 +//» Dienste.// Algorithmen und Meta Layout müssen den Anwendern zugänglich gemacht werden, damit ein Nutzen daraus entsteht. Dazu müssen wir verschiedenste graphische Frameworks mit vorhandenen Layout-Bibliotheken integrieren und eine Reihe von Werkzeugen entwickeln, mit denen die Verfügbarkeit unserer Lösungen gesteigert wird. Hierzu gehört z.B. die Unterstützung von Standard-Graphenformaten sowie ein Web-Service für automatisches Layout.
26 +
31 31  = Modeling Pragmatics =
32 32  
33 -**Advisors:** Reinhard von Hanxleden, Ulf Rüegg, Christoph Daniel Schulze.
29 +**Advisors:** Ulf Rüegg, Christoph Daniel Schulze, Reinhard von Hanxleden
34 34  
35 -* **Comment Attachment** (Bachelor)
36 -When computing a new layout for a diagram that contains comments (comparable to comments in source code), the comments often get placed far away of the nodes they refer to. This is because often the reference is not explicitly encoded in the original model. We have used a distance-based metric in the past to discover references automatically, but there are lots of ideas for improvement. This bachelor thesis would implement them, perhaps come up with additional ideas, and finally evaluate them in a thorough experiment.
37 -* **Control Flow Graph Exploration / Visualization** (Bachelor)
38 -Use pragmatics concepts (automatic layout, focus & context) for exploring/visualizing control flow graphs and specific paths, eg. as computed by OTAWA WCET analysis tool, eg. using KLighD.
39 -* **Compound Graph Exploration** (Bachelor, Master)
31 +* **1 Compound Graph Exploration** (Bachelor, Master)
40 40  A new graph exploration approach should be examined which is uses different zoom levels for different compound nodes. This tries to map the "Google Maps approach" of only showing the information of interest at any given zoom level to the field of graph exploration.
33 +* **1 OpenStreetMap-Based Model Exploration** (Bachelor, Master)
34 +Implement a prototype to investigate whether OpenStreetMap can be used to display custom data (such as, say, rendered diagrams) to use its filtering and exploration features for exploring large diagrams.
35 +* **3 Control Flow Graph Exploration / Visualization** (Bachelor)
36 +Use pragmatics concepts (automatic layout, focus & context) for exploring/visualizing control flow graphs and specific paths, eg. as computed by OTAWA WCET analysis tool, eg. using KLighD.
37 +* **Use signal flow graphs for parameterizing / debugging audio system configurations (Master)**
38 +The configuration of how signals are routed and how signal processors are configured in an audio system is a complex task. Make configuration and debugging easier by providing a visualization of the current configuration. Also, research what will help developers and users find configuration problems. The resulting software can be integrated into an existing Python-based configuration application, or be developed as a standalone tool that communicates with the audio system through Ethernet. (In conjunction with [[sonoware GmbH>>url:https://www.sonoware.de/en/||shape="rect"]])
41 41  
42 -= Semantics and Synchronous Languages =
40 += Semantics, Synchronous Languages and Model-based Design =
43 43  
44 -**Advisors:** Christian Motika, Steven Smyth
42 +**Advisors:** Steven Smyth, Alexander Schulz-Rosengarten, Reinhard v. Hanxleden
45 45  
46 -* **Automatic documentation generation for model-based languages **(Bachelor)
47 -Develop an automatic SCCharts documentation & comment system
48 -* **Merging SCCharts and KLOTS** (Bachelor)
49 -Implement KLOTS as demonstrator extension of the KIELER SCCharts implementation
50 -* **On the usability of the KIELER SCCharts compiler** (Bachelor)
51 -Evaluate the actual implementation of the KIELER SCCharts compiler and provide suggestions for improvements, i.e. the usability as standalone (commandline) compiler
52 -\\
53 -* **Validation Manager for Models **(Bachelor/Master)
54 -Develop an integrated, flexible and generic syntactic validation framework for models (e.g. Esterel or SyncCharts).
55 -* **SCCharts compiler validation with Esterel **(Bachelor/Master)
56 -Automate the validation of the SCCharts compiler using the Esterel simulation.
57 -* **Transformation from SCCharts to Esterel** (Bachelor/Master)
58 -Develop a transformation in Xtend2 to generate Esterel code for SCCharts.
59 -* **Hardware Synthesis from SCCharts to FPGA **(Bachelor/Master)
60 -Use the circuit-based code generation approach to produce code for FPGAs
61 -* (% style="line-height: 1.4285715;" %)**Optimization of the SCCharts compiler **(%%)(Bachelor/Master)
62 -Profile the actual SCCharts compiler and apply optimizations; also evaluate the possibility to use multiple cores for compilation
63 -* **Optimization of the SCCharts transformations** (Bachelor/Master)
64 -Profile the actual SCCharts transformations and apply optimizations
65 -* **SCCharts Andriod backend for Mini Drones** (Bachelor/Master)
66 -Develop a new code generation backend for SCCharts for Andriod applications with Mini Drones as demonstrator
67 -* **On the pragmatics of modelling large models in SCCharts** (Bachelor/Master)
68 -Evaluate the possibilities to create and maintain large models in model-based languages (i.e. SCCharts) and provide suggestions for improvements
69 -* **Extend the SC MoC to handle priority-based variable accesses** (Bachelor/Master)
70 -Add priorities to variable accesses to extend the SC MoC and therefore the number of valid sequentially constructive synchronous programs.
71 -\\
72 -* **Detecting tick boundaries in SCCharts **(Master/Bachelor)
73 -Implement an algorithm that detects tick boundaries (in concurrent) threads and therefore improves the scheduling
74 -* **Efficient data dependency analyses in SCCharts** (Master/Bachelor)
75 -Implement data dependency analyses for SCCharts to improve static scheduling of the compiler
76 -* **KIELER evaluation environment for synchronous languages** (Master/Bachelor)
77 -Develop a reliable evaluation environment to compare common synchronous languages (i.e. Esterel/SyncCharts & SCCharts)
78 -* **Raceyard evaluation** (Master/Bachelor)
44 +Synchronous languages are well-established for the design of embedded, in particular safety-critical systems. One of our research areas concerns the further development of such languages and their efficient compilation. Specifically, we explore the paradigm of "sequential constructiveness" for reconciling familiar, imperative programming concepts with the sound grounding of synchronous languages. One language we have developed to try out and validate our concepts is the [[SCCharts>>doc:KIELER.SCCharts||shape="rect"]] language, which keeps evolving and thus offers many opportunities for student theses.
45 +
46 +//SCCharts Modelling & Transformations//
47 +
48 +* **SCCharts Verification** (Master/Bachelor)
49 +Add the possibility to perfom model checking on SCCharts
50 +* **Derive M2M Transformations from Pseudocode** (Master/Bachelor)
51 +Create a Pseudocode DSL (and generator) to automatically derive M2M transformations.
52 +* **Raceyard evaluation** (Master)
79 79  Evaluate the possibility for the use of SCCharts in the Raceyard context and pave the way for future experiments
54 +
55 +//SCCharts Code Generation & Optimizations//
56 +
57 +* **Optimization of the SCCharts compiler/transformations **(Bachelor/Master)
58 +Profile the actual SCCharts compiler/transformations and apply optimizations; also evaluate the possibility to use multiple cores for compilation.
59 +* **SCG Optimization based on SSA **(Bachelor/Master)
60 +The Static Single Assignment form enables powerful optimizations such as [[sparse conditional constant propagation>>url:http://dl.acm.org/citation.cfm?id=103136||shape="rect"]]. Adjust and implement this algorithm in the context of SCGs and evaluate the result.
61 +* **Efficient data dependency & scheduling analyses in SCCharts** (Master/Bachelor)
62 +Implement analyses for data dependency, scheduling (e.g. tick boundaries) for SCCharts to improve static scheduling of the compiler.
80 80  \\
81 -* **Quartz **(Master)
82 -Integrate the synchronous Quartz language into KIELER for validation purposes and teaching.
83 -* **Implementation of a priority-based compilation approach **(Master) [work in progress, Caroline Butschek]
84 -Implement the SyncCharts priority-based compilation approach into the SCCharts compiler chain.
85 -* **From Esterel to SCL **(Master) [work in progress, Karsten Rathlev]
86 -Implement transformations that translate Esterel programs to SCL
87 -* **Curing Schizophrenia in SCCharts **(Master)
88 -Develop new synchronizer to handle schizophrenia properly (e.g. depth join).**
89 -**
90 -* **Railway 4.0 **(Master) [work in progress, Nis Wechselberg]
91 -Design a new and modern hardware controlling (Version 4) for the railway installation.
92 92  
93 -= PRETSY / PRETSY2 =
65 +//SCCharts Simulation//
94 94  
95 -**Advisors:** Insa Fuhrmann, Steven Smyth
67 +* **Visualization of Model-based Simulation via Tracing** (Bachelor/Master)
68 +Use the already implemented Model-to-Model-Tracing in KIELER to visualize simulations.
69 +* **Core SCCharts Interpreter** (Master/Bachelor)
70 +Implement an Interpreter for Core SCCharts.
96 96  
97 -* **Real-time extensions for SCCharts** (Bachelor/Master)
98 -Make the timing instructions //delay_until// und //exception_on_expire// of the [[FlexPRET>>url:http://rtsys.informatik.uni-kiel.de/confluence/Multithreaded/Multicore execution of SCCharts Evaluate possibilities to preserve parallelism in SCCharts, implement mapping for (fine grained) multithreading and multicore based on the FlexPRET||shape="rect"]] processor available in SCCharts.
99 -* **Adding dataflow to SCCharts** (Bachelor/Master) [work in progress, Axel Umland]
100 -Add dataflow to SCCharts 
101 -\\
102 -* **Multithreaded/Multicore execution of SCCharts **(Master/Bachelor)
103 -Evaluate possibilities to preserve parallelism in SCCharts, implement mapping for (fine grained) multithreading and multicore 
104 -based on the [[FlexPRET>>url:http://www.eecs.berkeley.edu/Pubs/TechRpts/2013/EECS-2013-172.pdf||shape="rect"]] processor.
72 +//Model-based C Code Compilation//
105 105  
106 -= (% style="color: rgb(0,0,0);" %)Miscellaneous Topics(%%) =
74 +* **Incremental Model-based Compilation of Legacy C Programs** (Bachelor/Master)
75 +Modify the model-based compiler in KIELER so that it is able to compile C to (S)CCharts incrementally.
76 +* **Execution of Recursive Dataflow Code** (Master/Bachelor)
77 +* **Execution of Concurrent Dataflow Code** (Master/Bachelor)
78 +Modify the model-based dataflow compiler in KIELER so that it is able to compile recursive/concurrent C programs.
79 +For Master students: Implement both.
107 107  
108 -**Advisors:** to be determined.
81 +//Synchronous Languages//
109 109  
110 -* **Developing an Info Screen** (Bachelor)
111 -Info screens are screens that present data in ways that can be easily understood. This includes static data (project description graphics, members of a team, ...) as well as dynamically aggregated data (bug statistics, automatic build overviews, ...). This topic is about developing such an info screen for our group and making it easily configurable.
83 +* (% style="letter-spacing: 0.0px;" %)**eSCL - Implementing {{code language="none"}}gotopause{{/code}}**(%%) (Bachelor/Master)
84 +Create an extended dialect of the SC Language including the {{code language="none"}}gotopause{{/code}} statement and implement a transformation to SCL.
85 +\\
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -10751356
1 +40894631
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/10751356/Topics for Student Theses
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/40894631/Topics for Student Theses