writing C++ code. These rules exist to keep the code base manageable while still allowing coders to use C++ language features produc- tively. Style, also known as readability, is what we call the conventions (for example, transfer of pointer ownership), leaving textual hints for the reader at the point of use is valuable (std::unique_ptr demonstrates the ownership transfer unambiguously at the call site). Be consistent with the broader C++ community when appropriate Consistency with the way other organizations use C++ has value for the same reasons as consistency within our code base. If a feature in the C++ standard

annotation type (@interface). 2. The term comment always refers to implementation comments. We do not use the phrase “documentation comments”, instead using the common term “Javadoc.” Other “terminology notes” 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 (of which there is exactly one), plus the .java escapes outside string literals and comments are strongly dis- couraged. Tip: In the Unicode escape case, and occasionally even when actual Unicode characters are used, an explanatory comment can be very

list of pylint warnings by doing pylint --list-msgs. To get more information on a particular message, use pylint --help-msg=C6409. Prefer pylint: disable to the deprecated older form pylint: disable-msg. For example: def foo(a, unused_b, unused_c, d=None, e=None): _ = d, e return a Imports link￿ Use imports for packages and modules only. Definition: Reusability mechanism for sharing code from one 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 the module name 3 with no prefix. Use from x import y as z if two

Our experiments show that CLA achieves in-memory operations performance close to the uncompressed case and good compression ratios that allow us to fit larger datasets into available memory. % 4. Say submission: 12 pages (+ more figures, experiments, etc)  Solid, Reproducible Experiments  Create, use, and share dedicated benchmarks / datasets  Avoid weak baselines, start early w/ baseline comparisons Matthias Boehm, Graz University 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

on same line, last on own line 7. else: Surround else with braces 8. Assignment: use <-, not = 9. Semicolons: don’t use them 10. General Layout and Ordering 11. Commenting Guidelines: all comments begin Identifiers Don’t use underscores ( _ ) or hyphens ( - ) in identifiers. Identifiers should be named according to the following conventions. The preferred form for variable names is all lower case letters and Length The maximum line length is 80 characters. Indentation When indenting your code, use two spaces. Never use tabs or mix tabs and spaces. Exception: When a line break occurs inside parentheses, align

Representative of real data distributions? Representative for variety of workloads / common case? 9 706.015 Introduction to Scientific Writing – 03 Experiments & Reproducibility Matthias Boehm SW components: OS, programming language, versions, other software  Baselines and configuration  Use recent versions of baseline systems  Data and workloads w/ data sizes, parameters, configurations Reproducibility Matthias Boehm, Graz University of Technology, WS 2021/22 Presentation – Figures  Axes  Use Informative axes labels with units (e.g., Total Execution Time [ms])  Don’t cheat or mislead readers

missing pieces, missing experiments, missing related work? Scientific Reading  Read out loud  Use PDF-to-Speech 11 706.015 Introduction to Scientific Writing – 02 Scientific Reading and Writing Matthias fonts, underlining) creates a bad first impression  Recap: skimming and anchoring  Figures  Use same font and font size as the main text / code in main paper  Avoid text overlap, too aggressive Widows  Imprecise definition  Avoid few words per line, single line at next page  Highlighting  Use \emph{} (emphasize) over underlining or bold Scientific Writing “The paper’s approach is probably