Organizing science projects
Reproducibility of published scientific findings is key. Andrew will “audit” code, figures and data files before we submit for publication, so best to get started on the right foot.
- Every project (no matter how small) should have its own directory. Minimally, the root directory should contain a README file containing basic information on the project, as well as subdirectories for :
/src — source code
/data — input data files (directly from the source, never to be changed)
/results — resulting output files
Additional suggested directories include:
/docs — documentation
/temp — temporary files
More suggestions on how to organize bioinformatics projects can be found at:
- All code should be versioned using git and regularly checked in at Github/sulab or Bitbucket/sulab. Ask Andrew to be added to the team/organization.
- Use of IPython/Jupyter notebooks is encouraged.