Skip to Content

Changes for page Technical Stuff

Last modified by Alexander Schulz-Rosengarten on 2025/10/21 14:40
From version 13.1
edited by cds
on 2015/07/23 09:27
Change comment: There is no comment for this version
To version 8.1
edited by cds
on 2013/09/13 12:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,16 +6,12 @@
6 6  
7 7  = Use LaTeX and the KCSS Style =
8 8  
9 -Before you do anything else for your thesis work, you should get the technical issues for writing your thesis out of the way. Ie, you should create a git repository for your thesis, familiarize yourself with [[LaTeX>>url:http://de.wikipedia.org/wiki/LaTeX||rel="nofollow" style="text-decoration: none;" shape="rect" class="external-link"]] and the [[KCSS>>url:https://www.inf.uni-kiel.de/de/forschung/publikationen/kcss||shape="rect"]] style, and adapt/fill in the KCSS thesis template for your needs. This way, you can fill your thesis with contents as you work along on your thesis topic, instead of keeping notes in various ways and having to consolidate it all later.
9 +Before you do anything else for your thesis work, you should get the technical issues for writing your thesis out of the way. Ie, you should create a git repository for your thesis, familiarize yourself with [[LaTeX>>url:http://de.wikipedia.org/wiki/LaTeX||rel="nofollow" style="text-decoration: none;" shape="rect" class="external-link"]] and the [[KCSS>>url:http://www.informatik.uni-kiel.de/kcss/||shape="rect"]] style, and adapt/fill in the KCSS thesis template for your needs. This way, you can fill your thesis with contents as you work along on your thesis topic, instead of keeping notes in various ways and having to consolidate it all later.
10 10  
11 11  = Use Git =
12 12  
13 -Our shared repositories are managed with Git. The files associated with the thesis should be kept in the group's Git installation, as a separate repository that your advisor will create for you. The main purpose is to prevent loss of data, but it also facilitates access for fellow group members if needed, and to allow on-line publication. If you haven't used Git yet, there's a few excellent introductions to be found on the internet, for example:
13 +Our shared repositories are managed with Git. The files associated with the thesis should be kept in the group's Git installation, as a separate repository that your advisor will create for you. The main purpose is to prevent loss of data, but it also facilitates access for fellow group members if needed, and to allow on-line publication. See also [[doc:KIELER.Using Git]].
14 14  
15 -* [[The Git book>>url:http://git-scm.com/book/||shape="rect"]]
16 -* [[The excellent Git tutorial>>url:https://www.atlassian.com/git/tutorial||shape="rect"]], written by  the guys at Atlassian
17 -* The Git page in our KIELER Wiki: [[doc:KIELER.Using Git]]
18 -
19 19  The main tex file for a thesis should be {{code language="none"}}<name of repository>.tex{{/code}} (see also [[Git/Structure>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Git/Structure||style="text-decoration: none;" shape="rect" class="wiki"]] for the canonical naming scheme). E.g., the bachelor thesis of user xyz can be found in a repository named {{code language="none"}}xyz-bt{{/code}} [[in the Theses project of our Stash system>>url:https://git.rtsys.informatik.uni-kiel.de/projects/THESES||shape="rect"]], in a file named {{code language="none"}}xyz-bt.tex{{/code}}. If there is a talk to "defend" the thesis (Bachelor-Kolloquium, Disputation), the talk should also be included in this repository, and should be named {{code language="none"}}<name of repository>-talk.tex{{/code}} (e.g. {{code language="none"}}xyz-bt-talk.tex{{/code}}). In case your thesis should be made available on-line, the same names should be used, e.g.,{{code language="none"}} xyz.pdf{{/code}}.
20 20  
21 21  See also the notes on [[preparing a paper>>doc:Writing Papers]], e.g. regarding which files should be kept in Git and which shouldn't.
... ... @@ -22,17 +22,19 @@
22 22  
23 23  = Editor/IDE =
24 24  
25 -Prof. von Hanxleden would recommend Emacs as a very flexible and powerful editor for LaTeX (and everything else). But probably you belong to a post-Emacs generation, so here are some alternatives: Hauke (haf) recommends [[Texlipse>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Texlipse||style="text-decoration: none;" shape="rect" class="wiki"]] as an easy-to use and also powerful Eclipse plug-in. Christoph Daniel (cds) recommends using Kile, a KDE LaTeX editor that is fast, powerful, and reasonably easy to understand and to use. On all platforms, including Mac, texmaker is a fine editor.
21 +Prof. von Hanxleden would recommend Emacs as a very flexible and powerful editor for LaTeX (and everything else). But probably you belong to a post-Emacs generation, so here are some alternatives: Hauke (haf) recommends [[Texlipse>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Texlipse||style="text-decoration: none;" shape="rect" class="wiki"]] as an easy-to use and also powerful Eclipse plug-in. Christoph Daniel (cds) recommends using Kile, a KDE LaTeX editor that is fast, powerful, and reasonably easy to understand and to use. On Mac, TeXShop is a fine editor that looks a bitt dated on first glance, but works very well.
26 26  
27 27  = The ToDo Package =
28 28  
29 -When writing your thesis, you will often want to make a note of something you need to add or change. The {{code language="none"}}todonotes{{/code}} package makes this easy. It lets you add placeholder graphics and notes in or next to the text. To include the package, add the following line to your document:
25 +Es kommt häufig vor dass man sich während des Schreibens Anmerkungen zum Text machen oder Dinge später hinzufügen möchte. Damit dies einfacher zu verwalten ist, steht ein extra ToDo-Paket zur Verfügung. Mit diesem Paket lassen sich Platzhalter für Grafiken, Anmerkungen zum Text in verschiedenen Farben oder einfache ToDo-Kommentare mit Referenz zum Text schnell und unkompliziert realisieren. Eingebunden wird das Paket wie folgt.
30 30  
31 31  {{{ \usepackage{todonotes}
32 32  }}}
33 33  
34 -You can find a short manual [[over here>>url:http://www.tex.ac.uk/tex-archive/macros/latex/contrib/todonotes/todonotes.pdf||shape="rect"]].
30 +Eine kurze, detaillierte Anleitung kann man hier nachlesen:
35 35  
32 +>[[(% class="icon" %) (%%)http:~~/~~/www.tex.ac.uk/tex-archive/macros/latex/contrib/todonotes/todonotes.pdf>>url:http://www.tex.ac.uk/tex-archive/macros/latex/contrib/todonotes/todonotes.pdf||style="text-decoration: none;" shape="rect" class="ext-link"]]
33 +
36 36  = The Bibliography =
37 37  
38 38  Zur Erstellung einer Bibliographie mit LaTeX ist das Beispiel-Dokument zu Rate zu ziehen. Die dort benutzte BibTeX-Datenbank cau-rt.bib wird Lehrstuhl-weit von Mitarbeitern und Studenten gemeinsam benutzt um Literatur-Daten zu sammeln und zu publizieren. Alle Literaturdaten, die in studentischen Arbeiten anfallen, müssen also in dieser Datei verwaltet werden. **Wichtig:** Bitte vermeiden Sie bibtex-Warnungen beim Hinzufügen von neuen Einträgen! Weitere Hinweise zur Beachtung finden sich [[hier>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Preparing_a_Paper#The_Bibliography_-_Guidelines_for_bibtex_Entries||style="text-decoration: none;" shape="rect" class="wiki"]]
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -20153343
1 +7701006
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/20153343/Technical Stuff
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/7701006/Technical Stuff