Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapted compatibility-precice-dev branch #162

Conversation

Timo-Schrader
Copy link
Contributor

  • Added docstrings for some functions
  • Removed return statement in l. 593 of cyprecice/cyprecice.pxy (please confirm that this is correct)
  • Removed import statements in __init__.py since these functions do no longer exist.

timo-schrader added 2 commits January 11, 2023 19:43
@Timo-Schrader Timo-Schrader changed the title Compatibility precice dev Adapted compatibility-precice-dev branch Jan 11, 2023
Copy link
Member

@BenjaminRodenberg BenjaminRodenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks good to me 👍 I did not check it thoroughly, but let's merge this one quick and then we continue working in #159 together. Thank you!

@IshaanDesai IshaanDesai merged commit 8c52300 into precice:compatibility-precice-dev Jan 11, 2023
IshaanDesai added a commit that referenced this pull request Feb 20, 2023
* [WIP] Make bindings compatible with precice:develop

* Updating solverdummy and checkpoint related API functions

* Removing unnecessary semicolons

* Add correct arguments to functions in SolverInterface.cpp

* Add size as input argument to mesh connectivity API functions for testing

* Remove incorrect bracket from deleted namespace

* [WIP] Using same names for input arguments of API functions

* correct return type for setMeshEdge in SolverInterface.cpp

* void function setMeshEdge should not return anything

* Adapted compatibility-precice-dev branch (#162)

* Use precice-setup-action

* Modify solverdummy Action

* Use precice-setup action appropriately in steps

* Change apt-get commands to use sudo in build and test workflows

* Change rm -rf commands to use sudo in build and test workflows

* Remove get_mesh_vertices and get_mesh_vertex_ids_from_positions

* Use precice-setup-action in Spack workflow

* Simplify testing.

* Remove sudo.

* Use benjaminrodenberg/precice:develop

* Try with root user.

* Update solverdummies test.

* Fix solverdummy.

---------

Co-authored-by: Ishaan Desai <[email protected]>
Co-authored-by: Timo-Schrader <[email protected]>
IshaanDesai added a commit that referenced this pull request Mar 9, 2023
* [WIP] Make bindings compatible with precice:develop

* Updating solverdummy and checkpoint related API functions

* Removing unnecessary semicolons

* Add correct arguments to functions in SolverInterface.cpp

* Add size as input argument to mesh connectivity API functions for testing

* Remove incorrect bracket from deleted namespace

* [WIP] Using same names for input arguments of API functions

* correct return type for setMeshEdge in SolverInterface.cpp

* void function setMeshEdge should not return anything

* Adapted compatibility-precice-dev branch (#162)

* Use precice-setup-action

* Modify solverdummy Action

* Use precice-setup action appropriately in steps

* Change apt-get commands to use sudo in build and test workflows

* Change rm -rf commands to use sudo in build and test workflows

* Remove get_mesh_vertices and get_mesh_vertex_ids_from_positions

* Use precice-setup-action in Spack workflow

* Use main branch of setup-precice-action

* Use container precice/precice:develop

* Remove sudo from build-and-test.yml

* Use C++17 in setup.py

* Install sudo in workflows and use it to remove lock file

* Use user: root in setup_test workflow

* Remove sudo from the command to remove lock files

---------

Co-authored-by: Timo-Schrader <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants