THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below.
User who did this - Nicolas Schwenck (Nicolas) Attached to Project - DuMuX Summary - Ba/Ma/PhD data storage Task Type - Feature Request Category - Discussion Status - New Assigned To - Operating System - Unspecified Severity - Medium Priority - Normal Reported Version - SVN Due in Version - Undecided Due Date - Undecided Details - 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. More information can be found at the following URL: http://www.dumux.uni-stuttgart.de/flyspray/index.php?do=details&task_id=197 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______________________________________________ Dumux mailing list [email protected] https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
