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

Option to prescribe spherical normal and tangential velocties individually #4387

Open
anne-glerum opened this issue Oct 29, 2021 · 3 comments

Comments

@anne-glerum
Copy link
Contributor

It would be wonderful to be able to prescribe either the normal or the tangential velocity component on a boundary of a spherical domain, e.g. a chunk. For box models it is possible to prescribe e.g. the x component of velocity and leave the tangential y and z components free.

Would it be possible to use deal.II's compute_nonzero_tangential_flux_constraints() and compute_normal_flux_constraints() for this?

@tjhei
Copy link
Member

tjhei commented Oct 29, 2021

Can you be more precise what you are trying to achieve? If you want free tangential velocity and a given normal flux, then nonzero normal flux is the correct one to use in deal.II.

@anne-glerum
Copy link
Contributor Author

My specific use-case would indeed be to prescribe a normal velocity on the lateral boundaries of a chunk, but leave the tangential components of velocity free. At the moment, I have to prescribe all components of velocity on a spherical domain's boundary.

In essence, I'd like the same functionality as for boundary velocities on box geometries, where one can specify (or not specify) the velocity magnitude per coordinate direction.
E.g. set Prescribed velocity boundary indicators = east phi: function.

At the moment, I can specify the boundary velocity in spherical coordinates, using spherical unit vectors, but, the way I understand it, still all velocity components are prescribed.

@tjhei
Copy link
Member

tjhei commented Oct 29, 2021

Then you would need to use compute_nonzero_normal_flux_constraints() instead of compute_no_normal_flux_constraints(). Shouldn't be too difficult to do the change. The hardest part is to make a plugin system.
Do you want to give it a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants