workflow_notes

Technical Notes

General Notes

Here are some notes on available compute resources for the project:

• We have access to the BCGSC's ORCA service, which has been set up with a selection of bioinformatics software
• You can see the current list of installed software and versions at versions.tsv
• The server that our team will be using is at hackseq1.bcgsc.ca. Please contact @rdocking for login credential information
• Note: team members are welcome to use their own computers for the project - the initial datasets will be available through ORCA though, and it's available for general computing

Data Resources

These are the main project directories available on ORCA:

• Home directories: /home/userhome/$USERNAME
• Project directory: /home/projects/hackseq17_3

In general, here's where things should go:

• Source code, scripts, etc should go in the main project git repository
• Commentary and discussion should take place in GitHub issues and the Slack channel
• Documentation can be added to this wiki
• Larger data files (e.g. BAM files, VCF files, etc) should be stored in a well-named directory under /home/projects/hackseq17_3

Workflow Suggestions

This is all up for discussion, but my (@rdocking's) suggestion is:

• We will meet as a group (in person and via Slack) to define small, actionable issues, which will be added on GitHub.
• Team members may work on these issues independently or together, as you like
• Most work for a given issue should be carried out in a seperate branch. When work on the issue is complete, submit a pull request and ask for review before merging back to master.

Note that this is fairly aspirational - it may be the case that we need to work more directly from the master branch. We'll update as we see how things go.