Gsoc 2026 - vipul singh

Jobs & theses market GSoC
1

@Makis @gdenayer

Hi preCICE community!

I’m Vipul Singh, a first-year BTech CSE student from Galgotias University, India. I’m excited to apply for GSoC 2026 with preCICE!

About me:

  • Languages: C++, Python, TypeScript

  • Frontend: React, Node.js

  • Hardware: Arduino, ESP32

What I’ve done so far:

  • Currently working on Issue #1561: Making tests follow naming convention (GSoC 2026 good first issue)

Why preCICE:

I want to contribute to real scientific computing software that has actual impact. The codebase is well-structured and the community is welcoming. Working on Issue #1561 has given me good exposure to the project structure.

Availability:

I’m fully available throughout the GSoC period with no other commitments.

Looking forward to contributing more!

GitHub: https://github.com/vipulsin650-arch

1 Like
2

UPDATE

What I’ve done:

  • Fixed Issue #1561: Updated test configurations to follow preCICE naming convention
  • Renamed data/mesh names (e.g., stretch1 → Stretch-1, stretch2 → Stretch-2, pointa → Point-A)
  • Used full participant names (e.g., Activation-M1, Displacement-M1SM)
  • Updated both XML and C++ test files
  • PR #2464 merged successfully :white_check_mark:

@Makis

3

UPDATE

I solved another issue PR addresses Issue #1966 by fixing incorrect context matching in configuration checks.

Changes

  • Changed to in MappingConfiguration.cpp

  • Added participant name to error message in M2NConfiguration.cpp for better debugging

Files changed:

  • src/mapping/config/MappingConfiguration.cpp

  • src/m2n/config/M2NConfiguration.cpp

@Makis