diff options
| author |  Andrew Myers <atmyers@lbl.gov>
| 2021-10-18 14:06:08 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2021-10-18 14:06:08 -0700 |
| commit | 2bc1322aa76f7026e5b42639bb3d12125da2407c (patch) | |
| tree | 7b8dbd4285fea5d47bf2b2b18a24af767342f34a /Source/Utils/WarpXMovingWindow.cpp | |
| parent | 3e9903c07561c24bb8309a7bfa8feeb76ba2eebd (diff) | |
| download | WarpX-2bc1322aa76f7026e5b42639bb3d12125da2407c.tar.gz WarpX-2bc1322aa76f7026e5b42639bb3d12125da2407c.tar.zst WarpX-2bc1322aa76f7026e5b42639bb3d12125da2407c.zip | |
Option to do single precision mesh communication. (#2294)
* option to use single precision guard cell exhanges
* add missing files
* fix namespace issue
* change precision of comms to float
* ParmParse the single_precision_comms flag
* set back to real
* test
* make sure dst is filled
* nGrow -> nGrowVect
* restore float
* don't override valid cells
* single precision mesh
* whitespace
* wrap SumBoundary
* Wrap additional uses of FillBoundary.
* catch missing copies of ParallelCopy
* missing OverrideSyncs
* add wrapper for iMultifab
* fix typo
* moar typos
* typo
* strip single_precision_mesh option
* fix original copy
* update fusible syntax
Co-authored-by: Weiqun Zhang <WeiqunZhang@lbl.gov>
* Fix: Single Precision Builds
Should not copy around data for `do_single_precision_comms`
* Docs: warpx.do_single_precision_comms
* initialize this tmp multifab to 0.0
* fix tiny profile label
* remove orig copies, they are only correct for FillBoundary
* loosen tolerance for space charge tests for single precision
* missing some setVal
* another missing setVal
* missing setVal
* add wrapper for new version of sumboundary
* add explicit cast to silence compiler warning
* add a test for single precision comms
* revert change to test precision
* add benchmark for single precision comms test
* restore tolerance I removed by mistake
* tolerance
* copyright headers
* drop tolerance for single precision tests in default analysis script
* missing python module
* bump tol again
* fix bad merge
* Apply suggestions from code review
Co-authored-by: Axel Huebl <axel.huebl@plasma.ninja>
Co-authored-by: Remi Lehe <remi.lehe@normalesup.org>
Co-authored-by: Axel Huebl <axel.huebl@plasma.ninja>
Co-authored-by: Weiqun Zhang <WeiqunZhang@lbl.gov>
Diffstat (limited to 'Source/Utils/WarpXMovingWindow.cpp')
| -rw-r--r-- | Source/Utils/WarpXMovingWindow.cpp | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/Source/Utils/WarpXMovingWindow.cpp b/Source/Utils/WarpXMovingWindow.cpp index 9b270469c..a95b58a41 100644 --- a/Source/Utils/WarpXMovingWindow.cpp +++ b/Source/Utils/WarpXMovingWindow.cpp @@ -10,6 +10,7 @@ #include "BoundaryConditions/PML.H" #include "Particles/MultiParticleContainer.H" +#include "Parallelization/WarpXCommUtil.H" #include "Utils/WarpXConst.H" #include "Utils/WarpXProfilerWrapper.H" @@ -292,7 +293,7 @@ WarpX::shiftMF (MultiFab& mf, const Geometry& geom, int num_shift, int dir, if ( WarpX::safe_guard_cells ) { // Fill guard cells. - tmpmf.FillBoundary(geom.periodicity()); + WarpXCommUtil::FillBoundary(tmpmf, geom.periodicity()); } else { IntVect ng_mw = IntVect::TheUnitVector(); // Enough guard cells in the MW direction @@ -300,7 +301,7 @@ WarpX::shiftMF (MultiFab& mf, const Geometry& geom, int num_shift, int dir, // Make sure we don't exceed number of guard cells allocated ng_mw = ng_mw.min(ng); // Fill guard cells. - tmpmf.FillBoundary(ng_mw, geom.periodicity()); + WarpXCommUtil::FillBoundary(tmpmf, ng_mw, geom.periodicity()); } // Make a box that covers the region that the window moved into |