is not the same as a license to proceed. Use your judgment, and if you are unsure, please don’t hesitate to ask your project leads to get additional input. Header Files In general, every .cc file should includes. Of course, keep your system-specific code small and localized. Example: #include "foo/public/fooserver.h" #include "base/port.h" // For LANG_CXX11. #ifdef LANG_CXX11 #include All declarations are within the namespace scope. // Notice the lack of indentation. class MyClass { public: ... void Foo(); }; } // namespace mynamespace // In the .cc file namespace mynamespace { // Definition

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 section that is present. 3.1 License or or copyright information, if present If license or copyright information belongs in a file, it belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section Examples: return () -> { while (condition()) { method(); } }; return new MyClass() { @Override public void method() { if (condition()) { try { something(); } catch (ProblemException e) { recover(); }

returned by functions. • If needed, globals should be made internal to the module and accessed through public module level functions; see Naming below. Nested/Local/Inner Classes and Functions link￿ Nested/local/inner guidelines for doc strings below. Modules Every file should contain license boilerplate. Choose the appropriate boilerplate for the license used by the project (for example, Apache 2.0, BSD, LGPL, GPL) Functions Classes should have a doc string below the class definition describing the class. If your class has public attributes, they should be documented here in an At- tributes section and follow the same formatting

Reusable  Metadata and data described with plurality of accurate and relevant attributes  Clear license, associated with provenance, meets community standards Reproducibility and RDM [https://www.go-fair http://commonwl.org Popper Container Workflows https://github.com/ systemslab/popper ReproZip General-purpose Bundles http://reprozip.org Sciunit Self-contained Experiments Bundles http://sciunit.run

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 with # followed by a space; inline omitted for consistency with other Google style guides.) Organization General Layout and Ordering If everyone uses the same general ordering, we’ll be able to read and understand each other’s scripts faster

Scientific Writing Figure~\ref{fig:exp1} Equation~\eqref{eq:e1} employ general-purpose compression techniques employ a general-purpose compression technique Each entry ???????????????????????? can

the data into single-node or distributed main memory. % 2. Say why it's an interesting problem General-purpose, heavy- and lightweight compression techniques struggle to achieve both good compression