forked from SimVascular/svMultiPhysics
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
struct/ustruct 0D coupling (SimVascular#188)
* struct 0D coupling changes and test, but still some bugs * Bug fix, cleanup, and tests Bug fix: In set_bc.cpp, when computing flowrates with integ, I was calling the wrong overloaded integ function, so the integration was not being performed in the 'o' or 'n' configurations. Instead, the flowrates were being computed with the 'r'eference configuration. The tangent contribution, however, correctly accounted for the 'n' configuration, so it was inconsistent with the flowrate. This lead to poor convergence after significant deformation of the LV model in the test case. Cleanup: Removing some unnecessary lines and function arguments. Also, adding catch for invalid configuration character in gnnb(), and initializing v to 0 in fsils_bc_update() Tests: 2 tests, LV_NeoHookean_passive_genBC and LV_NeoHookean_passive. LV_NeoHookean_passive_genBC is the test for struct - 0D coupling feature, but I figured I'd add LV_NeoHookean_passive (no genBC coupling) anyway. With this commit, there is very good (not exact) agreement of results between vvedula22/svFSI and aabrown100-git/svFSIplus for LV_NeoHookean_passive_genBC. The convergence histories, AllData files, and results.vtu are all nearly identical. There is also good agreement for LV_NeoHookean_passive. * Extremely minor edit to LV_NeoHookean_passive input file * Add folwP check, finish test cases. * Bug for ustruct 0D coupling, ustruct test Fixed bug in set_bc.cpp for ustruct 0D coupling. When using ustruct, the Yo or Yn has nsd+1 components (nsd velocities and 1 pressure). When computing flowrate, using Yo or Yn with nsd+1 components caused an error in integ(). Error is avoided by explicitly providing the start (0) and stop (nsd-1) indices to integ(). This tells integ to only use the velocity components in Yo or Yn. Also, adding LV_NeoHookean_passive_genBC test. This is identical to the test in struct/, except uses ustruct. * Remove previous results folders when testing * Add CMM to valid physics for 0D coupling * Update genBC Makefile to use mpif90, remove system calls in tests * Add gcc to MacOS dependencies for testing Adding gcc in hopes that gfortran will be available to compile genBC on GitHub Mac machine (SimVascular#188) * Add debug statements for Github Mac (will revert) * Modify debug statements for Github Mac * Remove debug statements for Github Mac Keeping brew reinstall -v gcc in test.yml, which seemingly properly installs gfortran and allows genBC to be compiled in my test cases. * Addressing style comments Addressing style comments from Matteo and Dave in PR: SimVascular#188 * Removing LV_Holzapfel_passive svFSI.inp * Add all output fields to test cases and update ref sols * Change enum MechConfigType names
- Loading branch information
1 parent
308791b
commit 29a94c3
Showing
90 changed files
with
5,404 additions
and
122 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.