Get set up with the Sokol-Hessner Lab!
The goal of this page is to help new members of the Sokol-Hessner Lab (SHLab) get set up quickly and easily.
Email Peter with…
He will then add you to…
Finally, you need to get your stuff set up! Read on for more info about the above items and the rest of the setup.
The lab uses two main ways to communicate, plus a few others.
There are two Slack workspaces1 to join. Peter will add you to both of them.
R, python, MATLAB, and more.Slack works best when everyone’s on it, and people are relatively responsive. To this end…
We have two lab email lists: shlab-general@du.edu and shlab-core@du.edu. To be added to these lists, please send your name@du.edu email to Peter.
These lists are used for forwarding email announcements, and occasionally for lab events. shlab-general is meant for anyone & everyone within the department of psychology who is interested in things that the S-H Lab may be discussing or doing. shlab-core is meant only for ‘core’ members of the lab (graduate students, undergraduate RAs, etc).
We have weekly lab meetings during the academic quarter2. All active lab members are expected to come to lab meetings and occasionally present/lead lab meeting. Lab meetings are typically scheduled immediately prior to each quarter (taking into account members’ schedules). The goal is that lab meetings are helpful! Think about things you’d like feedback on, deadlines that’d be useful to you (to help you accomplish something on time, whether that be in your research, classes, or something else), and can be formal or informal presentations, guided discussions, or ‘journal clubs’ in which we present and discuss recent exciting research on emotion and decision-making.
Lab members are also generally on Bluesky and X. You are encouraged to join Bluesky and follow other lab members to facilitate the sharing of interesting or relevant info about science, research, job opportunities, resources, or anything else. Twitter is your call (the place is not always the healthiest). Peter’s Bluesky is @p1sh and the lab’s is @shlab. Peter’s Twitter is @p1sh, and the lab’s is @ItsTheSHLab. Joining Bluesky/X isn’t required, just recommended.
The lab uses GitHub for all project- and lab-related scripts, functions, etc. We use it to facilitate collaboration, documentation, backup, and storage. We believe this is a tool that every psychological scientist can benefit from learning to use, and require all lab members who are working on or producing code to use GitHub. The lab’s page on GitHub is here.
If you don’t know how to use GitHub, we recommend beginning at Start Your Lab (created by lab alumnus Ari Dyckovsky!), specifically the Docs page. Read and complete the steps listed in the Setup and Tutorial pages. You may also find the information on the Text Editors and Glossary pages helpful.
Along the way, you’ll need to…
If you have questions about how to use GitHub, ask! We were all new users not so long ago, and would love to help you get set up.
Once you’re all set up, look through some of the repositories3 on the lab’s GitHub page to see how we use GitHub (though if you have ideas for how to do so better, please share! We’re all looking to improve).
While GitHub is for scripts, functions, documentation, etc (and communication around those), the lab’s data should not be put on GitHub. Instead please use the University of Denver’s shared secure drive space for all data. There are two drives - the “S” drive and the “R” drive. Please email Peter with your name@du.edu address to be added to those drives. Peter will send you the file sharing addresses for those drives and help you connect to them.
These drives also have some non-GitHub based resources (PDFs of helpful textbooks, etc.).
In order to access the drives from off-campus, you must have the latest & greatest version of the DU VPN installed. See here for more.
The lab uses Google Calendars for all lab-wide events (e.g., lab meetings, important dates) and to coordinate use of the lab’s experiment rooms. We also occasionally shares files (including docs or spreadsheets) using Google. Share your Google account username (i.e. accountname@gmail.com) with Peter so he can give you access to the relevant files.
The lab website contains brief profiles of all lab members. Please send the following to Peter:
Peter will then put your profile on the website. If anything changes about your profile info, ask Peter to update the relevant portion of your profile - it’s your responsibility to keep it up to date!
We use programming tools for a lot of our work. Install at least the following, in addition to Slack and GitHub Desktop:
We used to use the following tools, but almost never do at this point:
You may want to consider other tools too, the Adobe Creative Suite (DU site license; e.g., Illustrator, Photoshop; see here), Office 365 (DU site license; see here), Zotero (free & paid versions; used for PDF management, annotation, and citation management in Word and/or Google Docs; see here) and more.
The lab is located in Room 155 of Frontier Hall (2155 S. Race St.), on the University of Denver campus. Experiment rooms are immediately adjacent to lab.
To familiarize yourself with the kind of research we do and how we do it, you can read published, in press, and pre-print papers from the lab on the website. Follow your interests and ask the lab members you’re working with (Peter, a graduate student, etc) which they recommend for you.
Many of our datasets are also available on the Open Science Framework (OSF; Peter’s OSF profile).
Mentorship is critical to a scientist’s success! We’re big believers in professional development and mentorship (e.g., see PIPS, ASFP), and value opportunities to practice mentorship and get better at it.
The lab’s philosophy is that mentorship is best thought of as an ongoing conversation. We try to structure portions of that conversation to ensure that lab members experience a consistent, thorough, supportive environment. That said, a good mentoring relationship is a relationship - it’s best when both parties are working at it. That means we encourage lab members to take responsibility over their mentoring relationships!
With this perspective in mind, we treat ‘mentor contracts’ as documents that facilitate conversations about expectations and goals. Here are two example contracts: for PhD students, for undergraduate RAs. These are living documents that require updates and are open to revision or addition. If you want to change the text or add text for your mentor contract, have that conversation with your mentor! We encourage lab members to consider using mentor contracts in all significant mentorship relationships (not just with Peter).
All lab members should also do the following:
Last but certainly not least, when working with people (including data from people) in a scientific context, you are required to complete the Institutional Review Board (IRB) training. Thus before conducting studies or even analyzing data in the lab, you must be IRB-certified. The DU IRB uses the CITI Program to administer, certify, and track researchers’ training. Here’s how to do it:
Social Behavioral Educational Research Investigators - Basic Course.RCR for Social, Behavioral, Educational, and Humanities (RCR is short for Responsible Conduct of Research).Research Conflict of Interest.Completing your CITI certification shouldn’t take more than two (2) hours, and once completed, you won’t have to revisit it for a few years - just get it done!
If you have questions during the process, don’t hesitate to ask! After you’ve completed everything, Peter will add you to the lab’s IRB protocol, thereby certifying you to interact with human participants and their data.
We hope this was helpful. Note that this website is hosted via GitHub, making it easy for existing lab members to edit and improve upon this document! Please offer suggestions and edits to improve this page via GitHub! If you’re new, don’t worry about that yet - just follow the instructions above to get started in the lab.
Welcome! We’re excited you’re here, and look forward to doing science with you!
A workspace is a collection of people and topics in Slack. Typically, a workspace is for an organization (like a lab). Workspaces contain multiple channels. ↩
The University of Denver is on an quarter system. Each quarter is 10 weeks. ↩
Repositories are for all the files related to one project. See the Start Your Lab glossary for more. ↩