Ishaan Desai
Ishaan Desai
Currently mesh connectivity information is only defined for 2D cases in the form of triangles (constructed from edges). For 2D cases one could also define quads. Additionally for 3D cases,...
Recently in a presentation, users of this adapter pointed out that the limitations of the adapter are not explicitly mentioned in the documentation. This led the users to believe that...
Due to changes in https://github.com/precice/python-bindings/blame/develop/.github/workflows/build-docker.yml#L36-L44 the [workflow](https://github.com/precice/python-bindings/actions/workflows/build-docker.yml) to update the Docker image is triggered on the master branch. This workflow fails on the master branch: https://github.com/precice/python-bindings/actions/runs/7799939617/job/21271746402 because it tries to...
The following API functions currently do not have tests: * `set_mesh_edge` (and correspondingly also the new incoming function `set_mesh_edges`) * `set_mesh_triangle` (and correspondingly also the new incoming function `set_mesh_triangles`) *...
Similar to https://github.com/precice/precice/issues/1454 The precice-config file: https://github.com/precice/python-bindings/blob/develop/examples/solverdummy/precice-config.xml does not follow the naming conventions set in https://precice.org/community-contribute-to-precice.html#naming-conventions.
Right now the dependencies of the bindings are manually specified in the [pythonpublish](https://github.com/precice/python-bindings/blob/develop/.github/workflows/pythonpublish.yml) workflow. This is problematic when a release contains the addition of a new dependency, as then there...
Currently the `python-bindings` documentation lies in a [README](https://github.com/precice/python-bindings/blob/0d9b589d0a6b3fd16ab7872436230ecea9efd4d4/README.md) to which even the website documentation is [redirected to](https://precice.org/installation-bindings-python.html#more-details--troubleshooting). I propose to move most part of the documentation to the website and...
Currently the dockerfile used in CI runs is `precice/ci-spack-pyprecice-deps-1804` which is the dockerfile on [python-bindings/develop](https://github.com/precice/python-bindings/blob/0d9b589d0a6b3fd16ab7872436230ecea9efd4d4/spack/ci-spack-pyprecice-deps-1804.dockerfile) whereas actually the dockerfile from the respective fork or branch needs to be used in...
When the python `logging` module is used to generate log output in a code which is using the python-bindings, the assertion statements are not printed as part of the log....