-
Notifications
You must be signed in to change notification settings - Fork 196
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
AMReX/pyAMReX/PICSAR: weekly update #5391
Conversation
Looks like WarpX's NamedComponentParticleContainer needs an update. AddRealComp(const std::string& name, ...) exists now in AMReX. |
I renamed the WarpX functions Does this look good to you? There are only two instances left where we are directly calling the AMReX functions from WarpX, without wrapping them in WarpX functions. It's not clear to me whether the goal of recent PRs such as AMReX-Codes/amrex#4163 was to remove the WarpX functions and use directly the AMReX ones. |
Also, in WarpX's newly renamed functions |
Discussed on Slack: |
Rebase after #5399 to pass the |
I just disabled auto-merge here, please feel free to review and suggest further changes as in #5401 if you see that something is missing. Here we decided to rename the WarpX functions, since we thought it creates less confusion with the AMReX functions, until the permanent change (which will remove the WarpX functions) is implemented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thanks!
Changing the names of the routines is fine since this is only a temporary fix until they are ultimately removed.
- Weekly update to latest AMReX: ```console ./Tools/Release/updateAMReX.py ``` - Weekly update to latest pyAMReX: ```console ./Tools/Release/updatepyAMReX.py ``` - Weekly update to latest PICSAR (no changes): ```console ./Tools/Release/updatePICSAR.py ```
./Tools/Release/updateAMReX.py
./Tools/Release/updatepyAMReX.py
./Tools/Release/updatePICSAR.py