-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add Levenberg-Marquardt model calibration #31
Conversation
Fix Debug build Set debug messages to be printed in debug build Fix deprecation warnings
Update: I think I got the interface and coupling to svSolver to work now. I have also created a simple C++ test case for the interface while doing this, which should be added to the github actions (#30 ). Still wondering what would be the best way to add a test case specifically for the svSolver (and eventually svFSIPlus) coupling. One issue I'm having is running the test cases when I build the code using CMake instead of pip (on Sherlock). In this case, pytest cannot find the svzerodplus package that is required to run tests/test_integration_cpp.py. Is there a way to have this work when using the CMake installation? I will push my changes in the next few days! |
…nto least-squares Pulled latest changes before pushing back working interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me for the most part! The only problem is pytest not working when using the CMake build on Sherlock.
Unfortunately the python interface (which pytest is using) only works when installing svZeroDPlus via pip. But the pip installation should work on brocken. |
Thanks for adding the test, @richterjakob! I'll move the |
Haha, you were faster than I could type that the only thing left is to decide whether keeping |
But otherwise I think we are ready to merge, right? |
In that case, one last thing I need to do is test the pip installation and pytest on Sherlock. If that doesn't work, it's not huge deal because people pushing from Sherlock can still use Github actions in their own branches to run the tests. But I will add a note in the documentation if that is the case. I should have this done this morning. If there's nothing else to add (apart from moving the |
I tested the build on Sherlock already and it worked without problems. If that's okay, I would like to do the honour of merging this 😁 |
No description provided.