Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Have main function to create project, separate functions for the type #72
I wonder if one should not have one "create scientific project" template, with different folders for the different elements a scientific project will have at the end:
This would need some brainstrom about what is indeed needed in such a folder and how to keep things flexible.
Hm, I originally had done this way of structuring projects, but I came across several problems...
I think one of the main reasons why I prefer the "single project, single folder/repo" model is that it changes the emphasis and mindset of the code/data/figures/etc as a "means to create the paper, poster, etc" to "the code/data/etc is just as valuable as the paper/etc and is an entity/product on its own and should be treated as such".
I am not sure what you mean by "project", I think there is some misunderstanding between Rprojects, scientific projects and scientific output (poster/presentation/paper) (?).
If you like your doi to refer only to the code for one output and get a different one for the data, one would need a new Rproject folder for that output. I think I got your point here. I would then rename the functions and discussion here, using "create new report for your project" as description of what the functions are doing. One could still have a create new scientific project function on top?
Did I understood you correctly this time?