GSOC 2026 Project #13 : AnalySim : Fixing beta testing and forking

GSoC
1

Mentors: Cengiz Gunay <cgunay@ggc.edu>, Anca Doloc-Mihu, <adolocm@gmail.com> (Planned break for both mentors due to CNS meeting: July 5 - July 9 with limited email contact)

Skill level: intermediate/advanced preferable

Required skills: C#, .Net, HTML/CSS/Bootstrap, Angular, TypeScript, PostgreSQL, Docker

Time commitment: Full-time (350 hours)

About: AnalySim is a data sharing and analysis platform that seeks to simplify the visualization of datasets. With Analysim, researchers can collaborate by hosting their data and publishing their analysis notebooks to the world, or browse through multiple user-generated projects. Analysim is currently being hosted on the NSF-funded ACCESS-CI project infrastructure, but it can also be deployed independently via Docker.

AnalySim aims to be a general data sharing and hosting resource for crowdsourced-analysis, but it provides additional support for a specific type of dataset: one where many parameter combinations need to be tested and measurements are recorded for each instance. These datasets are very useful in mathematical modeling of natural phenomena, such as in computational neuroscience. We provide easy sharing, analysis, visualization, and collaboration capabilities on these datasets. In this GSoC iteration, we are improving on features developed in the summer and winter of 2024.

Aims: Helping run the controlled beta testing by fixing issues and adding new features for forking datasets/projects, following/joining projects. Improving usability of CSV data browser, versioning, and querying components.

Website: Project is still in progress and a demo site is available at: https://analysim.tech and a development version is at https://dev.analysim.tech

Source code: GitHub - soft-eng-practicum/AnalySim · GitHub

Tech Keywords: Angular (Typescript), HTML/CSS/Bootstrap, .Net Core (C#), PostgreSQL, and for analysis notebooks: JavaScript (ObservableHQ, D3.js, Vega, Plotly) and Python (Jupyter)

1 Like
2

Hi @arnab1896 ,

I’m Arpit Singhal from IIT BHU, pursuing Computer Science Engineering. I’m really interested in contributing to AnalySim for GSoC 2026, especially in beta testing, issue fixing, and improving dataset/project forking workflows.

I have experience with TypeScript, Angular, React.js, Node.js, HTML/CSS, and have worked on web apps, dashboards, and collaborative platforms. I’m comfortable exploring the codebase, identifying issues, and implementing frontend improvements.

Could you please point me to any starter tasks or issues where I can begin contributing?

Looking forward to contributing!

— Arpit Singhal

3

Hi @cengique (Cengiz) and @adm (Anca)

I’m Deenu, and I’ve been exploring AnalySim over the past few weeks — set it up locally, got everything running including the JupyterLite build, and spent time tracing through the codebase to understand how the pieces fit together.

While going through the issues I noticed #114 and wanted to take a proper shot at it rather than a surface-level fix. The root problem was that the postMessage readiness signal was injected directly into a manually-copied index.html — meaning every jupyter lite build would silently wipe it out. I addressed this in PR #135 by moving the logic into a proper JupyterLite plugin using app.restored, which is the stable lifecycle API for this. Along the way I also consolidated a JupyterLiteStorageService that existed in two near-identical copies across the admin and project folders, and fixed an event listener leak in ProjectNotebookItemDisplayComponent where ngOnDestroy never cleaned up the window message handler.

I’m applying for the “Fixing Beta Testing and Forking” project. The forking feature is what I’m most excited about working on — I’ve started reading through the project-related controllers and models to understand what a fork endpoint would need at the database and API level. I’ll be submitting a proposal with a concrete technical design for that.

Looking forward to contributing more and happy to discuss anything about the approach in PR #135.

Thanks, Deenu

1 Like
4

Thank you @Deenu_Bansal and @arpit_singhal . I will be checking the pull requests you submitted.

5

Thank you @cengique, I am looking forward to your feedback.

6

Hi, I’m interested in contributing to AnalySim for GSoC 2026. I’ve started exploring the repository and will work on fixing setup/testing issues. Could you guide me on priority bugs for beta testing?

7

Hi! I’ve submitted this PR to improve the README for easier setup and onboarding.

I’m interested in contributing more to Analysim (and possibly GSoC 2026).
Could you please suggest any beginner-friendly issues I can work on next?

Thanks!

8

@Deenu_Bansal sorry for the late reply. I’m reviewing your PR and please email me directly so we can talk about your application.

9

Hi @cengique thanks for your response !

Looking forward to your feedback !

10

Hello @cengique ,

I’m preparing a GSoC 2026 application for AnalySim and wanted to share that I’m interested in continuing my work on the project in a larger scope.

Over the past period, I have been spending time reading the codebase and contributing through PRs and issues. Based on that, I prepared a draft proposal and emailed it as well.

I would really appreciate any comments or suggestions when you have time.

Thank you.