-
Notifications
You must be signed in to change notification settings - Fork 0
Harvard Resources
Where to get help with your code or analysis depends on the type of problem you're having. In general there are three different groups at Harvard that can help you. They are:
- Research Computing
- Main website
- Documentation website
- Github repo with useful code
- Sign up for training seminars
- Best way to contact is their weekly office hours or filling out a support ticket
- FAS Informatics Group
- Main website
- Slack
- Sign up for hands-on workshops when available
- Best way to contact is through the slack or email one of the staff
- Office hours are active (Wed 1:30 - 4:00 pm) when workshops run, check slack or email updates
- Other Balskus lab members
Research Computing is helpful if you have trouble with hardware/software on the cluster. Example questions:
I'm having trouble logging into to Cannon cluster
I don't understand how parallel computing works or how to give my jobs more resources
I need guidance on where to put my files
I need help adapting my code that runs on my local machine to run on the cluster
Informatics Group is helpful if you want to get advice on best practices for bioinformatics workflows or pipelines. Example questions:
I've gotten my data but I don't know the best software I should use to do X
How can I set up a reproducible workflow in snakemake or nextflow?
I'm not sure this software is doing what I think it's doing. Am I using it correctly?
I'm running into an issue with a bioinformatics software that I need help debugging
Other Balskus lab members are helpful if you have questions about lab-maintained code, procedures, etc. Example questions:
Can you explain to me how lab_script_A works?
How should I put my code on github?
The best way to get help from any of the above sources is to describe your problem as best as you can. The more work you put into describing your problem, the easier it is for others to help you. For example, if you are experiencing an issue with some script or software you are trying to run, here are some ways you can document what's going on:
- Error message
- What you expected to happen
- Command used
- Environment/context
- Minimal example
The more removed a person is from your workflow in terms of subject matter expertise or context, the more information you should provide.