Scientific Writing

This repository contains tips regarding scientific writing and a LaTeX template for conferences. It is synced with an Overleaf project. If you publish associated open-source code, provide the BibTeX in the README.md, provide a CITATION.ccf file and link the official code to the arXiv Code & Data tab.

Tools

• Overleaf to write your paper in LaTeX
• LanguageTool (in "acribic mode") or Grammarly to check your writing style
• Zotero for your literature management. Can be synced with Overleaf
• Tables Generator for LaTeX tables

Overleaf Import

Download the GitHub project as a ZIP file

Import the ZIP file in Overleaf as a new project

Paper Style

"Get the gestalt right. I remember being impressed with Fei-Fei (my adviser) once during a reviewing session. I had a stack of 4 papers I had reviewed over the last several hours and she picked them up, flipped through each one for 10 seconds, and said one of them was good and the other three bad. Indeed, I was accepting the one and rejecting the other three, but something that took me several hours took her seconds." - Andrej Karpathy, Head of AI at Tesla

Key aspects: - Abstract, Introduction and pull-figure on page 1, making the "Related Work" headline the first line on page 2 - ~1 page related work section with a good density of citations - not too sparse, but not too crowded - A well-designed pull figure on page 1, typically in the upper right corner - A well-designed system figure on page 3, spanning the whole page width - Exactly 8 pages (or the page limit) and not a single line less

Use a color palette that is suited for colorblind people, such as the ones proposed by David Nichols:

Citations

• Use \"{o} instead of ö, \'{e} instead of é etc. to avoid issues
• Use the lastname1, firstname1 and lastname2, firstname2 format for the author list
• Put the title in {{title}}, this preserves the desired upper and lower case
• Use citation styles consistently
• Cite arXiv only if it is the only version of a paper (but keep in mind there is a trend towards arXiv citations)
• Add non-breaking spaces, so references don't slide to the next line: [...] in~\cite{} [...] instead of [...] in \cite{} [...]
• Use archive.org for archived versions of websites from the date you accessed them

Citation types:

arXiv

@article{Bogdoll_Taxonomy_2021_arXiv, author = {Bogdoll, Daniel and Orf, Stefan and T\"{o}ttel, Lars and Z\"{o}llner, J. Marius}, title = {{Taxonomy and Survey on Remote Human Input Systems for Driving Automation Systems}}, journal = {arXiv preprint:2109.08599}, year = {2021} }

Conference proceedings

@inProceedings{Bogdoll_Addatasets_2022_VEHITS, author = {Bogdoll, Daniel and Schreyer, Felix and Z\"{o}llner, J. Marius}, title = {{ad-datasets: a meta-collection of data sets for autonomous driving}}, booktitle = {Proceedings of the 8th International Conference on Vehicle Technology and Intelligent Transport Systems}, year = {2022} }

Published without proceedings

@article{Bogdoll_Compressing_2021_NeurIPS, author = {Bogdoll, Daniel and Jestram, Johannes and Rauch, Jonas and Scheib, Christin and Wittig, Moritz and Z\"{o}llner, J. Marius}, title = {{Compressing Sensor Data for Remote Assistance of Autonomous Vehicles using Deep Generative Models}}, journal = {NeurIPS Conference on Neural Information Processing Systems Workshop on Machine Learning for Autonomous Driving (ML4AD)}, year = {2021} }

Journal article

@article{choi_kaist_2018_its, author = {Choi, Yukyung and Kim, Namil and Hwang, Soonmin and Park, Kibaek and Yoon, Jae Shin and An, Kyounghwan and Kweon, In So}, title = {{KAIST Multi-Spectral Day/Night Data Set for Autonomous and Assisted Driving}}, journal = {IEEE Transactions on Intelligent Transportation Systems}, volume = {19}, year = {2018} }

Student Thesis

@mastersthesis{Guneshka_Ontology_2022_BA, author = {Guneshka, Stefani}, title = {{Ontology-based corner case scenario simulation for autonomous driving}}, school = {{Karlsruhe Institute of Technology (KIT)}}, year = {2022}, type = {Bachelor's Thesis} }

PhD Thesis

@phdThesis{Kuhnt_Holistic_2020_PhD, author = {Kuhnt, Florian}, title = {{Holistic Temporal Situation Interpretation for Traffic Participant Prediction}}, school = {Karlsruhe Institute of Technology (KIT)}, year = {2020} }

Patent

@patent{Bogdoll_Augmenting_2017_US, author = {Bogdoll, Daniel and Paudel, Shreyasha and Koduri, Tejaswi}, title = {{Augmenting Real Sensor Recordings With Simulated Sensor Data}}, number = {US20190065933A1}, year = {2017} }

Website

@misc{Asam_Openscenario_2020_Web, author = {{ASAM}}, title = {{ASAM OpenSCENARIO®}}, howpublished = {\url{https://web.archive.org/web/20220104123527/https://www.asam.net/standards/detail/openscenario/}}, year = {2021}, note = {Accessed: 2022-01-01} }

Talk published online

@online{Anguelov_Machine_2022_INSAIT, author = {Anguelov, Dragomir}, title = {Machine Learning for Autonomous Driving}, url = {https://www.youtube.com/watch?v=aEWyr3HAO7M}, organization = {INSAIT Conference}, year = {2022}, urldate = {2023-03-28} }

Standards/Whitepapers/Reports

@techreport{SAE_J3016_2021_Standard, author={{On-Road Automated Driving Committee}}, institution={{SAE International}}, number={J3016-202104}, title={{Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles}}, type={Standard}, year={2021} }

@techreport{IEEE_2846_2022_Standard, author={{Intelligent Transportation Systems Committee}}, institution={{IEEE}}, number={2846-2022}, title={{Standard for Assumptions in Safety-Related Models for Automated Driving Systems}}, type={Standard}, year={2022} }

English for Germans

Writing Style

A sentence should not be longer than 25 words.

| Writing Style | Negative Example | Positive Example | Explanation | ----------- | ----------- | ----------- | ----------- | | Active Voice | An error has occurred with your account, but every attempt was made to remedy it. | We made an error with your account, but we have made every attempt to remedy it. | Makes the text much easier to comprehend | | Oxford Comma | We monitored temperature, pressure and volume. | We monitored temperature, pressure, and volume. | The comma ensures that the last two items are not beeing understood as one | | Hyphen | Please bring the report up-to-date. | Please deliver an up-to-date report. | Use hyphens to describe nouns | | Verbs instead of abstract nouns | Examination of the metal components was carried out... | We examined the metal components... | Text is easier to read out aloud (max 1 breath per sentence) | Parallel Structures | Our investigation has two goals: ° to discover root causes of production problems, ° eliminating uncertainties in design processes | Our investigation has two goals: ° to discover root causes of production problems, ° to eliminate uncertainties in design processes | Structured lists

Tenses

• Present Tense: What is known
• Past Tense: What you did
• Future Tense: What comes after the paper

| Section | Tense | Notes | ----------- | ----------- | ----------- | | Abstract | Past or Present | Present for general statements and facts | Introduction | Present | Research question: Past, Present or Future | | State of the Art | Past or Present | If something is always true, then it should be written in present tense | | Method | Past | | | Evaluation | Past or Present | Specific results in Past, more general ones in Present | | Conclusion | Present or Future | Future for Outlook |