Style Guide Background C++ is one of the main development languages used by many of Google’s open- source projects. As every C++ programmer knows, the language has many powerful features, but this power Style is a bit of a misnomer, since these conventions cover far more than just source file formatting. Most open-source projects developed by Google conform to the requirements in this guide. Note that ___H_. To guarantee uniqueness, they should be based on the full path in a project’s source tree. For example, the file foo/src/bar/baz.h in project foo should have the following guard: #ifndef

document serves as the complete definition of Google’s coding standards for source code in the Java™ Programming Language. A Java source file is described as being in Google Style if and only if it adheres to Optional formatting choices made in examples should not be enforced as rules. 1 2 Source file basics 2.1 File name The source file name consists of the case-sensitive name of the top-level class it contains contains (of which there is exactly one), plus the .java extension. 2.2 File encoding: UTF-8 Source files are encoded in UTF-8. 2.3 Special characters 2.3.1 Whitespace characters Aside from the line terminator

pylint over your code. Definition: pylint is a tool for finding bugs and style problems in Python source code. It finds problems that are typically caught by a compiler for less dynamic languages like C sharing code from one module to an- other. Pros: The namespace management convention is simple. The source of each identifier is indicated in a consistent way; x.Obj says that object Obj is defined in module == 4: print x, y x, y = y, x No: if x == 4 : print x , y x , y = y , x No whitespace before the open paren/bracket that starts an argument list, in- dexing or slicing. Yes: spam(1) No: spam (1) Yes:

https://www.tugraz.at/sites/rdm/home/  Toni Ross-Hellauer  Ilire Hasani-Mavriqi / Sarah Stryeck (ISDS): Open and Reproducible Research Group (ORRG)  TU Graz RDM Policy since 12/2019, towards faculty-specific meta data; registered/indexes and searchable  #2 Accessible  Metadata and data retrievable via open, free and universal comm protocols  Metadata accessible even when data no longer available  #3 Self-contained Experiments Bundles http://sciunit.run Sumatra Numerical Simulations https://github.com/ open-research/sumatra 29 706.015 Introduction to Scientific Writing – 03 Experiments & Reproducibility

Understanding/Evaluation  Skepticism  Critical reading is important for understanding and evaluation  #1 Start open-minded, listen to arguments and trust provided evidence  #2 Don’t accept superficial, contradictory

Author comment 3. File description comment, including purpose of program, inputs, and out- puts 4. source() and library() statements 5. Function definitions 6. Executed statements, if applicable (e.g., print

of Technology, WS 2020/21 References  Setup  Use LaTeX \cite{} and BibTeX  Use a consistent source of bibtex entries (e.g., DBLP)  Different References Styles  But, not in footnotes (unless required)