Google Summer of Code 2025
28 Feb 2025
MDAnalysis has been accepted as an organization for Google Summer of Code (GSoC) 2025! 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 2025 with MDAnalysis.
The application window deadline is April 8, 2025 - 18:00 UTC. As part of the application process you must familiarize yourself with Google Summer of Code 2025, 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).
Potential GSoC Contributors are expected to familiarize themselves with application requirements and mentoring organizations as soon as possible. If you are interested in working with us, please read on to learn about MDAnalysis project ideas and MDAnalysis-specific requirements for putting together your application.
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.
Our experience shows that having the listed skills increases the chances that a project will be completed successfully, so we use them as part of our decision criteria in choosing GSoC contributors.
This year, MDAnalysis is joining forces with three other open source projects to offer even more far-reaching collaborative projects: WESTPA, Molecular Nodes, and ProLIF (an MDAKit).
| project | name | difficulty | project size | description | skills | mentors |
|---|---|---|---|---|---|---|
| 1 | Integrating MDAnalysis streaming analysis within WESTPA propagators | medium | 175 hours | Integrate MDAnalysis with WESTPA to analyze streamed trajectory data | Python (multiprocessing), Networking (TCP/IP), MD Engines | @jeremyleung521, @ltchong, @fiona-naughton, @orbeckst |
| 2 | Dashboard for tracking WESTPA simulation progress | easy | 90 hours | Create a graphical user interface to report MD trajectory progress | Python (frontend UI, multiprocessing), Networking (TCP/IP) | @jeremyleung521, @ltchong, @fiona-naughton, @talagayev |
| 3 | Lazy trajectory analysis with Dask and a Lazy Timeseries API | medium | 175 hours | Build out a lazy reader and timestep interface | Dask or lazy computation paradigm, Object-oriented programming, Writing analysis code classes/scripts, Experience with a numpy-like-interface | @ljwoods2, @orbeckst, @yuxuanzhuang |
| 4 | Better interfacing of Blender and MDAnalysis | medium | 350 hours | Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories | Python, MDAnalysis, Blender (and programming via its Python API) | @yuxuanzhuang, @bradyajohnston |
| 5 | HBond interactions from implicit hydrogens | medium | 175/350 hours | Make interaction fingerprints analysis with ProLIF (an MDAKit) more accessible and faster to run | Python, RDKit, SMARTS, compchem | @cbouy, @talagayev |
| 6 | Continuous (i.e., non-binary) interaction fingerprints (IFPs) | hard | 350 hours | Define thresholds for interactions and implement continuous encoding for interactions | Python, RDKit, compchem | @cbouy, @talagayev |
| 7 | Improving ProLIF’s 2D interaction visualizations | medium | 90/175 hours | Improve ProLIF’s “LigNetwork” plot and add 2D visualizations to summarize information in IFPs | Python, JavaScript | @cbouy, @talagayev |
| 8 | Benchmarking and performance optimization | easy/medium | 175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython | @orbeckst, @ljwoods2 |
| 9 | Integrating OpenFolds’ structural prediction confidence metrics into the topology system | easy/medium | 90 hours | Expose the predicted local distance difference test metric (pLDDT) via the MDAnalysis topology system | OpenFold or structural prediction tools more generally, Python, Solving parsing problems | @ljwoods2, @orbeckst |
Information for prospective GSoC Contributors
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.
In short:
- Agree to be bound by our Code of Conduct (and WESTPA’s Code of Conduct if you are applying for a WESTPA collaboration project [i.e., Project 1, Project 2]);
- Familiarize yourself with MDAnalysis and relevant partner projects;
- Submit a short pre-proposal —
- If you have been invited to proceed with your application (based on your pre-proposal) have a pull request merged in MDAnalysis or a partner organization.
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:
- Watch the MDAnalysis Trailer
- Complete the Quick Start Guide
- If applicable to the project idea you are interested in, learn more about WESTPA, Molecular Nodes, and/or ProLIF.
Watch the MDAnalysis Trailer
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, Molecular Nodes and ProLIF
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, Molecular Nodes and/or ProLIF.
Submit a pre-proposal
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 work on an issue to get involved in the code development 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 contribute a pull request for evaluation (see below). If you are invited to contribute a pull request 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 this submission form as soon as possible, but no later than March 21, 2025. You should prepare the following information for your pre-proposal:
- Email address
- GitHub handle
- Real name (optional)
- 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.
Have a pull request merged (by invitation)
Based on your pre-proposal we may invite you to contribute a pull request.
GSoC contributors with MDAnalysis will need to demonstrate that they have been seriously engaged with the MDAnalysis project and/or the partner software projects (WESTPA, Molecular Nodes, ProLIF) by having a pull request (PR) merged prior to submitting their full GSoC application on the GSoC website. Submit the PR in one of the repositories under the MDAnalysis org or, for projects related to Molecular Nodes (i.e., Project 4) or ProLIF (i.e., Project 5, Project 6, Project 7), in the relevant repositories (MolecularNodes: BradyAJohnston/MolecularNodes, ProLIF: chemosim-lab/ProLIF).
You must have at least one commit merged in one of the organizations to be eligible. Note that the earlier you submit your pre-proposal (which are reviewed on a rolling basis), the more time you may have to work on having code merged!
We have a list of easy bugs and suggested GSOC Starter issues to work on in our issue tracker on GitHub. We only accept one GSOC Starter issue per applicant so that all contributors invited to attempt pull requests get a chance. If you want to dive deeper, we encourage you to tackle some of the other issues in our issue tracker. We also appreciate contributions which add more tests or update/improve our documentation. Note that some of the project ideas include related issues that you might want to explore.
To start developing for MDAnalysis have a look at our guide on contributing to MDAnalysis and write to us on the GSoC with MDAnalysis discussion forum if you have more questions about setting up a development environment or how to contribute.
Final remarks
Submit your pre-proposal before March 21, 2025, 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 attempt an issue on GitHub and ultimately submit a full application; we strive to inform you of a decision within a week of your submission. The GSoC contributor application period opens on March 24, 2025.
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.
We look forward to working with you in GSoC 2025!
— MDAnalysis GSoC mentors and organization administrators (GitHub @MDAnalysis/gsoc-mentors, Discord @gsoc-mentor)