Bumped to Stage2025 for HPC

[jakob-fritz]

By this, also changed version of FFTW (as the previous one seems to not be included in Stage 2025)

[brownbaerchen]

I don't understand what's going on here. I was able to install mpi4py-fft in a fresh venv after loading the same modules as in this PR and then running

FFTW_LIBRARY_DIR="/p/software/juwels/stages/2025/software/FFTW/3.3.10-GCC-13.3.0/lib64" pip install --no-deps --force-reinstall -e .

However, when using the same command here, it complains that it does not find NumPy. Seems to me that the Python versions are getting mixed up somewhere. After loading the Scipy-Stack module, NumPy should be installed, which indeed it is because when installing pySDC, it is already there. Anybody knows what's happening?

[tlunet]

I don't understand what's going on here. I was able to install mpi4py-fft in a fresh venv after loading the same modules as in this PR and then running

FFTW_LIBRARY_DIR="/p/software/juwels/stages/2025/software/FFTW/3.3.10-GCC-13.3.0/lib64" pip install --no-deps --force-reinstall -e .

However, when using the same command here, it complains that it does not find NumPy. Seems to me that the Python versions are getting mixed up somewhere. After loading the Scipy-Stack module, NumPy should be installed, which indeed it is because when installing pySDC, it is already there. Anybody knows what's happening?

No idea, but I got similar problem before when loading Scipy-Stack. I believe there is another module that has numpy in it. But I would also strongly recommend not using any python install from JSC, but rather recompile python from source, create an environment from it, and install everything in there using pip.

[pancetta]

The strange thing is that this started to fail with the new stage. All of this worked before, except for this weird venv problem (which we got rid off). If I'm right, this is related to the new stage only. Want to call SC support (or keep bothering @jakob-fritz)?

[brownbaerchen]

Well how much time do you have at the moment, @jakob-fritz? I would be fine with opening a ticket at the support and postponing this a bit.

[jakob-fritz]

I can have a brief look at it now. If I don't find anything, you can open a ticket at SC support.

[jakob-fritz]

I could not really reproduce the issue, when using a venv in my own home directory (the shared one was not accessible to me, as it is owned by Robert). Therefore, I did some slight changes and let's see if it now works as expected.

[brownbaerchen]

I could not really reproduce the issue, when using a venv in my own home directory (the shared one was not accessible to me, as it is owned by Robert). Therefore, I did some slight changes and let's see if it now works as expected.

Same, I also found no issue when following the steps to install everything in a venv in my home directory.. So it looks like a combination of the new stages and the Gitlab pipeline that causes this issue..

[jakob-fritz]

Ok I cannot see, why it does not work with a venv on SCRATCH via Jacamar, but does work when you or I test it manually with a venv in the own home-directory.
So, @brownbaerchen if you want to, go ahead and open a ticket, as I did not find where the approaches differ (apart from the location of the venv)

[brownbaerchen]

Ok I cannot see, why it does not work with a venv on SCRATCH via Jacamar, but does work when you or I test it manually with a venv in the own home-directory. So, @brownbaerchen if you want to, go ahead and open a ticket, as I did not find where the approaches differ (apart from the location of the venv)

Well, thanks for trying anyways! I'll open a ticket next week. Really weird bug..