This marks our seventh consecutive year participating as an independent GSoC organization.
A big thank you goes out to Google for supporting these three exciting projects.
We’re looking forward to getting started!
This project will implement WESTPAParser and WESTPAReader inside westpa/westpa, exposing WESTPA’s HDF5 Framework simulation data as a standard MDAnalysis Universe. Post-simulation analysis currently requires custom boilerplate code via w_crawl which this project will replace with a single command, making the entire MDAnalysis toolkit accessible on WESTPA data.
Kunj is an undergraduate student at PES University, pursuing a Bachelor of Technology in Computer Science and Engineering. He has always had an interest in various fields of science and technology since his early school days. In his free time, he listens to music, plays different musical instruments and enjoys cooking as well.
This project will develop a browser-based, real-time dashboard for molecular dynamics simulations using the new IMDv3 streaming protocol, enabling live monitoring, analysis, and visualization of running simulations. The dashboard will leverage imdclient and MDAnalysis to receive and analyze data streams from running simulations.
Pardhav is an undergraduate student from India pursuing a Bachelors in Computer Science and Engineering from Vellore Institute of Technology (Vellore) and a BS in Data Science and Applications from Indian Institute of Technology (IIT) Madras.
This project intends to add web retrieval functionality to MDAnalysis by augmenting the existing fetcher module. By introducing new fetchers,
it is intended to allow MDAnalysis to download structures and trajectories from external databases such as AlphaFold and the Molecular Dynamics Data Bank by passing downloaded data to the in-built Universe class. Additionally, this project intends to introduce a new suite of functions that is capable of retrieving any molecular data from any database supporting REST API.
Joshua Raphael Uy is a Physics Ph.D student at Arizona State University. He earned a Bachelor of Science in Physics, a Bachelor of Arts in
Mathematics at Miami University in Oxford, Ohio, and a Master in Science in Physics at Arizona State University. He has a bio page and a Linkedin.
To follow this project, you can check out Josh’s blog.
MDAnalysis has been accepted as an organization for Google Summer of
Code (GSoC) 2026! If you are interested in working with us and you
are new to open source, please read the advice and links below to learn how you can apply to participate in GSoC 2026 with MDAnalysis.
The application window deadline is March 31, 2026 - 18:00 UTC.
As part of the application process you must familiarize
yourself with Google Summer of Code 2026, including eligibility requirements, timelines, and generally how the program works.
We are looking forward to all applications from any new and beginner
open source contributors or students over 18 years old; see a full list of the eligibility requirements in the GSoC FAQ. Projects
are scoped as either 90-hour (small), 175-hour (medium) or 350-hour (large) size. The
duration can be extended from the standard 8 weeks to up to 12 weeks (for small projects), or from the standard 12 weeks up to 22 weeks (for medium or large projects).
For GSoC, MDAnalysis collaborates with other projects that have direct links with MDAnalysis and where it is especially useful to draw on the combined mentoring expertise.
This year, MDAnalysis is joining forces with WESTPA and Molecular Nodes. Applicants who want to work with one of the collaborating projects should familiarize themselves with MDAnalysis and the project that they are interested in. GSoC projects with either WESTPA or Molecular Nodes will be mentored by experts from the collaborating project and MDAnalysis.
Project Ideas
If you have your own idea about a potential project we’d love to work with you
to develop this idea; please write to us on the GSoC with MDAnalysis discussion forum to discuss it there.
We also have listed several possible projects for you to work on. Our
initial list of ideas (see summaries in the table below) contains various
projects of different scope and with different skill requirements. However,
check the ideas page — we might add more ideas after the posting date of
this post.
You must meet our own requirements if you want to be a GSoC
Contributor with MDAnalysis this year (read all the docs behind these
links!) and read the points below for the application process. You must also meet the GSoC eligibility criteria. Our GSoC FAQ collects common questions from applicants.
Participate in a video interview with developers of MDAnalysis and/or one of the partner organizations. You will be invited for interview based on your pre-proposal.
Submit your full GSoC application. You will be invited to submit your application based on your video interview.
Code of Conduct
The MDAnalysis community values diversity and is committed to providing a
productive, harassment-free environment to every member. Our Code of Conduct
explains the values that we as a community uphold. Every community member (and every
GSoC Contributor) agrees to follow the Code of Conduct.
Familiarize yourself with MDAnalysis and relevant partner projects
As a start to get familiar with MDAnalysis and open source development you
should follow these steps:
The MDAnalysis Trailer on YouTube
is a one minute introduction to MDAnalysis.
There are also additional introductory videos available to give you an idea of what problems MDAnalysis is solving.
Complete the Quick Start Guide
Start by installing the MDAnalysis package. We have a Quick Start Guide explaining the basics of MDAnalysis. You should go through it at least once to understand how MDAnalysis is
used. Continue reading the User Guide to learn more.
Learn More About WESTPA and Molecular Nodes
As some of the project ideas represent collaboration between MDAnalysis and other partner software projects, you should follow the recommended steps linked here to familiarize yourself (as relevant) with WESTPA and/or Molecular Nodes.
Interactions and engagement with MDAnalysis
GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant partner software project). Submitting a pull request is a great way to know you as a good candidate. As is relevant to the GSoC project idea you are interested in, you should submit your PR in one of the following repositories:
We have a list of easy bugs and suggested GSOC Starter issues to work on in our issue tracker on GitHub. If you want to dive deeper, we encourage you to tackle some of the other issues in our issue tracker or create a new one. We also appreciate contributions which add more tests or update/improve our documentation. Note that some of the GSoC 2026 Project Ideas include related issues that you might want to explore.
We ask you to submit a short pre-proposal so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and participate in a video interview or tell you that we will not consider your application. Please note that this decision is final, and applicants should only submit one pre-proposal. A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis.
We require GSoC applicants to submit a pre-proposal that will determine who is then invited to participate in a video interview. If you are invited to participate in an interview and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include.
Submit your pre-proposal via our pre-proposal submission formby March 9, 2026. The submission form will go live a few days after this post is available from Feb 28, 2026.
❗Do not use generative AI to develop or write your pre-proposal. We need to hear your ideas and voice.
You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.
You should prepare the following information for your pre-proposal:
Email address
GitHub handle
Real name (optional)
Certify that you did not use AI tools to develop or produce the pre-proposal.
Basic information on your background (e.g., education, relevant experience with MDAnalysis and molecular dynamics or computational physics/chemistry/materials)
Project title
Project size (90h, 175h, 350h)
Problem: Describe the problem to be solved. What is the background? What is the overarching question? You can also comment on why this is an interesting or difficult problem. Clearly define the overall goal of what you want to find out.
Approach: Describe how you are going to reach your goal (i.e., answer the overarching question). Which algorithms are you going to use? Are there any libraries or other packages you want to use? Do you need to research different solutions? Be as concrete as possible; you want to convince your audience that it is feasible to solve this problem and you have an idea how to tackle it.
Objectives: Use a numbered list to state 3–5 measurable non-trivial outcomes that you need to achieve in order to reach the overall goal. These are the milestones that you have to reach; they are possibly dependent on each other. For each objective it must be clear how to decide if you fulfilled it or not. Objectives are formulated in terms of actions and deliverables.
Interactions: Describe the interactions you had with maintainers from MDAnalysis (or WESTPA/Molecular Nodes if you plan on working on a collaborative project). Be specific and link to specific instances of interactions (e.g. Pull Requests) if possible. (500 words)
Participate in a video interview (by invitation)
Applicants who are invited for a video interview will be contacted no earlier than 72 hours after they submit their pre-proposal. During the interview (15 minutes), you will discuss your pre-proposal with 1-2 developers. The video may be recorded for evaluation by other developers/mentors. During the interview, you will be required to share your (full) screen and respond live to questions. The interview may involve live programing and discussions of code sections of MDAnalysis that are relevant for your project. The interview will be conducted using Google Chats or an equivalent video conferencing software.
Submit full application (by invitation)
If you pass the interview stage, you will be invited to submit your full GSoC application through the GSoC site (starting March 16, 2026). We will only review invited applications.
❗Do not use generative AI to develop or write your application. We need to hear your ideas and voice.
You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your application in your own English words.
Final remarks
Submit your pre-proposal before March 9, 2026, but the earlier the better! We will then let you know via the email you provide in the pre-proposal submission form if you have been selected to participate in a video interview and ultimately submit a full application. The GSoC contributor application period opens on March 16, 2026.
Feel free to ask any questions on the discussion forum. We are also happy to chat on our MDAnalysis Discord server in the #gsoc channel (join with the public invitation link). Please note that MDAnalysis as an organization highly values transparency and therefore we strive to conduct all discussions in public forums so please ask questions publicly and not via direct messages or emails.
As part of our ongoing commitment to fostering an open, welcoming, and respectful community, the MDAnalysis project has updated its Code of Conduct and formally adopted the NumFOCUS Code of Conduct. This replaces our previous Code of Conduct, which had been in place since 2017, and brings our community standards into alignment with those of our fiscal sponsor, NumFOCUS.
Our decision to adopt the NumFOCUS Code of Conduct was motivated by a desire to better serve our growing and diverse community through a process that is impartial, transparent, and sustainable. By aligning with NumFOCUS’s framework, all Code of Conduct reports are reviewed by the NumFOCUS Code of Conduct Working Group, a team of trained responders who operate independently of the MDAnalysis team to ensure reports are reviewed, investigated, and advised upon with neutrality.
expected behavior, such as respectful communications and inclusion of diverse perspectives;
unacceptable behavior, including harassment and discrimination;
reporting procedures and contact points for individuals who experience or witness potential conduct violations;
enforcement procedures, namely, that the MDAnalysis Code of Conduct Committee is responsible for enforcement based on recommendations from the NumFOCUS Code of Conduct Working Group.
The Code of Conduct applies to all MDAnalysis project spaces — including GitHub and GitHub Discussions; Discord; LinkedIn; Bluesky; workshops and events; and all other forums associated with MDAnalysis.
Our Commitment
All MDAnalysis core developers have unanimously agreed to adopt the new Code of Conduct and are fully committed to upholding its principles. Our goal is to ensure that the MDAnalysis community continues to be a place where all contributors, users, maintainers, and other community members feel welcomed, valued, and safe. As it takes all of us, and not just core developers, to foster an inclusive environment, all MDAnalysis community members agree to share a common set of core values and act according to these principles in all interactions within our community.
If you have any questions or concerns regarding the Code of Conduct, we encourage you to reach out to the MDAnalysis Code of Conduct Committee. We thank you for joining us on our mission to foster a welcoming and inclusive community!
