Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Table of Contents

Use LaTeX and the KCSS Style

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 and the KCSS 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.

Use Git

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:

The main tex file for a thesis should be <name of repository>.tex (see also Git/Structure for the canonical naming scheme). E.g., the bachelor thesis of user xyz can be found in a repository named xyz-bt in the Theses project of our Stash system, in a file named xyz-bt.tex. 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 <name of repository>-talk.tex (e.g. xyz-bt-talk.tex). In case your thesis should be made available on-line, the same names should be used, e.g., xyz.pdf.

See also the notes on preparing a paper, e.g. regarding which files should be kept in Git and which shouldn't.

Editor/IDE

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

The ToDo Package

When writing your thesis, you will often want to make a note of something you need to add or change. The todonotes 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:

 \usepackage{todonotes}

You can find a short manual over here.

The Bibliography

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

Das Erstellen eines deutschsprachigen Literaturverzeichnisses ist mit Hilfe des Paketes bibgerm und dem bibliographystyle gerplain möglich.

 \usepackage[ngerman]{babel}
 \usepackage{bibgerm}
  .
  .
  .
 \bibliographystyle{gerplain}

Links zu BibTeX:

Work Within the RTSYS Domain

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.

Work Outside the RTSYS Domain

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.

Accessing the Git-Repository of the BibTeX Files

Für Zugriff auf das Git-Repository der BibTeX-Datenbank ist folgender Befehl zu verwenden

git clone git@…:resources/bib.git

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.

Publishing the thesis on-line

If your advisor has agreed that your thesis should be made available on-line, and you have signed your consent, 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

scp xyz-bt.pdf biblio@…:/home/biblio/public_html/downloads/theses

If you don't have the right permissions to do this, ask your advisor or the System Administrator to publish this for you.

Then, check that your thesis is indeed available under the URL

 http://rtsys.informatik.uni-kiel.de/~biblio/downloads/theses/xyz-bt.pdf

Note: The name of this file should follow the canonical naming scheme used in subversion (Subversion/Structure ), even if your thesis is for some reason not in the subversion system.

Source Code

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 Beispieldokument (s.o.).

  • No labels
https://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=13008942
rtsys.informatik.uni-kiel.de
crawl=CC-MAIN-2019-51
59117
application/http; msgtype=response
sha1:JH6LETX5NCVIHENHCL2Q7BNVUCJEPIDO
<urn:uuid:f1418c98-51d9-4b75-be02-8424f586e75c>
2019-12-10T06:39:22Z
134.245.253.156
text/html
sha1:Z2HQOGTBVABUFNTFKUZCWHSAFGI5WMFG
<urn:uuid:42af46ac-0ee2-4d67-8aa6-b2bc6786bcbc>
https://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=13008942
response
<urn:uuid:ca045a49-aadf-4e8e-8922-49699cf22657>
isPartOf: CC-MAIN-2019-51
publisher: Common Crawl
description: Wide crawl of the web for December 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-9.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/