-
Notifications
You must be signed in to change notification settings - Fork 705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{numlib}[GCC/11.3.0] FFTW v3.3.10 #15406
{numlib}[GCC/11.3.0] FFTW v3.3.10 #15406
Conversation
@boegelbot please test @ generoso |
@bartoldeman: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1114904311 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @SebastianAchilles |
Test report by @branfosj |
I'm putting #15406 (comment) here so we know about the failure. However, because I expect we'll have issues creating a |
Test report by @branfosj |
Test report by @branfosj |
@bartoldeman Can you clarify the intended use of this exactly? Do you want to split off the FFTW MPI parts into a separate module for |
It will need a few framework changes, in fftw.py to include both library paths. Also if we stick to FFTW.serial (GCC toolchain) / FFTW (gompi toolchain) If we use instead rename this PR from FFTW.serial to FFTW (GCC toolchain) and use FFTW.MPI (gompi toolchain), as more people on slack seem to be in favour of (3 vs 1 now), then |
@boegel would you prefer to pause this one for more discussion? |
@bartoldeman I think building FFTW with MPI support is the exception, so that should be reflected in the name, so |
@boegelbot please test @ generoso |
@SebastianAchilles: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1124220872 processed Message to humans: this is just bookkeeping information for me, |
@boegelbot please test @ jsc-zen2 |
@SebastianAchilles: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1124221707 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @SebastianAchilles |
Test report by @boegelbot |
Test report by @SebastianAchilles |
Test report by @jfgrimm |
Test report by @verdurin |
@bartoldeman Any updates on the necessary changes to framework that are required for this split FFTW approach? I would like to squeeze in those changes for the EasyBuild v4.5.5 release, which I would like to get out there ASAP... |
@boegel I was waiting for Open MPI 4.1.4 to be released but that doesn't seem to be in the cards, so we can't have FFTW-MPI yet since gompi/2022a can't be there yet. |
@bartoldeman It would be nice if we can get the necessary framework changes already included, since that'll make playing with FFTW-MPI and the candidate for |
Test report by @boegel |
Test report by @boegel |
@bartoldeman Open MPI 4.1.4 was released, see also merged PR #15426 Is there any reason not to merge this PR yet? |
This PR can be merged as is. The changes are needed to support FFTW.MPI only. |
I'll send a PR for FFTW.MPI later today |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Going in, thanks @bartoldeman! |
using --new-pr but manually adjusted
Note that since FFTW puts MPI functionality in separate libraries (such as
libfftw3f_mpi.so.3.5.8
) the concerns raised by @Micket in easybuilders/easybuild#649 (comment) that apply to HDF5 and netCDF don't apply for FFTW (or Boost).