Hi everyone 
I’m Ankit, a third year IT student. I’m interested in contributing to preCICE through GSoC 2026.
Background: C, C++, Python, MATLAB, Compiler Design (handling with ASTs), Software Engineering
What I’ve done so far: I’ve spent time understanding the preCICE codebase and submitted my few PRs –
#2513 [OPEN] – addresses issue #2442(allowing convergence measures to use written but non-exchanged data). This involved modifying the coupling scheme configuration to relax a validation restriction and adding an integration test.
#2487 [MERGED] – addresses #2248, renames the Fortran functions for consistency with C/C++ naming scheme.
Project Interests: Clean multi-step configuration, Error messages with configuration context
Looking forward to contributing more. Happy to receive any feedback on the PR.
Best, Ankit
2 Likes
Hi all,
Since last time, I opened another PR #2517 which prevents participant usage after it has encountered a non-recoverable exception due to, let’s say, communication buildup failure in initialize().
I also performed the entry test for the project Clean multi-step configuration –
Building preCICE from source -
Running the elastic tube 1D tutorial –
Simulations generated –
Modifying the precice-config.xml -
removing <data name="CrossSectionLength"... /> to trigger error
Locate and modify the error message in the source code –
Rebuilt and installed –
New error message upon running the solvers –
Looking forward to more contributions. Open for feedbacks.
hi @Makis, @fsimonis I have submitted my GSoC proposal for “Error messages with configuration context” project and understand that maintainers are busy. Although, If you get a chance to review it, I would really appreciate any feedback or suggestions for improvement.
