Edoardo Zoni

Here's an example of output with print statements for debugging: [test_1d_photoneutralization_dsmc.txt](https://github.com/user-attachments/files/23490081/test_1d_photoneutralization_dsmc.txt). This is the relevant diff showing where I'm printing: ```diff diff --git a/Source/Particles/Collision/BinaryCollision/BinaryCollision.H b/Source/Particles/Collision/BinaryCollision/BinaryCollision.H index 89d4a93e2..6f7889151 100644 --- a/Source/Particles/Collision/BinaryCollision/BinaryCollision.H...

@atmyers I was debugging this with @RemiLehe and things are still unclear here. Here's the latest output with some ad hoc print statements: [test_1d_photoneutralization_dsmc.txt](https://github.com/user-attachments/files/23507870/test_1d_photoneutralization_dsmc.txt). Currently, it seems like `ux_avg` cannot...

I confirm that it does seem to have something to do with photons specifically. If I change the order of the parent species in the input file, the error occurs...

Feedback from @WeiqunZhang shared on Slack: `DefautlInitializeRuntimeAttributes` is supposed to initialize the resized runtime component vectors. The problem seems to be its caller. It's called in `SplitAndScatterFunc`: https://github.com/BLAST-WarpX/warpx/blob/cbe73680443ea633c24ba79f133e8d8b63310baf/Source/Particles/Collision/BinaryCollision/ParticleCreationFunc.H#L254-L267 The data...

With or without #6413, this is what I see from `PhysicalParticleContainer::Evolve` when called for the `electrons` species, which inherits from the `photons` species: ``` 25: Starting PhysicalParticleContainer::Evolve for electrons 25:...

@WeiqunZhang @atmyers @ax3l @RemiLehe If you look at the output in https://github.com/BLAST-WarpX/warpx/pull/6275#issuecomment-3564815506, the number of components and the names seem corret to me. Isn't this inconsistent with what @WeiqunZhang had...

I'm going to push the print statements I'm adding for debugging, to make it easier to follow my comments with output snippets.

@WeiqunZhang @atmyers @ax3l @RemiLehe For me something along the lines of 277fee4 (explicit initialization of the average momentum components to zero inside `DefaultInitializeRuntimeAttributes`, even though I thought it wasn't needed)...

@RemiLehe @oshapoval All CI tests passed here, despite the particle boundary change.

@RemiLehe @oshapoval Some CI tests failed here, because of the particle boundary change: - `1d`: ``` The following tests FAILED: 26 - test_1d_ionization_neutral_dsmc.analysis (Failed) 27 - test_1d_ionization_neutral_dsmc.checksum (Failed) 30 -...