Workshop overview

As mentioned on the Welcome page, this workshop will be focused on reproducible neuroimaging and cover various important aspects from an introduction to the problem and motivation to adapt neuroimaging reesarch workflows accordingly to the utilization of basic and advanced tools/resources. In general, the idea is to do a split between first, the basics of reproducible neuroimaging and second, more advanced and specialized approaches. Regarding the first, we will try to provide folks with a brief overview of central aspects, as well as important issues and concerning the second, evaluate and introduce a versatile set of cutting-edge approaches that build upon the former. Within both, we will go through and practice the use of respective software, tools and resources. We will further explain both aspects, as well as the setup, etc. below. For a precise outline of this workshop, please consult the respective page.

The framework and setup

All workshop materials will be provided within the Jupyter Book format you’re currently looking at, free for everyone to check and try out, as well as utilize further. The workshop itself will use a mixture of slides, code and other media within presentations, practical hands-on sessions and discussion rounds to enable a holistic introduction paired with firsthand experience. Depending on a given participant’s computational resources and infrastructure, we provide multiple ways to participate in the workshop as outlined in the Setup for the workshop section.

Instructors

To provide a holistic introduction into the topic of reproducible neuroimaging and its subcomponents, we assembled a stellar team of instructors entailing highly experience experts of both the ReproNim team as well as colleagues from adjacent initiatives. You can find them below and get further information via clicking on the respective names.


Guiomar Niso

Dorota Jarecka (she/her)

David Kennedy (he/him)

Jean-Baptiste Poline (he/him)

Adina Wagner (she/her)

Sebastian Urchs (he/him)

Peer Herholz (he/him)

Gimme the details

Below you will find important details regarding the course summarized in a compact form. Please consult and familiarize yourself with the information presented there prior to the course.

When and where

The course will take place on two afternoons: Tuesday, 22/03/2002 & Wednesday, 23/03/2022, from 1 - 6 PM CET respectively. Given the current situation re the pandemic and the international line-up of instructors, the entire workshop will be run via Zoom and in parts Gathertown. The respective links will be provided for registered participants shortly before the workshop.

Can I use my calculator? 🖥️

For this class you will need frequent access to a computer that can run bash and python among other things. None of the analyses that we will be doing will be very intensive, so this does not need to be a modern or “fast” computer. Still, it will need to be running a standard operating system like Windows, Mac OS X, or Linux. Unfortunately, tablets running mobile operating systems (iOS, Android) probably won’t work for this purpose. If this is an issue for you, please get in touch with the instructors as soon as possible so that we can try to figure out a solution. Regarding software and installation thereof, please check the next section.

via GIPHY

How do I get all the software and do I have to apply for a loan to get it? 🖥️

Don’t worry at all. First, in order to help you get all the software required for the course, a comprehensive installation instruction was compiled. In a step-by-step manner it guides you through the installation process, covering several OS: windows, macos and linux. Second, everything will be completely free of charge as we will only use publicly available open-source software. Why? Because teaching students via proprietary software is just not fair and won’t help anyone: students have to obtain licenses or use those from the university (which usually doesn’t have enough for everyone), leading to tremendous problems regarding inequity now and in the future. Additionally, opens-source software can do everything, if not more, what proprietary software can and is furthermore usually better supported, tested and documented, creating a fantastic sense of community.

via GIPHY

Where is everything?

All course materials (lecture slides, lecture demo notebooks, etc.) will be available on the workshop website, i.e. the one you’re looking at right now. Everything will be completely open and free to use, thus constituting an open educational resource you are free to explore, enhance and share. Thus, this website and all materials will also remain up for the entire duration of the workshop and beyond, ideally to end of the internet. The usage of this resource and the materials therein will be explained at the beginning and throughout the workshop.

via GIPHY

Syllabus and Text

As noted above, this page serves as the syllabus for this workshop, with the precise outline indicated in the respective section. As usual, the syllabus is subject to change.

Code of conduct

This workshop has a Code of conduct. Please inform yourself about the specifics by carefully reading through the respective section.

via GIPHY

How to Get Your Question(s) answered and/or provide feedback 🙋🏼‍♀️ ⁉️

It’s great that we have so many ways to communicate, but it can get tricky to figure out who to contact or where your question belongs or when to expect a response. These guidelines are to help you get your question answered as quickly as possible and to ensure that we’re able to get to everyone’s questions.

That said, to ensure that we’re respecting everyone’s time, we will mainly answer pre-/post-workshop questions between normal working hours (M-F 9AM-5PM). The instructors are also going to do their best to stick to these working hours when they want to share information. However, they know that’s not when you may be doing your work. So, please feel free to post messages whenever is best for you while knowing that if you post late at night or on a weekend, you may not get a response until the next weekday. As such, do your best not to wait until the last minute to ask a question.

If you have:

  • questions about course content - these are awesome! We want everyone to see them and have their questions answered too, so either use the hypothes.is plugin, the zoom chat, e-mail or the GitHub repository.

  • a technical assignment question - come to office hours. Be as specific as you can in the question you ask. And, for those answering, help your fellow participants as much as you can without just giving the answer. Help guide them, point them in a direction and provide pseudo code.

  • been stuck on something for a while (>30min) and aren’t even really sure where to start - Computational work can be frustrating and it may not always be obvious what is going wrong or why something isn’t working. That’s OK - we’ve all been there! IF you are stuck, you can and should reach out for help, even if you aren’t exactly sure what your specific question is. To determine when to reach out, consider the 2-hour rule. This rule states that if you are stuck, work on that problem for an hour. Then, take a 30 minute break and do something else. When you come back after your break, try for another 30 minutes or so to solve your problem. If you are still completely stuck, stop and contact us (office hours). If you don’t have a specific question, include the information you have (what you’re stuck on, the code you’ve been trying that hasn’t been happening, and/or the error messages you’ve been getting).

  • questions about workshop logistics - first, check the overview & syllabus. If you can’t find the answer there, first ask a fellow participant classmate or instructor. If still unsure, post on the zoom chat.

  • something super cool to share related to the workshop or want to talk about a topic in further depth - feel free to post on the zoom chat, contact the instructors or come to office hours.

  • some feedback about the course you want to share anonymously - If you’ve been offended by an example in the workshop, really liked or disliked a lesson, or wish there were something covered in the workshop that wasn’t but would rather not share this publicly, etc., please fill out the anonymous Google Form*

*This form can be taken down at any time if it’s not being used for its intended purpose; however, you all will be notified should that happen.

Acknowledgements

Several parts of this section are directly taken or adapted from Alexander Huth’s Neuro Data Analysis in Python syllabus licensed under a BSD-3-Clause License and Shannon Ellis’ COGS 18: Introduction to Python.