Lab space: everybody (including undergraduate students) have a right to desk space; let SP know if you need it
Work targets and weekly meetings
We set OURSELVES weekly (recommended) targets embedded in long-term goals; pass your long term goals by SP initially
Everybody meets weekly with SP (30-60 min slots, typically on Thursday/Friday). Please come with specific points, and so will SP. Email SP if meeting is not needed in any particular week, giving a reason
Give a summary of where you are WRT those targets in the weekly 1:1 meeting. If you are consistently failing to achieve targets, you need to recalibrate your expectations (and perhaps revisit your work plan/schedule); come to SP!
Consider keeping a running record of targets and tasks in a document
When SP is not around, postdocs take over (meet with them)
In the Hamilton Boardroom every Thursday 10:30–12:00, unless stated otherwise.
One or two people (including SP) present every week on either own research or a relevant/interesting paper. We will go in first-name alphabetical order (who's next?!), unless somebody wants to go earlier to get feedback on something. Use the lab slack to send around the paper/writeup at least 3 days before (so, by the Monday of that week)
Pawarlab web app
This is a web2py web app source code is here . You have read/write access to it – email SP if you don't have access.
You may edit web page content (within reason!), but most importantly, you are responsible for keeping your profile updated through the lab personnel database
We don't have a lab blog (as of now), but if you feel the urge for a lab blog, we can consider adding it on (let me know if you want to have a go at setting it up as part of the pawarlab web app!)
Lab servers, computing
This is a *nix (Linux or mac; no windows) only lab (you may ask SP WHY!) – of course, you are free to use windows for your own, non-lab purposes (e.g., SP uses a virtual machine within his Ubuntu with Windows XP on it to deal with the incessant rain of word documents and excel sheets! )
Lab server (currently called Harvey and William) documentation is available within this lab web app – everybody edits it when necessary
We have two 3 TB backup drives (We can get more if needed). rsync recommended, but format and partition as necessary with consideration of others (e.g., for mac backups)
Please keep documentation of all software/code/workflows! –either in lab repository or your project repository
Lab projects and papers
Each project/paper has a git repository (on bitbucket or git); every other lab member has a right to at least read access to every project.
A project list document on the lab repository contains the address of each repository. Each person is expected to put in their project repo address and a brief description into this document
Lab Data and Databases
Don't use git for backing up data, especially when files get into the 100's+ mb size range. zenodo is a good option, and can be cross-linked to/from git repositories
Get to know the BioTraits database: all of you will be using it to some degree