Schwilk Lab Resources
Repository for lab resources for lab and field work, data management and analyses, and field methods and lab protocols. The Schwilk Lab at Texas Tech
Schwilk lab code
Code for various projects is stored in individual git repositories. A few that might be of most interest for re-use are
- chiller: Code to run a temperature profile program on the Thermo-Fisher refrigerated bath.
- serial-balance: Communicate with an analytical balance.
- skyisland-climate: Example of a fairly well documented and organized repository for a large project.
- emacs-starter: Fairly lightweight emacs starter package (.emacs.d config files) for my students so you setup will be not too different from mine.
This folder folder for information on lab business, scholarships and funding, data management, etc.
- computers-network: Instructions and description of our lab computer network
- field-work-checklist: Use this checklist when packing for the field!
- funding-opportunities: List of graduate fellowships and scholarships
- lab-business: For information on mailing packages, departmental contacts, orderings supplies
data management, code and version control
- Git and GitHub: Our lab guide to using git and GitHub for collaboration.
- data-management: Our current lab best practices for managing lab data, setting up a project, organizing code and keeping the whole thing in version control.
Experimental methods and protocols. See individual files
We'd like to add a key to plants of Lubbock County and that will be an ongoing project aided by collections students make in BIOL-3306.
Lab safety plan and safety protocols
- schwilk-lab-safety-plan: Our EHS required safety plan. Individual safety protocols covered separately
- chainsaw-safety-protocol: Chainsaw safety.
- bleach-safety-protocol: Our most dangerous lab chemical.
Instructions for editing these protocols
These files are all stored in markdown format (https://daringfireball.net/projects/markdown/ , see also https://help.github.com/articles/github-flavored-markdown)
If these are methods on which you are working, feel free to edit and commit changes or create an issue first to give folks a heads up on the proposed changes.
Although it is ok to commit to master, a good workflow on a shared repository is:
- Make a working branch for yourself. You can even push this branch to the repository, in that case, make sure to give it a descriptive name involving the planned work or perhaps your name.
- Do you work in this branch and commit often.
- Issue a pull request so others can review your work before it is merged into /master.
This may be overkill for the protocols repository, but may make sense for others.
The plan is to make this repository public. Because it is very difficult to actually delete anything from a git repository, it is important to never commit any private information we don't want shared. I don't think there is much chance of that, but I just wanted to warn everyone.