The MacManes lab strives to be an internationally recognized leader in the field of ecophysiological and evolutionary genomics. To accomplish this goal, we push ourselves to be careful in our observations, broad in our questions, and vigorous in our pursuit of research funding. We are generous in the dissemination our products. Indeed, our vision for the future of science is collaborative more so than competitive. To this end, lab members should be prepared to develop the ability to:
One key to success is to make other people say no to you (rather than you saying no to yourself). Don't not apply for some fellowship/job/position because you don't feel qualified. It's good to be realistic about your qualifications, but imposter syndrome (https://www.chronicle.com/article/Impostor-Syndrome-Is/238418) is real, and powerful.
Another important key to success is persistance. Seriously, you are going to be rejected far more frequently (jobs, papers, grants, etc) than not. Keep at it! Don't take it personally, and submit your paper somewhere else!
Positive attitude. Grad school is a ton of work, but this is all supposed to be fun and exciting. You are getting paid at this point to learn, discover, explore. That's wicked cool! Having a positive attitude, at least most of the time, is going to help you, and everyone around you. It's not always easy, and we're all human, but let's try..
We expect lab members to fully imerse themselves in the process of research and its dissemination. To accomplish this, we will conduct careful and reproducible experiments, write good code, and disseminate our results widely through approachable publications. When we submit papers, we expect that the analytical code behind those papers will be something that we can be proud of. To these ends, we will provide reviewers and the scientific community with all source code required to conduct analsyes in the paper that result from computational analyses.
About being a good lab citizen. You are expected to share freely, and without conditions, with your lab mates. This includes data, protocols, code, and other information. Unless you paid for the data yourself, it does not belong to you, it belongs to the lab. It’s my job as the PI to make sure you are properly credited via authorship, etc. I promise that you will get the credit you are due for the work you have done.
About email/slack One of the amazing things about academia is that you have a lot of freedom to set your own hours. Some of us have/had small children, and so normal business hours don't really work. I work when I can, and sometimes this is on the weekend, at night, early AM. Just because I do this, does not mean that I expect you to. If I send you an email at 0200 (see below tweet), I don't expect immediate action.
Your role in the lab is to take primary responsibility for the success of your research project and career development. As a member of the lab, you are expected to participate fully in the team, which includes supporting others in their endeavours, and mentoring more junior members. In general lab members are expected to be present from 9:00AM to 3:00PM on weekdays to facilitate discussion within the group.
Matt’s goal is to facilitate your success as well as that of your project. Within your project, Matt will serve as a sounding board for ideas, will help you plan your project, and will help to devise experiments to test your hypotheses. For your success, Matt will help you to plan your training, to devise a career plan that takes you where you want to go, to manage your portfolio of project risk, and other elements of professional development.
All members of the lab, along with visitors, are expected to agree with the following code of conduct. We will enforce this code as needed. We expect cooperation from all members to help ensuring a safe environment for everybody.
The lab is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, race, or religion (or lack thereof). Sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention will not be tolerated.
Members asked to stop any harassing behavior are expected to comply immediately.
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Matt immediately. For official concerns, please see the University of New Hampshire ombuds office.
We expect members to follow these guidelines at any lab-related event.
See the original doc related to the code of conduct.
You will also be required to conduct University wide training on maintaining professional workplace envrionments. These will be emailed to your unh email account.
Postdocs will get a faculty/staff permit that will allow them to park in the Gregg Hall lot. You'll have to go the Parking office (https://unh.edu/transportation/parking).
For grad students, you also will get a permit (same office), but this will only allow you to park in A-lot (located right next to the parking permit office, across the street from the 'Field House'). You should ask another of the grad students for those details.
NOTE: You will need your "nine number" to get your permit (this should have been given to your in your 'welcome email', if you don't have one, contact UNH IT to get it). Get your permit BEFORE or AFTER the first week of classes, or get to the parking permit office right when they open.
Information on how to get accounts on computers and in the services that the lab uses are below.
Email: UNH will assign you an email
Postdocs: Firstname.Lastname@unh.edu
Grad Students: Firstname.Lastname@unh.edu
This information and your 'nine number' (a long numeric identifier) should be in a 'welcome email; that you will recieve soon after you start. If you don't receive an email, don't fret! You can contact UNH IT (https://www.unh.edu/it/) and they'll set you up with a temporary password to get you started.
All code written for the lab should be committed to a repository with the macmanes-lab organization as the owner. This helps us to maintain continuity and provides a single location for our code. You can make your code private or public.
If you make your code public, we have certain expectations:
It will be under an open source license (specified in a LICENSE.txt file in the repository root).
In certain circumstances, we will require a specific license. Usually this will be the BSD 3-clause license. If you’re not sure on a license, check with Casey.
You will maintain a README file describing the purpose and use of the repository.
If you keep your repository private, we will have expectations:
Your repository can be private during development, but expect that one day your code will be world readable.
In the event that you publish a manuscript, we expect that lab members will simultaneously release a code repository capable of generating all of the figures in the paper for which it is appropriate (again, if not sure, ask, but if you wrote code to generate a figure at one point, it should be included).
You will maintain a README file describing the purpose and use of the repository.
We aim to write good code, and we recognize that not all projects are created equal. Using the vocabulary of The Pragmatic Programmer, some code is for production and other code represents tracer bullets. In either case, it’s helpful to use a linter (see tools) and to minimize the number of problematic sections.
I'm not going to force you, but most people find Twitter to be a good place for networking and communicating with the broader scientific community. Promoting yourself, and your work, via social media, is important in 2022.
I have a google calender that I'd encourage you to use for notifying me of extended periods of time when you will be out of the office - just send me an email and I can add you to it. If you don't use the calender, I reserve the right to ask you at least daily when you are going to be gone, and where you are when you are away.
See another member of the lab for the IP address for the printer. You should be able to print things from your laptop/desktop.
If you are going to work with animals, you need to fill out the forms, here: https://www.unh.edu/research/occupational-health-program-animal-handlers.
The Animal Resource Office (ARO) is in the basement of Rudman Hall. Dean Elder is the director.
You'll need card key access to Rudman hall (https://www.unh.edu/research/form/rudman-hall-electronic-access-card-key-request-form), and a metal key to get into the animal area itself.
You will likely need access to both XSEDE and Premise.
To set up your premise account:
email rccops@sr.unh.edu
Ask for a premise account with this information:
Full Name:
Email and phone:
Requested login id:
Research Group: MacManes lab
Expected use case / Research area: Evolutionary genomics
ID:
Here's a list of software already install on premise: http://premise.sr.unh.edu/colsa.html#installed-software-packages
Toni Westbrook (office right next to mine) is the COLSA liason for Premise. He is a great resource for all things related to the server, and also Bioinformatics and programming. Ask Toni connect you to the colsa-bigdata slack group for premise updates.
Meet Krys and ask her to submit a key request for you. In addition to the key for the building, grad students wll have keys that open the lab, the conference room, the CABOOSE, and the grad cubes. Postdocs get keys that open every door on the 4th floor. Keys take ~1-2 weeks to get in.
There are a few editors that are used within the lab listed below. In general, pick something that works for you and learn it well. We recommend an editor that supports linters and other programming-specific capabilities.
This material will find a home eventually, but will be here for now..
This document was adapted from an onboarding document developed by Casey Green (@GreenScientist).