Google C++ Style Guideimportant) issues. Consistency also allows for automation: tools that format your code or adjust your #includes only work properly when your code is consistent with the ex- pectations of the tooling. In many cases new portions of the codebase. When in doubt, waivers to rules of this type can be sought by asking your project leads. This is specifically important for our codebase because code ownership and team membership global namespace: name collisions across a codebase of hun- dreds of millions of lines are difficult to work with and hard to avoid if everyone puts things into the global namespace. Concede to optimization0 码力 | 83 页 | 238.71 KB | 1 年前3
02 Scientific Reading and Writing - Introduction to Scientific Writing WS2021/22Scientific Reading and Writing Matthias Boehm, Graz University of Technology, WS 2021/22 Finding Relevant Work Motivation Some research areas might be very large (e.g., index structures, compression) How of top-tier conferences/journals and find latest work These papers’ related work should provide a good categorization and discussion of related work recursive lookup By Author Sometimes there Find author publications via DBLP and other libraries By Keywords Broad survey of other related work, to augment the bias year/venue/author approach Scientific Reading 7 706.015 Introduction to Scientific0 码力 | 26 页 | 613.57 KB | 1 年前3
01 Structure of Scientific Papers - Introduction to Scientific Writing WS2021/22paper summary (7min + 3min Q&A) Timeline Today: List of projects proposals, feel free to bring your own Nov 11: project selection via email to m.boehm@tugraz.at (11.59pm) subject: [Scientific Writing] Overview Matthias Boehm, Graz University of Technology, WS 2020/21 Preparation #1 Know your Audience #2 Get your Workflow in Order Writing: LaTeX (e.g., Overleaf, TeXnicCenter), versioning (e.g., PhD thesis, 4 years, 237 pages 1st book, 5+2 years, 157 pages Structure of Scientific Papers Your reader’s time is a scarce resource 15 706.015 Introduction to Scientific Writing – 01 Introduction0 码力 | 36 页 | 1.12 MB | 1 年前3
03 Experiments, Reproducibility, and Projects - Introduction to Scientific Writing WS2021/22experiments observations and ideas for improvements Don’t be afraid of throw away prototypes that don’t work Good Research Fires Itself Initial experiments give directions for further improvements Problem-oriented Overview Proper planning helps to keep you from “getting lost” Repeatable experiments simplify your own work There is no single way how to do it right There are many ways how to do it wrong Basic latest results used for the current plots Scripts: data preparation, baselines, benchmarks Automate your experiments as much as possible Reproducibility and RDM 25 706.015 Introduction to Scientific Writing0 码力 | 31 页 | 1.38 MB | 1 年前3
Google Python Style Guidedetails that are initially hidden from view. They are marked by the triangle icon, which you see here on your left. Click it now. You should see “Hooray” appear below. Hooray! Now you know you can expand points For Emacs, the default settings should be fine. Python Language Rules Lint link Run pylint over your code. Definition: pylint is a tool for finding bugs and style problems in Python source code. It Write around it b) Suppress its warnings or c) Improve it. Decision: Make sure you run pylint on your code. Suppress warnings if they are inappropriate so that other issues are not hidden. To suppress0 码力 | 30 页 | 94.81 KB | 1 年前3
Google's R Style GuidekConstantName Syntax Line 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 Assignment Use <-, not =, for assignment. GOOD: x <- 5 BAD: x = 5 Semicolons Do not terminate your lines with semicolons or use semicolons to put more than one command on the same line. (Semicolons tests should go in a separate file named originalfilename_test.R. Commenting Guidelines Comment your code. Entire commented lines should begin with # and one space. Short comments can be placed after0 码力 | 8 页 | 47.42 KB | 1 年前3
Google Java Style Guideorder mark Good: use escapes for non-printable characters, and comment if necessary. Tip: Never make your code less readable simply out of fear that some programs might not handle non-ASCII characters properly Terminology Note: Horizontal alignment is the practice of adding a variable number of additional spaces in your code with the goal of making certain tokens appear directly below certain other tokens on previous0 码力 | 19 页 | 84.76 KB | 1 年前3
共 7 条
- 1













