Skip to content

Instantly share code, notes, and snippets.

@danielronnkvist
Created November 21, 2014 09:23
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save danielronnkvist/2419edd70d24dc86ccb5 to your computer and use it in GitHub Desktop.
Save danielronnkvist/2419edd70d24dc86ccb5 to your computer and use it in GitHub Desktop.
From a lecture 2014-11-20

Writing lab reports

Lecture by Shelly Torgnyson, 2014-11-20

Do as much work as possible for the draft session. Have questions ready before the five minute session with Shelly.

Simple report structure

  • Title page
  • Abstract optional only
  • Introduction
  • Method/Materials
  • Results
  • Discussions
  • Conclusion
  • Appendix(only if necessary)

Title page

  • the title of experiment/project
  • write names and group number
  • List of instructors name (Anna, Shelly, (Lab Assistant))
  • date that experiment was performed
  • Submission date

Abstract

Very short summary. Gives a broad outcome of whats about to come.

  • purpose
  • scope
  • findings

More than 150 words. Contains no details, no numbers/references and so on.

Introduction

Think of who is about to read this report. The language is commonly in presence form.

Subject

Define topic and associated terminology. May include history and theory.

Purpose

Indicates the reason

Scope

Indicates the extentended limits of the investiation.

Methods and materials

Use tables, graphs, diagrams, figures.. to illustrate your findings. Make sure your text where you reference(reference like this: (Fig. 8)) the illustraions.

Tables

The information should be on top of the table. Be consistent in your tables. Should be centered on the page. Make sure you reference the table in the text. (Reference like: See table 1).

Equations

Number consecutively. Use parentheses (1) (2) (3)

Equation centered, but equation number to the right margin but not to close to equation itself. Reference like: Calculated by using (1), but if you have to start a scentence do: Equation (1)...

If you have to reference an illustration many times throughout the text put the illustration in the appendix.

Language for data

Use the present tense.

Table 1 displays, shows, exhibits..

The graph clearly illustrates.. not The graph is clearly illustrating.., skip the ing.

Result and Discussion

Describes what you learned. Use the past tense here.

Result

What didi you learn about the problem throughout your reasearch?

Discussion

What could have done differently? How accurate are your findings?

Conclusion

Restatement of Results. Concluding remarks.

Appendices

Plural: Appendices

Singular: Apendix

All appendices have to refered to in the text. Make sure they are clearly labeled.

Appendix A. Data sheets.. Appendix B. Data tables..

Scientific writing styles

Write in complete, grammatically correct sentences. If most of your sentences(4 or more 'clauses' or parts) you will confuse the reader.

Be concise. If you can choose one work instead of a phrase, choose one word(ex. get around = avoid)

Be objective. Limit your use of personal pronouns. Skip emotionally loaded words. Don't be casual(The reaction carried on for 10 minutes).

Use technical terms correctly. Learn what they mean, how to use them and how to spell them. Use the glossary provided by Anna on Lisam.

Do not use contraction! (isn't, doesn't, it's). Common in speech but not in formal writing.

DOs and DON'Ts

DO:

  • use appropriate tense.
  • Keep a consistent style.
  • Ensure all figures have appropriate numbered captions.
  • Reference source material if relevant
  • re-read many times

DON'Ts:

  • just list instructions
  • give detailed arithmetic or algebraic equations
  • use jargon or undefined
  • make excessive use of personal style of "I" or "we". (Can be written in discussion but rather not)

Some notes

  • Title page on its own cover.
  • Get rid of the ing in words.
  • Never usually more then 4 pages.
  • 3-4 pages of text
  • Is it happening now? Is it happening all the time? Has it happened?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment