Accounts and training

• U-M uniqname and email. Used for U-M systems and the lab's Google Drive.
• Human-subjects training. U-M requires human-subjects research protections training, completed through PEERRS. A recent CITI human-subjects course is accepted as equivalent. Complete this before working with any human-subjects data.
• IRB. Most projects use public or secondary data, but check with Nari before accessing anything restricted. The lab's board is U-M IRB-HSBS.
• GitHub. A free GitHub account for code and shared materials.
• Reference manager. The lab recommends Paperpile; see this guide to using Paperpile. Zotero is a free alternative.

Software and tools

You do not need all of these on day one. Set them up as a project calls for them.

• Python (Anaconda). The lab's main analysis language. Install the Anaconda distribution, which bundles Python and common packages.
• Google Colab. Run notebooks in the browser with no local setup at colab.research.google.com. New to it? See this beginner's guide to Google Colab.
• Stata. For econometric and design-based analysis, many estimators are still available only in Stata, which also offers some of the most precise estimation options.
• Mplus. If you are interested in structural equation modeling and latent variable work, Mplus offers the widest range of estimation options.
• Git and GitHub. Version control for code and for this site. GitHub quickstart.

How the lab works

Read these two once, early. They explain how work and credit operate so there are no surprises later.

• The contribution ladder: how tasks range from foundational support to lead intellectual work, and what earns acknowledgment versus authorship.
• The full authorship and contribution policy.
• If you want to lead your own study, the independent projects guide.

You do not need prior research experience to start. Early tasks are usually foundational, such as literature searching, data cleaning, or annotation, and you can take on more over time.

Meetings and communication

The lab meets every other Friday at 1pm. Come with a short update on what you worked on and any blockers. For day-to-day questions, email Nari or message her on Google Chat. If something needs a longer conversation, book a 20 or 30 minute slot at calendly.com/nari-yoo. You will get more out of meetings if you bring specific questions.

Presenting your work

Conference talks and posters are a big part of lab life. See the conferences page for where the lab presents, and tell Nari before you submit an abstract. If it is your first time presenting, these guides help:

• Tips for PhD students: writing, publication, and presentation (has a presentation section).
• Delivering a Compelling Conference Presentation (University of Chicago handout).
• A beginner's guide to giving a conference presentation (The Biochemist).
• 22 Tips for Conference and Seminar Presentations (Marc Bellemare).

Using this site

• The site is behind a shared passcode, saved on your browser after the first entry.
• Research programs: see what the lab is working on and sign up for an open task; email Nari to get started, and we share progress at lab meeting.
• Publications, journals, and conferences: what the lab works on and where it publishes.

Your first week

1. Read this page and the authorship policy.
2. Set up the accounts above and start human-subjects training.
3. Install Python (Anaconda) or open a Google Colab notebook.
4. Browse the current projects and mark interest in one.
5. Bring your questions to the next meeting.

Questions

When in doubt, ask. Email Nari at nariyoo@umich.edu or raise it at a meeting. Asking early is always better than guessing, and no question is too small.