Edoardo Zoni

@wangjia-ai Thank you for reporting this. A few bug fixes that address this issue were just merged this morning, see commit 48c1a86047fb06b957474c5a92d15f104c77b039 and the corresponding PR, #3290. Would you like...

@wangjia-ai Glad to see that the main issue is solved. Regarding the distortion points you see, we discussed among a few developers and we think the distortion might go away...

@wangjia-ai Thank you. Can you please confirm to us that these distortion points do **not** show up if current correction is turned off (`psatd.current_correction=0`)?

Thank you, Remi. I will address the comment asap. As far as aborting the code is concerned, here's the code for it: https://github.com/ECP-WarpX/WarpX/blob/5761b4bf998eab84ea0f7e4b132026593f3ddf9f/Source/WarpX.cpp#L980-L983

@lucafedeli88 @RemiLehe Something that came to mind, while thinking about the idea that this could be more of a numerical issue, is to try activating divergence correction (namely, div(E) and...

@lucafedeli88 @RemiLehe There could be also the issue of using such a high spectral order (128, not sure why so high for this LWFA case?). I wonder if it could...

@WeiqunZhang @dpgrote In my view, this is not meant for debugging only. It is meant to facilitate code development overall. Here's an example of a simple code development workflow that...

Closing this PR because all changes are included in #3484.

> This was done in order to reduce the number of registers/thread to increase the warp occupancy on GPUs. Could you also post in the PR description above some data/plots...

@Thierry992 In order to fix the `xmid` warning, you can add `amrex::ignore_unused(xmid);` inside the `if constexpr (depos_order == 0)` block (before the `return` command), since `xmid` is not used there....