Our project teams meet weekly to collaborate on cutting-edge computational neuroscience research. Work alongside fellow students, learn new skills, and contribute to exciting projects!
Our project meetings have already started! Sign up ASAP!
This team is working on replicating this previously published computational neuroscience paper (https://www.eneuro.org/content/eneuro/6/2/ENEURO.0423-18.2019.full.pdf), which was coded in NEURON with Python. Our goal is to get published in ReScience! This would involve reproducing the results in a significantly different manner (for example with the Brian2 package instead, or if you'd really want to, Julia or Octave). Hosted with generous mentorship from Dr. Rodrigo Pena, Dr. Juan Lopez, and PhD student Ty Roachford from the Stiles Nicholson Brain Institute.
If you're interested in joining a project team, but missed the stipend application deadline, don't worry! You can still participate as a member on our project team. If you're passionate about computational neuroscience research and want to gain real research experience while being mentored by experienced members and faculty, apply now at the button/link above!
Ready to jump into real-world neuroscience and computing? We're looking for enthusiastic and curious undergraduate students to join our team!
If you don't meet all of the required qualifications, but you're eager to learn and contribute, we strongly encourage you to apply anyway! We value enthusiasm and potential.
Compensation: $16-$21/hr (Paid work experience!)
Commitment: Just 2-3 hrs/week (Flexible to fit your class schedule!)
What you'll do: Be the essential support system for the team! You'll help Project Leads and Mentors, troubleshoot tech issues, and assist with hands-on Collaboration Sessions (in-person or Zoom) and prepare engaging workshop materials and assessments. This is a great way to see how a research project really runs!
Skills you'll sharpen: Time management, professionalism, great communication, and a solid foundation in literature review. You'll also learn about Open Science and research reproducibility, which are essential skills for any future scientist.
Helpful, but not required: Familiarity with Microsoft/Google Forms, scientific writing, Python, Conda, VS Code, or tools like GitHub Copilot/ChatGPT. (We can help you learn these!)
Compensation: $17.5-$22/hr
Commitment: 2-4.5 hrs/week (Flexible, but impactful!)
What you'll do: Dive deep into Open Science literature. You'll be leading your own 2 or 8 one-hour Workshops over the semester/year (don't worry, you'll be supervised!). You'll also coordinate with the Technical Rigor Intern on fun pre/post-workshop assessments and help review documentation for reproducibility. You'll report directly to the Project Lead and Mentors who can expand your network!
Skills you'll sharpen: Stellar communication, time management, professionalism, and the ability to work independently. You need to be comfortable with presentation design (PowerPoint/Google Slides), document design (Word/Google Docs), scheduling, and have a good grasp of Python and VS Code, plus scientific writing.
Helpful, but not required: Any experience with Git/GitHub, or a willingness to jump in and self-learn about research documentation.
Compensation: $17.5-$23.5/hr
Commitment: 2-4.5 hrs/week
What you'll do: This role is for the student excited about the technical side of research! You'll lead your own 2 or 5 cutting-edge technical Workshops (think: containerization, FAIR data, replication tools) over the semester/year. You will also review GitHub pull requests and be the go-to person for technical inquiries and supporting code pushes. You'll report to the Project Lead and Mentors.
Skills you'll sharpen: You need a strong foundation in Git/GitHub, Python, VS Code, and Conda environment management (or be ready for rapid self-learning!). Proficiency in the command line (CLI), time management, a proactive approach, and great communication are key. Experience with presentation design, scientific writing, and code documentation (plus GitHub Copilot) is essential.
Helpful, but not required: Familiarity with .gitignore files, or a drive to learn!