Open n01r opened 9 months ago
Hi @n01r, what was printed on stdout
?
Hi @ax3l, this is how far the stdout
got:
Initializing AMReX (23.12)...
MPI initialized with 8 MPI processes
MPI initialized with thread support level 3
Initializing HIP...
HIP initialized with 8 devices.
AMReX (23.12) initialized
PICSAR (23.09)
WarpX (23.11-63-gb9b0748f1d00)
__ __ __ __
\ \ / /_ _ _ __ _ __\ \/ /
\ \ /\ / / _` | '__| '_ \\ /
\ V V / (_| | | | |_) / \
\_/\_/ \__,_|_| | .__/_/\_\
|_|
Level 0: dt = 1.530214125e-17 ; dx = 5.580357143e-09 ; dz = 8.081896552e-09
Grids Summary:
Level 0 8 grids 9977856 cells 100 % of domain
smallest grid: 1344 x 928 biggest grid: 1344 x 928
-------------------------------------------------------------------------------
--------------------------- MAIN EM PIC PARAMETERS ----------------------------
-------------------------------------------------------------------------------
Precision: | DOUBLE
Particle precision: | DOUBLE
Geometry: | 2D (XZ)
Operation mode: | Electromagnetic
| - vacuum
-------------------------------------------------------------------------------
Current Deposition: | Esirkepov
Particle Pusher: | Boris
Charge Deposition: | standard
Field Gathering: | energy-conserving
Particle Shape Factor:| 3
-------------------------------------------------------------------------------
Maxwell Solver: | Yee
| - staggered grid
Guard cells | - ng_alloc_EB = (4,4)
(allocated for E/B) |
-------------------------------------------------------------------------------
For full input parameters, see the file: warpx_used_inputs
--- INFO : Writing plotfile diags/diag1000000
--- INFO : Writing openPMD file diags/openPMDfw000000
--- INFO : Writing openPMD file diags/openPMDbw000000
And here the submit script:
@ax3l I just run today into the exact same problem. It was somewhat hard to debug, would you consider making this a required option until this has been solved? That way, other users won't run into this error again.
Btw. this is the stderr that I get on perlmutter:
amrex::Abort::6::CUDA error 700 in file /global/homes/p/pordyna/src/warpx/build_pm_gpu/_deps/fetchedamrex-src/Src/Base/AMReX_GpuDevice.cpp line 614: an illegal memory access was encountered !!!
SIGABRT
amrex::Abort::1::CUDA error 700 in file /global/homes/p/pordyna/src/warpx/build_pm_gpu/_deps/fetchedamrex-src/Src/Base/AMReX_GpuDevice.cpp line 614: an illegal memory access was encountered !!!
SIGABRT
amrex::Abort::3::CUDA error 700 in file /global/homes/p/pordyna/src/warpx/build_pm_gpu/_deps/fetchedamrex-src/Src/Base/AMReX_GpuDevice.cpp line 614: an illegal memory access was encountered !!!
SIGABRT
I recently encountered a cryptic error message when working with the
ParticleHistogram2D
reduced diagnostics. I forgot to set the parametervalue_function(t,x,y,z,ux,uy,uz,w)
. It would be good if we had something that told the user more clearly what to do.How to reproduce: Just run the example at
Examples/Physical_applications/laser_ion
but comment outPhaseSpaceElectrons.value_function(t,x,y,z,ux,uy,uz,w) = "w"
frominputs_2d
before running it.Tested on one node on Crusher (OLCF)
Error output