structure A source file consists of, in order: 1. License or copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each in a file, it belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section 4.4, Column limit: 100) does not apply to package statements. 3.3 Import statements blocks. There are no other blank lines between import statements. Within each block the imported names appear in ASCII sort order. (Note: this is not the same as the import statements being in ASCII sort

identified by a alphanumeric code (C0112) and a sym- bolic name (empty-docstring). Prefer the symbolic names in new code or when updating existing code. If the reason for the suppression is not clear from the argument or prefixing the argument name with ‘unused_’. In situations where changing the argument names is infeasible, you can mention them at the beginning of the function. For example: def foo(a, unused_b Cons: Module names can still collide. Some module names are inconveniently long. Decision: Use import x for importing packages and modules. Use from x import y where x is the package prefix and y is

if applicable use mix of different plot types and tables  Consistency: use consistent colors and names for same baselines  Labeling  Make the plots self-contained  Simplifies skimming and avoids join Technology, WS 2021/22 SIGMOD Reproducibility Process  Overview  Accepted papers can submit package, verified by committee  ACM Results Replicated / ACM Artifacts Available labels  Most Reproducible

#include that header. • When using a class template, prefer to #include its header file. Please see Names and Order of Includes for rules about when to #include a header. 5 Inline Functions Define functions the class, either for convenience or to document its behavior, e.g., for accessors and mutators. Names and Order of Includes Use standard order for readability and to avoid hidden dependencies: Related Scoping Namespaces With few exceptions, place code in a namespace. Namespaces should have unique names based on the project name, and possibly its path. Unnamed namespaces in .cc files are encouraged.

designed in collaboration with the entire R user community at Google. Summary: R Style Rules 1. File Names: end in .R 2. Identifiers: variable.name (or variableName), FunctionName, kConstantName 3. Line Length: avoid S4 objects and methods when possible; never mix S3 and S4 1 Notation and Naming File Names File names should end in .R and, of course, be meaningful. GOOD: predict_ad_revenue.R BAD: foo.R Identifiers conventions. The preferred form for variable names is all lower case letters and words separated with dots (variable.name), but variableName is also accepted; function names have initial capital letters and no

Titles and Names  Titles: capitalize meaning-carrying words  Names: capitalize, e.g., Bayesian, Euclidean  References like Figure 1, Table 2, Section 3, Chapter 4, Equation 5 are names as well Scientific