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

Implicit Views #778

Closed
PhilipDeegan opened this issue Nov 15, 2023 · 1 comment
Closed

Implicit Views #778

PhilipDeegan opened this issue Nov 15, 2023 · 1 comment
Assignees

Comments

@PhilipDeegan
Copy link
Member

In order to facility decomposition of work load for both threading and GPGPU.

The goal really, is that when we get to executing inside a solver, we shouldn't really care what sort of memory or objects we are dealing with, and inputs should be processed essentially as they are now but in potentially different forms, which are not necessarily patch based, or entire particle arrays.

This will also remove the need to use set on patch in a number of places, which is a coupling to SAMRAI

A view hierarchy should be created, and recreated per regrid, so that we have a set of pointers per patch, per level, and it should be easy to access particular members like it currently is on the hybrid state

potentially it might require a hierarchy per solver/state, ie. one for hybrid, one for mhd, or they might share a superclass

@PhilipDeegan
Copy link
Member Author

PhilipDeegan commented May 19, 2024

closed by #790

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done 🥳
Development

No branches or pull requests

2 participants