Update ABLASTR & pyAMReX

[ax3l]

To latest commit on development each.

[ax3l]

Test that shows changes:

• https://impactx.readthedocs.io/en/latest/usage/examples/cfchannel/README.html#constant-focusing-channel-with-space-charge

[ax3l]

Investigating if the changes in ECP-WarpX/WarpX#5284 just need a slightly higher tolerance now or if we cut too close to the beam.

[ax3l]

@RemiLehe even if I increase resolution (amr.n_cell), wrapping around the beam geometry.prob_relative
https://github.com/ECP-WarpX/impactx/blob/3a8ab8dc981aafccc9ab3de167e222d986f8b374/examples/cfchannel/input_cfchannel_10nC_fft.in#L43-L45
and rtol I do not et it to pass our tolerance again so far:
https://github.com/ECP-WarpX/impactx/blob/3a8ab8dc981aafccc9ab3de167e222d986f8b374/examples/cfchannel/analysis_cfchannel_10nC.py#L82

We expect these values:

    [sigx, sigy, sigt, emittance_x, emittance_y, emittance_t] ==
    [
        1.2154443728379865788e-003,
        1.2154443728379865788e-003,
        4.0956844276541331005317e-004,
        1.000000000e-006,
        1.000000000e-006,
        1.000000000e-006,
    ]

and I see these:

    [
        0.00111891388596667,
        0.0011285746858011444,
        0.0003732679938919104,
        9.993789938274477e-07,
        1.0106011946996333e-06,
        1.0016124683067494e-06
    ]

[EZoni]

I was thinking that another possibility to check this would be to switch on/off the change of ECP-WarpX/WarpX#5284 (a one-line change) locally and see what effect it has on a given test that currently fails, if you haven't already tried.

[ax3l]

Thanks @EZoni - that line causes the issue.

[ax3l]

CUDA issue needs ECP-WarpX/WarpX#5346 to fix

[ax3l]

yay