Changes for page Technical Stuff
Last modified by Alexander Schulz-Rosengarten on 2025/10/21 14:40
<
>
edited by Reinhard von Hanxleden
on 2013/09/12 16:42
on 2013/09/12 16:42
edited by Reinhard von Hanxleden
on 2013/09/12 17:11
on 2013/09/12 17:11
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,17 +6,13 @@ 6 6 7 7 = Use LaTeX and the KCSS Style = 8 8 9 - Grundsätzlich steht esIhnenfrei,wieSie IhreArbeiterstellen-mit [[(% class="icon"%)(%%)LaTeX>>url:http://de.wikipedia.org/wiki/LaTeX||rel="nofollow" style="text-decoration: none;" shape="rect" class="external-link"]]odereinemOffice-Paket(oderauch handschriftlich). Eswird jedoch dringendnahegelegt,LaTeX zu verwenden,dahiermitauchgrößereArbeitenmitumfangreichenQuerverweisen etc.(relativ)problemloszuerstellensindund einkonsistentgutesLayouterzeugtwerdenkann.Auchgibteshierzu eine recht umfassendetechnische Unterstützung, incl. Templates undeinergemeinsamgepflegtenBibliographie-Datenbank.Infolgenden Hinweisenwird deswegenangenommen,dassSie LaTeXverwenden,sowieBibTeX für die Bibliographie. Beideswirdweiteruntenerläutert.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 - Das Layout Ihrer Arbeit sollte der Kiel Computer Science Series (KCSS) entsprechen. Auf der [[KCSS-Seite>>url:http://www.informatik.uni-kiel.de/kcss/||rel="nofollow"shape="rect" class="external-link"]] sind ein LaTeX-Stylefile und umfangreiche Dokumentation hierzu verfügbar. Sollten Sie nicht LaTeX verwenden, bzw. nicht den KCSS-Style, ist eine technischeUnterstützung IhrerArbeitnur eingeschränkt möglich.11 += Use Git = 12 12 13 -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 the KCSS style, and adapt/fill in the 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. 14 - 15 -= Using Git = 16 - 17 17 The files associated with the thesis should be kept in the group's [[Git>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Git||style="text-decoration: none;" shape="rect" class="wiki"]] repository. The main purpose is to prevent loss of data. It also facilitates access for fellow group members if needed, and to allow on-line publication. 18 18 19 -The main tex file for a thesis should be <name of directory>.tex. 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. Eg, the bachelor thesis of user xyz can be found in a repository named xyz-bt in the Thesss project of our [[(% class="icon" %) (%%)Gitorious>>url:https://git.rtsys.informatik.uni-kiel.de/projects||style="text-decoration: none;" shape="rect" class="ext-link"]] 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 directory>-talk.tex; eg xyz-bt-talk.tex. In case your thesis should be made available on-line, the same names should be used, eg, xyz.pdf.15 +The main tex file for a thesis should be <name of directory>.tex. 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. Eg, the bachelor thesis of user xyz can be found in a repository named xyz-bt in the Thesss project of our[[(% class="icon" %) (%%)Gitorious>>url:https://git.rtsys.informatik.uni-kiel.de/projects||style="text-decoration: none;" shape="rect" class="ext-link"]] 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 directory>-talk.tex; eg xyz-bt-talk.tex. In case your thesis should be made available on-line, the same names should be used, eg, xyz.pdf. 20 20 21 21 See also the notes on [[preparing a paper>>url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Preparing_a_Paper||style="text-decoration: none;" shape="rect" class="wiki"]], eg regarding which files should be kept in revision management (ie, should be checked into Git) and which shouldn't. 22 22
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -770099 11 +7700993 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/770099 1/Technical Stuff1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/7700993/Technical Stuff