You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 1 |[Dashboard for tracking MD simulation progress with the new streaming interface](#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface)| easy/medium | 175/350 hours | Create a web-based dashboard for real-time monitoring and analysis of MD simulations | Python (frontend UI, multiprocessing), Networking (TCP/IP) |[@HeydenLab](https://github.com/HeydenLab)[@amrutesht](https://github.com/amrutesht)[@orbeckst](https://github.com/orbeckst)|
50
-
| 2 |[Better interfacing of Blender and MDAnalysis](#project-2-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) |[@bradyajohnston](https://github.com/bradyajohnston)[@nilay-v3rma](https://github.com/nilay-v3rma)|
51
-
| 3 |[Benchmarking and performance optimization](#project-3-benchmarking-and-performance-optimization)| easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython |[@orbeckst](https://github.com/orbeckst)[@yuxuanzhuang](https://github.com/yuxuanzhuang)[@talagayev](https://github.com/talagayev)|
52
-
| 4 |[Lazy trajectory loading and indexing](#project-4-lazy-trajectory-loading-and-indexing)| medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization |[@yuxuanzhuang](https://github.com/yuxuanzhuang)[@orbeckst](https://github.com/orbeckst)[@talagayev](https://github.com/talagayev)|
53
-
| 5 |[Dashboard for tracking WESTPA simulation progress](#project-5-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](https://github.com/jeremyleung521)[@ltchong](https://github.com/ltchong)[@nilay-v3rma](https://github.com/nilay-v3rma)|
54
-
| 6 |[Interface for post-analysis analysis ("crawling") of WESTPA simulations](#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation)| easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) |[@jeremyleung521](https://github.com/jeremyleung521)[@ltchong](https://github.com/ltchong)|
49
+
| 1 |[Dashboard for tracking MD simulation progress with the new streaming interface](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface)| easy/medium | 175/350 hours | Create a web-based dashboard for real-time monitoring and analysis of MD simulations | Python (frontend UI, multiprocessing), Networking (TCP/IP) |[@HeydenLab](https://github.com/HeydenLab)[@amrutesht](https://github.com/amrutesht)[@orbeckst](https://github.com/orbeckst)|
50
+
| 2 |[Better interfacing of Blender and MDAnalysis](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-2-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) |[@bradyajohnston](https://github.com/bradyajohnston)[@nilay-v3rma](https://github.com/nilay-v3rma)|
51
+
| 3 |[Benchmarking and performance optimization](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-3-benchmarking-and-performance-optimization)| easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython |[@orbeckst](https://github.com/orbeckst)[@yuxuanzhuang](https://github.com/yuxuanzhuang)[@talagayev](https://github.com/talagayev)|
52
+
| 4 |[Lazy trajectory loading and indexing](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-4-lazy-trajectory-loading-and-indexing)| medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization |[@yuxuanzhuang](https://github.com/yuxuanzhuang)[@orbeckst](https://github.com/orbeckst)[@talagayev](https://github.com/talagayev)|
53
+
| 5 |[Dashboard for tracking WESTPA simulation progress](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-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](https://github.com/jeremyleung521)[@ltchong](https://github.com/ltchong)[@nilay-v3rma](https://github.com/nilay-v3rma)|
54
+
| 6 |[Interface for post-analysis analysis ("crawling") of WESTPA simulations](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation)| easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) |[@jeremyleung521](https://github.com/jeremyleung521)[@ltchong](https://github.com/ltchong)|
55
55
56
56
## Information for prospective GSoC Contributors
57
57
@@ -80,7 +80,7 @@ As a start to get familiar with MDAnalysis and open source development you
80
80
should follow these steps:
81
81
1.[Watch the MDAnalysis Trailer](#watch-the-mdanalysis-trailer)
82
82
2.[Complete the Quick Start Guide](#complete-the-quick-start-guide)
83
-
3.*If applicable to the [project idea](#project-ideas) you are interested in*, [learn more about WESTPA and/or Molecular Nodes(#learn-more-about-westpa-and-molecular-nodes).
83
+
3.*If applicable to the [project idea](#project-ideas) you are interested in*, [learn more about WESTPA and/or Molecular Nodes](#learn-more-about-westpa-and-molecular-nodes).
84
84
85
85
#### Watch the MDAnalysis Trailer
86
86
@@ -105,19 +105,19 @@ As some of the [project ideas][ideas] represent collaboration between MDAnalysis
105
105
106
106
### Interactions and engagement with MDAnalysis
107
107
108
-
GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant [partner software project]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#collaborations). Submitting a pull request is a great way to know you as a good candidate. As is relevant to the [[GSoC project idea|GSoC 2026 Project Ideas]] you are interested in, you should submit your PR in one of the following repositories:
108
+
GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant [partner software project]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#collaborations). 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.
113
+
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][ideas] include related issues that you might want to explore.
114
114
115
115
To start developing for MDAnalysis have a look at our guide on
116
116
[contributing to MDAnalysis][dev-guide] and write to us on the [GSoC with MDAnalysis discussion forum][discussion forum] if you have more questions about setting up a development environment or how to contribute.
117
117
118
118
### Submit a pre-proposal
119
119
120
-
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.
120
+
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.
121
121
122
122
**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [participate in a video interview](#participate-in-a-video-interview-by-invitation) (see below). 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.
123
123
@@ -137,7 +137,15 @@ Submit your pre-proposal via [this submission form][submission form] **as soon a
137
137
138
138
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.
139
139
140
-
### Final remarks
140
+
### Submit full proposal (*by invitation*)
141
+
142
+
If you pass the interview stage, you will be invited to submit your full GSoC proposal through the GSoC site (starting March 16, 2026). We will only review invited proposals.
143
+
144
+
Please read the additional information on our [expectations for a full proposal](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-proposal).
145
+
146
+
147
+
148
+
## Final remarks
141
149
142
150
**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][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.
0 commit comments