anyway. This principle mostly explains the rules we don’t have, rather than the rules we do: for example, goto contravenes many of the following principles, but is already vanishingly rare, so the Style of this principle: When some- thing surprising or unusual is happening in a snippet of code (for example, transfer of pointer ownership), leaving textual hints for the reader at the point of use is valuable 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 FOO_BAR_BAZ_H_

” Other “terminology notes” will appear occasionally throughout the document. 1.2 Guide notes Example code in this document is non-normative. That is, while the examples are in Google Style, they may when actual Unicode characters are used, an explanatory comment can be very helpful. Examples: Example Discussion String unitAbbrev = "￿s"; Best: perfectly clear even without a comment. String unitAbbrev unitAbbrev = "\u03bcs"; // Greek letter mu, "s" Allowed, but awkward and prone to mistakes. 2 Example Discussion String unitAbbrev = "\u03bcs"; Poor: the reader has no idea what this is. return '\ufeff'

changing the argument names is infeasible, you can mention them at the beginning of the function. For example: def foo(a, unused_b, unused_c, d=None, e=None): _ = d, e return a Imports link￿ Use imports import y as z if two modules named y are to be imported or if y is an inconveniently long name. For example the module sound.effects.echo may be imported as follows: from sound.effects import echo ... echo for cleanup, i.e., closing a file. • When capturing an exception, use as rather than a comma. For example: try: raise Error except Error as error: pass Global variables link￿ Avoid global variables.

conferences/journals (act as filter)  Make the paper useful for others (ideas, evidence, code)  Example (my own theses/books)  Seminar (~bachelor), 5 months, 446 pages  Diploma (~master), 9 months, Camera-ready  Similar: bachelor/master thesis  drafts to advisor / final version  Demo CMT  Example DEEM 2021, PVLDB 2022 Structure of Scientific Papers [Simon Peyton Jones: How to write a great good research, get it published in SIGKDD and get it cited!, KDD 2009] [Recommended Reading] Example SIGMOD 2020 October 15, 2019: Abstract submission October 22, 2019: Paper submission December 10

need two spaces before the # 12. Function Definitions and Calls 13. Function Documentation 14. Example Function 15. TODO Style: TODO(username) Summary: R Language Rules 1. attach: avoid using it 2. descriptive enough that a caller can use the function without reading any of the function’s code. Example Function CalculateSampleCovariance <- function(x, y, verbose = TRUE) { # Computes the sample covariance

& Reproducibility Matthias Boehm, Graz University of Technology, WS 2021/22 RDM in Practice – Example So2Sat LCZ42  Data and ML Pipelines  ESA Sentinel-1/2 datasets  4PB/year  Training of local & Reproducibility Matthias Boehm, Graz University of Technology, WS 2021/22 RDM in Practice – Example So2Sat LCZ42, cont. Reproducibility and RDM [So2Sat LC42 Dataset https://mediatum.ub.tum.de/1454690]

Matthias Boehm, Graz University of Technology, WS 2021/22 Plagiarism – Duplicate Submission  Example SIGMOD’21 A research paper submitted to SIGMOD 2021 cannot be under review for any other publishing