-
Notifications
You must be signed in to change notification settings - Fork 195
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
Diagnostics: Time-Averaged Fields #5165
Comments
@ax3l why would we need to enforce this assumption? |
@RevathiJambunathan because otherwise we will have run-away memory consumption (and more book keeping). As an update, we clarified in the last meetings (AMP and KISMET) with the current sciences cases in our projects that this assumption works very well for everyone that requested this feature. |
But we can have a running average being written out often - it will not consume more memory. We can chat during the hackathon |
This PR adds time-averaged field diagnostics to the WarpX output. To-do: - [x] code - [x] docs - [x] tests - [x] example Follow-up PRs: - meta-data - make compatible with adaptive time stepping This PR is based on work performed during the *2024 WarpX Refactoring Hackathon* and was created together with @RevathiJambunathan. Successfully merging this pull request may close #5165. --------- Co-authored-by: RevathiJambunathan <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Edoardo Zoni <[email protected]> Co-authored-by: Edoardo Zoni <[email protected]>
For LPI simulations, we would like a diagnostics that time-averages (over N subsequent steps) the output fields.
This is relatively easy to implement if we enforce the assumption that the output period P is greater than the averaging period N. For many simulations, that is sufficient and true.
The text was updated successfully, but these errors were encountered: