Skip to Content

Changes for page Technical Stuff

Last modified by Alexander Schulz-Rosengarten on 2025/10/21 14:40
From version 15.1
edited by nbw
on 2017/04/26 12:21
Change comment: There is no comment for this version
To version 17.1
edited by Niklas Rentz
on 2022/03/08 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.nbw
1 +XWiki.nre
Content
... ... @@ -6,7 +6,7 @@
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. 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||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. 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  
... ... @@ -16,7 +16,7 @@
16 16  * [[The excellent Git tutorial>>url:https://www.atlassian.com/git/tutorial||shape="rect"]], written by  the guys at Atlassian
17 17  * The Git page in our KIELER Wiki: [[doc:KIELER.Using Git]]
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 Bitbutcket 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}} (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 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 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 22  
... ... @@ -39,7 +39,7 @@
39 39  
40 40  = The Bibliography =
41 41  
42 -Proper bibliographies in LaTeX are built using bibtex, which allows you to store information about publications in so-called bib files with identifiers that you can use to reference them from your main LaTeX document. In a desperate attempt to keep everything neat and tidy, we have [[a central bib Git repository>>url:https://git.rtsys.informatik.uni-kiel.de/projects/RES/repos/bib/browse||shape="rect"]] which contains bib files we use and occasionally add to:
42 +Proper bibliographies in LaTeX are built using bibtex, which allows you to store information about publications in so-called bib files with identifiers that you can use to reference them from your main LaTeX document. In a desperate attempt to keep everything neat and tidy, we have [[a central bib Git repository>>url:https://git.informatik.uni-kiel.de/ag-rtsys/tex/bib||shape="rect"]] which contains bib files we use and occasionally add to:
43 43  
44 44  * cau-rt.bib: The main database which contains publications we reference, but have not written ourselves.
45 45  * pub-rts.bib: The database containing our own publications.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -121864193
1 +122159110
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/121864193/Technical Stuff
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/122159110/Technical Stuff