-
Notifications
You must be signed in to change notification settings - Fork 351
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
Named Particle SoA Components #3614
Comments
@atmyers volunteered to take this on 🙏 We decided to only add naming arrays for SoA (compile-time and runtime) particle components. ExamplesHere is an example of methods that we will need from ImpactX:
WarpX uses this earlier implementation: Performance NotePlease also add two signature of the form AddRealComp(name, comm);
AddRealComp({name1, name2, ...}, {comm1, comm2, comm3}); // or as pairs? so people can avoid double resizes (#3615 #3861). (Same for Int.) DeprecationPlease mark the old signature (w/o names) as deprecated - everyone can use the new signature without a problem: even if they do not use the name, this will make code more self-describing. Default NamesAs default names for the compile-time components and old TestsCurrently, there are no systematic tests in AMReX CI that add (and remove #3595) runtime components to containers and then use these containers (e.g., copy from, redistribute, etc.). Such tests need to be added to ensure correctness and stability. We currently do not cover the case where we add runtime components before the dummy multifab has been defined. |
X-ref:
ParticleContainer_*.to_df()
pyamrex#220It would be nice if AMReX supported the functionality to name particle attributes (as strings). In WarpX, we added this as
NamedParticleContainer
, but as a mainstream implementation we could avoid deriving yet another class type (because if we do, we will again have additional compile-time to bind that custom type in pyAMReX), and instead could just extend the particle classes with these runtime details.The text was updated successfully, but these errors were encountered: