Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

WRFV4 with PGI - dmpar

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

I did those but it didn't seem to change anything.
I am also a bit confused, if I am trying to use dmpar, then why would I need to un-set those options?
I thought that maybe the path was wrong, that's why it couldn't find mpif.h?
 

Attachments

  • compile_54_noMPI.log
    849.8 KB · Views: 10
Can you try compiling the attached test program with
Code:
mpif90 -o mpi_test.o -c mpi_test.f90
and see whether that works? This test program includes the "mpif.h" file, the path to which should be set by your mpif90 compiler wrapper. If compilation of this test program fails, then I think the issue may not be related to WRF, but to a more general issue with the MPI installation on your system. However, if you're able to bulid the test program, then the issue may be specific to WRF.
 

Attachments

  • mpi_test.f90
    142 bytes · Views: 22
Hi, this is my ouput.

PGF90-S-0017-Unable to open include file: mpif.h (mpi_test.f90: 3)
PGF90-S-0087-Non-constant expression where constant expression required (mpi_test.f90: 5)
0 inform, 0 warnings, 2 severes, 0 fatal for mpi_test

I have mpich compiled with PGI on my system.
 
Given that the small test program fails to compile with 'mpif90', it appears that the issue is not specific to WRF. The problem may be in the installation of MPI, or it may be related to your shell environment. If possible, it may be easiest to consult with your IT staff to work through issues in compiling the test program before focusing on the WRF model.
 
So, I fixed the problem.
I thought I would update this because looking at problems online, then finding someone with the same issues BUT no answer is incredibly annoying! haha.

I had a problem with how my mpi was compiled. I had issues with mpi and anaconda. My system was loading anaconda first, then on my bash files. There were things in my bash that could not overwrite the things that anaconda was calling. The way we got around this was to create a new user on my local host. So now my localhost (my PC) has user and user-wrf, where user-wrf ONLY has WRF files, data, etc. My normal user has everything else like anaconda. Both can access all data on the other system. This works for me, it may have been a quick "hack" to get around the anaconda issues but it does work.

Thank you for your help!
 
Hi,

Thank you so much for providing the solution to your problem. As you indicated, it will hopefully help someone in the future who runs into a similar issue. I'm glad to hear that you were able to resolve it!
 
Top