-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Solid viscosity update and restructuring first pass. Added preliminary viscosity test. Compiles and runs, but all existing struct and ustruct tests fail. Also, fluid/carreau-yasuda 3-procs fails. * Add useful comments * Update comments for solid visc models * Updating solid viscosity for ustruct. Removing solid viscosity stabilization in ustruct_xd_c() following Vijay's svFSI fork * Solid viscosity update for struct_2d(). Cleanup comments in struct_3d_carray() * Adding back viscosity-based stabilization in ustruct_xd_c(). PROBABLY REMOVE LATER. Also, print solid_viscosity parameters * Modifying viscosity test case and documentation * Removing viscosity-based stabilization in ustruct_xd_c(). According to Vijay, not important. Not included in Vijay's fork. This causes 2 ustruct tests (tensile_adventitia_HGO and LV_Guccione_active) to fail, because due to their larger momentum stabilization terms, they are slightly impacted by viscosity-based stabilization. * Potential viscosity bug fix (very important for convergence) * Minor bug fix in Newtonian tangent. Doesn't seem to improve convergence. Probably still another bug in Newtonian tangent. * Updating Newtonian viscosity test case, adding Potential viscosity test case * Adding note about likely error in Newtonian tangent * Add ustruct viscosity tests, update load profile description in READMEs * Change input file to take only "Viscosity". Code determines if Solid_viscosity or Fluid_viscosity from context * Replace raw strings with EquationType physics types. Add CMM and stokes to supported physics for fluid viscosity (integration tests now pass). Fixed small typo in pipe_3d_petsc input file viscosity definition * Removing references to old solid_viscosity
- Loading branch information
1 parent
e1ac609
commit f754c50
Showing
99 changed files
with
2,391 additions
and
478 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.