Skip to content

Opposition checklist

For your opposition of your assigned group, you are expected to prepare an oral and written opposition before the final presentation occasion. The oral opposition is carried out during the final presentation occasion. The written opposition should be sent to the other group after the final presentation occasion. Below you can find some checklists of what should be included in these two types of oppositions.

Oral opposition

The oral opposition should focus on questions that stimulates a scientific discussion with the group's report as a basis, such as:

  • How does the work relate to existing literature?
  • Do their work agree/conflict with existing literature and is this reasonable or not (from your perspective)?
  • What are the conclusions and what do you think about them?
  • Are they solving their stated research question?

Avoid bringing up grammatical errors and similar details from the report; it is not suited for an oral opposition and is better left to the written opposition.

Written opposition

The written opposition is more flexible and here you are free to comment on anything in the written report (grammar, text structure, readability, figures, references etc.). Remember, it is also worth pointing out things that you think are good. You are also supposed to test the code associated with the report. Here, we expect that a README will be provided that explains how the code should be run. We expect that you should be able to generate the figures from the report by running a single file, i.e. named PlotReportFigures.py. We do not expect you to go over all the code in detail, but to do some checks on code readability and if good coding practices are adhered to. Remember, the code is our research methodology and if it is not easy to understand we cannot expect our research to be accessible to others, nor reproduced.

Written report

  • Readability.
  • Text structure (Consult the checklist for report writing document).
  • Is the research question answered.
  • Are the references cited correctly.

Figures

  • Are the figures readable.
  • Are the figures referred to and used in the text.
  • Are the figure legends descriptive enough for the figure to be understood without the main text.

The code

  • Is a README file provided.
  • Is a list of all needed packages provided (if python; pip packages).
  • Can you generate the figures in the report by following the instructions in the README file.
  • Is the code readable.
  • Does the code adhere to good coding practices.