Skip to Content

Changes for page Technical Stuff

Last modified by Alexander Schulz-Rosengarten on 2025/10/21 14:40
From version 12.1
edited by cds
on 2015/07/22 13:49
Change comment: There is no comment for this version
To version 20.1
edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:24
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +RTSYS.Rtsys Group Wiki.Writing Guides.Writing and Grading Theses.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.als
Content
... ... @@ -6,26 +6,30 @@
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.numerik.uni-kiel.de/~~discopt/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. That is, you should have your advisor create a Git repository for your thesis, familiarize yourself with [[LaTeX>>url:http://de.wikipedia.org/wiki/LaTeX||style="text-decoration: none;" rel="nofollow" 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.
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. If you haven't used Git yet, there's a few excellent introductions to be found on the internet, for example:
14 14  
15 15  * [[The Git book>>url:http://git-scm.com/book/||shape="rect"]]
16 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]]
17 +* The Git page in our KIELER Wiki: [[doc:Kieler.Development.Guidelines.Using Git.WebHome]]
18 18  
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}}.
19 +The main tex file for a thesis should be {{code language="none"}}<name of repository>.tex.{{/code}} 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 GitLab system>>url:https://git.informatik.uni-kiel.de/ag-rtsys/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 -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.
21 +See also the notes on [[preparing a paper>>doc:RTSYS.Rtsys Group Wiki.Writing Guides.Writing Papers.WebHome]], e.g. regarding which files should be kept in Git and which shouldn't.
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.
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:
26 26  
27 -= The ToDo Package =
27 +* On all platforms, including Mac, texmaker is a fine editor.
28 +* Atom and Sublime have plug-ins that provide LaTeX syntax highlighting and an integrated compilation workflow.
29 +* Kile is a LaTeX IDE which runs on KDE and is powerful and reasonably easy to understand and to use
28 28  
31 += The ToDo Notes Package =
32 +
29 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:
30 30  
31 31  {{{ \usepackage{todonotes}
... ... @@ -32,58 +32,3 @@
32 32  }}}
33 33  
34 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"]].
35 -
36 -= The Bibliography =
37 -
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"]]
39 -
40 -Das Erstellen eines deutschsprachigen Literaturverzeichnisses ist mit Hilfe des Paketes //bibgerm// und dem bibliographystyle //gerplain// möglich.
41 -
42 -{{{ \usepackage[ngerman]{babel}
43 - \usepackage{bibgerm}
44 - .
45 - .
46 - .
47 - \bibliographystyle{gerplain}
48 -
49 -}}}
50 -
51 -Links zu BibTeX:
52 -
53 -* [[(% class="icon" %) (%%)BibTeX-Tutorial>>url:http://www.din1505.informationskompetenz.net/||style="text-decoration: none;" shape="rect" class="ext-link"]] (Link ist tot)
54 -* [[(% class="icon" %) (%%)Tame the BeaST - The B to X of BibTEX (Nicolas Markey)>>url:ftp://dante.ctan.org/tex-archive//info/bibtex/tamethebeast/ttb_en.pdf||style="text-decoration: none;" shape="rect" class="ext-link"]]
55 -* [[(% class="icon" %) (%%)Eine Auflistung von BibTEX Styles>>url:http://www.reed.edu/cis/help/latex/bibtexstyles.html||style="text-decoration: none;" shape="rect" class="ext-link"]]
56 -
57 -== Work Within the RTSYS Domain ==
58 -
59 -Beim Arbeiten im Lehrstuhl-Netzwerk werden keine zusätzlichen Maßnahmen notwendig; der LaTeX-Zugriff auf die BibTeX-Datenbank ist automatisch über das Netzwerk gewährleistet. Für verändernde Zugriffe auf die Datenbank muss mit dem Versionsmanagement earbeitet werden.
60 -
61 -== Work Outside the RTSYS Domain ==
62 -
63 -Beim Arbeiten außerhalb des Lehrstuhl-Netzes wird es notwendig, die Datenbank dem lokal installierten LaTeX-System zur Verfügung zu stellen. Eventuell muss die dazugehörige kpse-Datenbank reinitialisiert werden.
64 -
65 -== Accessing the Git-Repository of the BibTeX Files ==
66 -
67 -Für Zugriff auf das [[Git-Repository >>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Git||style="text-decoration: none;" shape="rect" class="wiki"]]der BibTeX-Datenbank ist folgender Befehl zu verwenden
68 -
69 ->git clone git@…:resources/bib.git
70 -
71 -Nach dem Auschecken des Moduls bib steht die Datei cau-rt.bib zur Verfügung. Hinweise zur genauen Syntax sind dem Kopf der Datei und den Beschreibungen der BibTeX-Sprache zu entnehmen.
72 -
73 -= Publishing the thesis on-line =
74 -
75 -If your advisor has agreed that your thesis should be made available on-line, and you have signed your[[(% class="icon" %) (%%)consent>>url:http://www.informatik.uni-kiel.de/fileadmin/arbeitsgruppen/realtime_embedded/misc/Einverstaendniserklaerung.doc||style="text-decoration: none;" shape="rect" class="ext-link"]], then you can publish this as follows. Say your thesis is xyz-bt.pdf. ("bt" for Bachelor theses, "mt" for Master theses, "diss" for dissertations.) To upload this, use the command
76 -
77 ->scp xyz-bt.pdf biblio@…:/home/biblio/public_html/downloads/theses
78 -
79 -If you don't have the right permissions to do this, ask your advisor or the [[System Administrator >>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/System_Administrator||style="text-decoration: none;" shape="rect" class="wiki"]]to publish this for you.
80 -
81 -Then, check that your thesis is indeed available under the URL
82 -
83 ->[[(% class="icon" %) (%%)http:~~/~~/rtsys.informatik.uni-kiel.de/~~~~biblio/downloads/theses/xyz-bt.pdf>>url:http://rtsys.informatik.uni-kiel.de/%7Ebiblio/downloads/theses/xyz-bt.pdf||style="text-decoration: none;" shape="rect" class="ext-link"]]
84 -
85 -Note: The name of this file should follow the canonical naming scheme used in subversion ([[Subversion/Structure >>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Subversion/Structure||style="text-decoration: none;" shape="rect" class="wiki"]]), even if your thesis is for some reason not in the subversion system.
86 -
87 -= Source Code =
88 -
89 -Von Ihnen im Laufe der Arbeit entwickelte Software (oder Hardware-Beschreibungen) sind Teil Ihrer Arbeit. Dies bedeutet: es sollte eine Übersicht über die Software in geeigneter Form gegeben werden, z.B. in Form von Klassendiagrammen mit Erläuterungen. Hinweise zum Einbinden von Code in LaTeX finden sich in dem[[(% class="icon" %) (%%)Beispieldokument>>url:http://www.informatik.uni-kiel.de/%7Ert-kiel/kiel/documents/papers/example.tar.gz||style="text-decoration: none;" shape="rect" class="ext-link"]] (s.o.).
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -13008944
1 +7700977
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/13008944/Technical Stuff
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/7700977/Technical Stuff