1 SCIENCE PASSION TECHNOLOGY Introduction to Scientific Writing 01 Structure of Scientific Papers Matthias Boehm Graz University of Technology, Austria Institute of Interactive Systems and Data Science Technology, WS 2020/21 Agenda  Data Management Group  Course Organization, Outline, and Projects  Structure of Scientific Papers  Paper Project Proposals 4 706.015 Introduction to Scientific Writing – and Overview Matthias Boehm, Graz University of Technology, WS 2020/21 Outline Lectures  01 Structure of Scientific Papers [Oct 28, 6.15pm, optional]  02 Scientific Reading and Writing [Nov 04, 6pm

virtual function will not compile, and this helps catch common errors. The specifiers serve as documentation; if no specifier is present, the reader has to check all ancestors of the class in question to a function exceeds about 40 lines, think about whether it can be broken up without harming the structure of the program. Even if your long function works perfectly now, someone modifying it in a few months numbers that are never negative. This is intended as a form 37 of self-documentation. However, in C, the advantages of such documentation are outweighed by the real bugs it can introduce. Consider: for (unsigned

(@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” will appear occasionally properly. If that should happen, those programs are broken and they must be fixed. 3 Source file structure A source file consists of, in order: 1. License or copyright information, if present 2. Package discouraged). 4. As required by other sections of this document (such as Section 3, Source file structure, and Section 3.3, Import statements). Multiple consecutive blank lines are permitted, but never

paper/thesis is about  Read abstract, and optionally introduction scan paper (sections/subsections, structure, figures)  Understanding  Goal: understand how the presented approach accomplishes the paper’s University of Technology, WS 2021/22 Process of Reading – Skimming/Understanding  Abstract and Structure  #1 Partial Reading (mostly skimming)  Read into each paragraph until you get what it’s about self-explanatory figures (close to text), and structure  Avoid unnecessary formalism  as simple as possible  Shortening the text in favor of structure improves readability  Ex. Compressed Linear Algebra

you can’t start at 0 [J. Sommer, M. Boehm, A. V. Evfimievski, B. Reinwald, P. J. Haas: MNC: Structure- Exploiting Sparsity Estimation for Matrix Expressions. SIGMOD 2019] 15 706.015 Introduction harvard.edu/ #Guidelines] [J. Sommer, M. Boehm, A. V. Evfimievski, B. Reinwald, P. J. Haas: MNC: Structure- Exploiting Sparsity Estimation for Matrix Expressions. SIGMOD 2019] 27 706.015 Introduction (all students) Paper Project Selection Alternative: LV combined with bachelor thesis See 01 Structure of Scientific Papers for project list 31 706.015 Introduction to Scientific Writing – 03 Experiments

inline comments 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 unit tests should serve as sample function calls (for shared library rou- tines). Function Documentation Functions should contain a comments section immediately below the function definition line. These

example.com/us/developer/documentation/api/content/v2.0/csv_file_name_extension_full_specification.html 16 No: # See details at # https://www.example.com/us/developer/documentation/api/content/\ # v2.0/