-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update wiki #13
Comments
Yes! Lets wait until the text for CAMI is def. finalised (two weeks max) and then move it there - together with the pipeline specific comments and minus the challenge-specific parts. Should we work on it jointly again? Best, Sent from my phone Am 07.11.2016 um 15:46 schrieb Adrian Fritz <[email protected]mailto:[email protected]>: Since we have a new and shiny text about the Simpipeline for the CAMI paper it would be great to incorporate this into the wiki, i.e. removing the nested structure of the documentation and instead have one central text in which all the relevant information is found, linking to external sources only (?) — Helmholtz-Zentrum für Infektionsforschung GmbH | Inhoffenstraße 7 | 38124 Braunschweig | www.helmholtz-hzi.de Vorsitzende des Aufsichtsrates: MinDir’in Bärbel Brumme-Bothe, Bundesministerium für Bildung und Forschung |
This Issue is actual again since the addition of the new features! |
@AlphaSquad What's the current status? At first glimpse, looking good. However, if you need help with the wiki, please let me, @pbelmann, ... know and we can jump in! |
A file of files for improving documentation (#35 ) should be handy, and maybe somewhere more information for people wanting to work/code with CAMISIM? User documentation should be fine I hope |
Since we have a new and shiny text about the Simpipeline for the CAMI paper it would be great to incorporate this into the wiki, i.e. removing the nested structure of the documentation and instead have one central text in which all the relevant information is found, linking to external sources only (?)
The text was updated successfully, but these errors were encountered: