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

Automatically disable prescribed boundary conditions #67

Open
fluidnumerics-joe opened this issue Nov 8, 2024 · 0 comments
Open

Automatically disable prescribed boundary conditions #67

fluidnumerics-joe opened this issue Nov 8, 2024 · 0 comments

Comments

@fluidnumerics-joe
Copy link
Member

GPU accelerated models still run prescribed boundary conditions on the CPU. This is done to make it easy to use prescribed boundaries. However, this has performance penalties, since the extboundary data needs to be updated on the host before filling in prescribed boundaries and pushed back to the device after filling prescribed boundaries.

On meshes that do not use prescribed boundaries anywhere, or are explicitly time independent boundaries, we should enforce disabling of the prescribed boundary conditions on behalf of the user to automatically promote optimal performance. When prescribed boundary conditions are detected, then the prescribed boundary condition evaluation should be retained.

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

No branches or pull requests

1 participant