GSoC 2026 | Shraddha Sharma

Hello everyone,

I am Shraddha Sharma, a first-year student pursuing B.Tech from Chennai, India.
I am interested in contributing to the
‘Error messages with Configuration context’ for GSoC 2026.

Motivation for GSoC:
As a first-year student, I am interested in learning new things and there can be nothing better than contributing to open source and learn new skills from experienced mentors and other contributors and developing peer connections.

What interests me the most about the Project?
What interests me most about this project is how much of a real difference it can make for users. It feels really frustrating when something goes wrong, and we get an error without knowing where in the file the problem is which makes it even harder. I find it really meaningful to work on something that directly reduces that frustration, by adding line numbers to errors just like a compiler would. It would make preCICE much more approachable for newcomers and experienced users.

Commitments:
I won’t have any other commitments during the GSoC period and will be fully focused on the project.

Previous Experience:
(i) I am familiar with the concept of OOPs in C++
(ii) I am familiar with basic Data Structure and Algorithms

Relevant Skills:
I have experience in programming languages: Java, C, C++, and Python.
Web Development: HTML/CSS and JavaScript.
Experience with Git and GitHub

Previous Experience with Git and GitHub:

My previous experience with Git and GitHub include contributions to few open source organisations :

(i) Python Software Foundation(PSF): I had raised PRs regarding documentation issues but it was unmerged as according to maintainer:
“Closing because this isn’t adding much value to the project. Half of these docstrings are on objects that don’t need an explanation, and this effort would be better directed in solving bugs.”

(ii) firstcontributions:

Screenshot 2026-03-10 001736

(iii) I am currently regualrly working with Git creating branches, raising PRs.

Entry Cases:
(i) I was able to set up preCICE from source.
(ii) Reviewed the README.md and contributors guidelines.

Closing:
I am really excited to contribute to preCICE and will contribute actively.
I will raise PRs and update soon.

Thank You!

2 Likes

I fixed a documentation issue:
#2012 API changelog in functions
Now moving forward to complex issues.

Thank You !

Implemented getCurrentLocation() in ConfigParser which provides line number and snippet context in XML configuration error messages (addressing #751)

Worked on issue #522(Landing page: Citation details outdated/broken)

Currently running the elastic tube 1D tutorial as part of the entry test

Thank You!

Successfully completed the second entry test!
Ran the elastic tube 1D tutorial: using the C++ fluid and solid solvers
Triggered a configuration error: by setting ‘time-window-size’ to ‘-1’ in ‘precice-config.xml’.
Built:

Located the error:

Before modification:

After modification:

I have also explored ConfigParser.cpp and implemented a getCurrentLocation() helper that extracts line number and source snippet during XML parsing. I have the changes ready but hit the collaborator restriction when opening a PR. I’d love feedback on my approach before submitting formally.
Looking forward to contributing!

Quick Update on the PRs raised:

I implemented getCurrentLocation() in ConfigParser.cpp which captures the line number and XML snippet during parsing. (Issue #751)

Merge-ready PRs:

Looking forward to feedback!

Thank You !