GitLab

Metadata

Property	Value
Project	dumux
Category	Discussion
Reported by	Nicolas Schwenck (nicolas.schwenck@iws.uni-stuttgart.de)
Reported at	May 23, 2013 13:47
Type	Feature Request
Version	Git
Last edited by	Johannes Hommel (johannes.hommel@iws.uni-stuttgart.de)
Last edited at	Jul 14, 2016 13:08
Closed by	Johannes Hommel (johannes.hommel@iws.uni-stuttgart.de)
Closed at	Jul 14, 2016 13:08
Closed in version	unknown (Id=0)
Resolution	Implemented

Description

The DuMuX Manifest simply states: \\\"Each completed thesis (BSc, MSc, PhD) is documented as described in the DuMux handbook (guidelines). Furthermore it is committed to the repository and tests are designed and implemented where appropriate. Afterwards the thesis can be handed in.\\\"

I think this does not cover all the cases and we should decide on:

What is the usual procedure for a completed thesis? Which data we want/need to store and how?

1) Data storage: For large amounts of data (several TB) we need a safe and easy possibility to store and also a standardized way to document it.

2) program: Should we only require a form which lists all DUNE/DuMuX revision numbers? Do we want to store the code itself on a DVD? Another possibility would be to store a fully running version on a virtual machine. This is maybe too much work for Ba/Ma theses.