GNU compilation with no leap calendar

M

markebouch

New member
hi everyone,
I am using boundary condition data that do not have 29.2 so I need to compile with no leap calendar.
I firstly compiled WRF (version 4.6) using gnu and adding the -DNO_LEAP_CALENDAR flag for ARCH_LOCAL in the configure.wrf and then for WPS (version 4.3.3) I added the same flag (-DNO_LEAP_CALENDAR) for CPPFLAGS in configure.wps.

The compilation was successful but then when trying to run simulations the model keeps getting stuck in wrf at the 14th task. To be more precise that's the error I get in the rsl.error.0014 file:
*************************************
d01 1801-01-11_00:00:00 alloc_space_field: domain 2 , 6427200 bytes allocated
d01 1801-01-11_00:00:00 alloc_space_field: domain 2 , 89098288 bytes allocated
RESTART: nest, opening wrfrst_d02_1801-01-11_00:00:00 for reading
d01 1801-01-11_00:00:00 Input data is acceptable to use:
MPICH ERROR [Rank 14] [job id 6684192.0] [Mon Mar 23 18:15:26 2026] [nid001373] - Abort(939550479) (rank 14 in comm 0): Fatal error in MPIR_CRAY_Bcast_Tree: Other MPI error, error stack:
MPIR_CRAY_Bcast_Tree(183): message sizes do not match across processes in the collective routine: I am using 4 but a peer process on my node is using 3000
aborting job:
Fatal error in MPIR_CRAY_Bcast_Tree: Other MPI error, error stack:
MPIR_CRAY_Bcast_Tree(183): message sizes do not match across processes in the collective routine: I am using 4 but a peer process on my node is using 3000

Did I do anything wrong in the compilation? Could maybe anyone help me with that? Let me know if you need any more information.
Thank you so much
 
Hi,
If you're still experiencing this problem, please package all of your rsl* files into a single *.tar or zipped file and attach that, as well as your namelist.input file, configure.wrf file, and the compile log so we can take a closer look. Thanks!
 
Hi,
Thank you for your response!
I am trying to upload the file here in the forum but i keep getting the following error: "The upload failed because the temporary directory was missing. The site administrator will need to resolve this before any files can be uploaded" so here is a wetransfer link to the file instead
rsl_and_config.tar.gz
I hope that works and it is helpful
 
Hi, apologies for the delay. I'm not able to access the file you shared due to permission restrictions, but the forum should now be fixed so that you can attach files here again.
 
Hi, no worries at all. Thank you for reaching out again. Yes, wetranser links are only valid for 7 days so i guess it just expired, but I am indeed able to upload it here now
 

Attachments

Hi,

I'm experiencing the same issue but with the Intel compiler. Despite having the NO_LEAP flags properly set in configure.wrf, real.exe continues to request February 29th data.

I'm from the same team as Markebouch, who started this thread. Please find attached my configure.wrf file for reference.

Regards,
Trang
 

Attachments

markebouch said:
Hi, no worries at all. Thank you for reaching out again. Yes, wetranser links are only valid for 7 days so i guess it just expired, but I am indeed able to upload it here now
Click to expand...
In the files you sent, the message (specific to real.exe) that appears in rsl.error.0000 shows the following:

Code: 
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     409
error opening met_em.d01.2019-09-04_12:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------

This either means that the dates in the namelist don't match the met_em* files you have in your directory, or that you didn't link the met_em* files to the directory.

Since this message is different than the one you mentioned originally, are these the rsl* files you intended to send?
 
ntrang said:
Hi,

I'm experiencing the same issue but with the Intel compiler. Despite having the NO_LEAP flags properly set in configure.wrf, real.exe continues to request February 29th data.

I'm from the same team as Markebouch, who started this thread. Please find attached my configure.wrf file for reference.

Regards,
Trang
Click to expand...

Hi, Although your issue is related to the original thread, it's a bit of a different problem since your team member is experiencing a model simulation hanging. To keep the threads specific to one issue, please start a new thread and we will assist you on that thread. Thanks, and apologies for the inconvenience.
 
Hi,
Yes, I changed a lot of compilers so maybe the first error was from another one.
Now I'm trying with a different compiler which is supposed to be working so I guess you do not need to deal with the initial error anymore
Thank you very much for all the support
 
You must log in or register to reply here.
Back
Top