You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to be able to impose spatially-varying values for certain boundary conditions, especially Robin boundary conditions for cardiac mechanics simulations (a la this paper
Solution
Within a boundary condition for a given face, the user could provide a .vtp file of the same face, with certain arrays defined on it. For example, if you are simulating an idealized LV , a variable Robin BC on the epicardial surface, defined by epi.vtp, could be defined like
The user would have to generate epi_variable_Robin.vtp, which has the same morphology as epi.vtp, but with arrays Stiffness, Damping, and External_pressure.
Additional context
This has been implemented in the (private) repository svMultPhys, which is an offshoot of svFSI.
Code of Conduct
I agree to follow this project's Code of Conduct and Contributing Guidelines
The text was updated successfully, but these errors were encountered:
That would be super useful. The idea of #77 was to do the same for volume parameters.
Ideally, this could be unified with getting a choice for every material/bc parameter you're setting in the input file: either scalar or a path to the .vtp or .vtu.
Problem
It would be very useful to be able to impose spatially-varying values for certain boundary conditions, especially Robin boundary conditions for cardiac mechanics simulations (a la this paper
Solution
Within a boundary condition for a given face, the user could provide a
.vtp
file of the same face, with certain arrays defined on it. For example, if you are simulating an idealized LV , a variable Robin BC on the epicardial surface, defined byepi.vtp
, could be defined likeThe user would have to generate
epi_variable_Robin.vtp
, which has the same morphology asepi.vtp
, but with arraysStiffness
,Damping
, andExternal_pressure
.Additional context
This has been implemented in the (private) repository svMultPhys, which is an offshoot of svFSI.
Code of Conduct
The text was updated successfully, but these errors were encountered: