Rules and Expectations and Goals
There are any number of reasons to establish lab rules incuding safety, philosophy, and expectations. This is how I want my research group to operate:
- Do good science by asking questions early and often, planning ahead, and collaborating.
- Give credit where credit is due.
- Highly Qualified Personnel (HQP, such as students and post-docs) should be the first author of papers coming from their thesis work. Authorship should be discussed early and generally follows the ESA’s Code – see also the advice of Schmidt 1987, Hunt 1991, and Weltzin et al. 2006.
- Be safe and help others be safe by thinking about what types of training are needed.
- Publish in Open Access venues whenever possible, noting there can be different requirements from each funder.
- Deposit all publications and technical reports on a preprint server such as bioRxiv, EarthArXiv, ESSOAr, etc.
- All data must be organized and stored on the group’s GitHub repository with the metadata template completed.
- Make available all data and code for each publication via a service like GitHub+Zenodo, Pangaea, etc.
- Have fun.
- It is important to interact with others in the group and although our work hours can be very flexible. it is important to be around between 9:30–14:00.
- We have routine lab meetings except during the middle of field season and attendance is expceted. It is an opportunity to present ideas and plans for new research, to show and discuss new data, and to practice presentations. People spend their attention and time to help so please respect this and come prepared.
- Everyone should attend at least one conference or workshop per year if funds are available and time permits. All are expected to apply for additional funds to support attending conferences and workshops. Please send your abstract to all the coauthors at least one week in advance so no one is suprised and people can provide feedback.
- Everyone needs to complete WHMIS training. Everyone doing field work needs to complete Standard First Aid is working close to populated areas and Wildness First Aid in all other cases. Everyone using a boat needs to obtain a Pleasure Craft Operator Card. Everyone needs to complete a set of risk assessment forms and provide emergency contact information to be kept on file in the department. No one does field work alone.
Here is the list of onboarding things to do to help integrate new people into the research group.
- Get a OneCard, remind Jason to email for you to have access to CCRWS and SRC buildings
- Take for Standard First Aid or Wilderness First Aid (typically by May and recently coordinated with Dean of Science office), email Jason a copy to be kept on file
- Take Canadian Firearm Safety Course, if working in the north, email Jason a copy to be kept on file
- Take WHMIS and Compressed Gas Training, available online, email Jason a copy to be kept on file
- Obtain a Pleasure Craft Operator Card, email Jason a copy to be kept on file
We use git and GitHub to keep track and control of our data, metadata, code, and papers:
- Make a GitHub account, add an avatar so it’s easier to find you, and ask Jason to be added to the appropriate teams
- Create a repo on GitHub with a README file
- Edit the README with and do some formatting with Markdown
- Install git to make it easier to integrate GitHub with your workflow
We use R and RStudio for organising, analysing, modelling, plotting, etc. our data, sometimes we use Matlab and other softwares like Jupyter and Python as needed:
- Download and install R
- Download and install RStudio Desktop
- Open RStudio to check that it works and there are no errors
- Note that Windows users may need
Rtoolsand Mac users may need
Xcodein order to compile R packages that are not available as pre-compiled binaries
- Install the
herepackages since they will be very handy (in RStudio, Tools -> Install Packages, type the names of the packages separated by a comma)
- New students should work through this Introduction to R lesson and Starting with data lesson
- Often small files will sneak into your repos even if you don’t want them to, so vaccinate your global gitignore with usethis::git_vaccinate
- Test out creating a repo on GitHub from our template, enter appropriate metadata that makes sense for your research, commit the change, and push it to GitHub
- The Tidyverse style guide is a great resource and following its general recommedations will make your code easier for you to write and easier for other people to follow what you have done.
- Jenny Bryan’s Happy Git and GitHub for the useR is an excellent reference and learning manual and everyone should walk through many of its chapters when setting up their system
- Karl Broman’s git/github guide: a minimal tutorial is also very useful
- The Data Analysis and Visualization in R for Ecologists lessons are an excellent way to learn how to employ R and RStudio to aggregate, analyse, and visualise data