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

Spatially-varying boundary condition values #291

Open
1 task done
aabrown100-git opened this issue Oct 22, 2024 · 1 comment
Open
1 task done

Spatially-varying boundary condition values #291

aabrown100-git opened this issue Oct 22, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@aabrown100-git
Copy link
Collaborator

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 by epi.vtp, could be defined like

<Add_BC name="epi" > 
      <Type> Variable Robin </Type> 
      <Spatial_values_file_path> epi_variable_Robin.vtp </Spatial_values_file_path> 
</Add_BC> 

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
@aabrown100-git aabrown100-git added the enhancement New feature or request label Oct 22, 2024
@mrp089
Copy link
Member

mrp089 commented Oct 22, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants