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

Error with adjusting some Register, Phys and Dyn_em.

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.


New member
I have successfully configured and compiled this version of the WRF V3.8 on ubuntu 16.10 in the past, but while using the same steps after adjusting the Registry and Phys, I got some errors during compilation and end up with an unsuccessful compile of em_real. Anyone knows what happened?? I have the successful and failed compile log files attached. During configuration I use a 64bit serial (13, ifort, icc) or (32, gfortran, gcc) with basic nesting.
Thank you for your help.


  • checkwrf-gfortan-succeed.log
    640.1 KB · Views: 50
  • checkwrf-gfortran-fail.log
    910.7 KB · Views: 50
  • checkwrf-ifort-fail.log
    1.5 MB · Views: 49
  • checkwrf-ifort-succeed.log
    603.7 KB · Views: 46
If you take a look at the unsuccessful compile logs, and do a search for the word "Error" (with a capital 'E'), you should find these errors:

 INTEGER , PARAMETER :: model_data_order   = DATA_ORDER_
Error: Parameter ‘data_order_’ at (1) has not been declared or is a variable, which does not reduce to a constant expression

    USE module_driver_constants, ONLY : DATA_ORDER_XYZ
Fatal Error: Can't open module file ‘module_driver_constants.mod’ for reading at (1): No such file or directory
compilation terminated.

I assume this is related to a change that you made when you modified the code. When you compile, a *.f90 file is created from each of the *.F files. You can take a look in your *.f90 file to find the line number that is causing the problem. For instance, the first error above shows that in line 53 (position 43) of module_driver_constants.f90 you have a problem with the variable 'DATA_ORDER_', and the exact problem is listed below that. You can then go to the module_driver_constants.F file to make the correction, as the *.f90 file is something that is generated during compilation, so any changes made in there will be ignored. Once you correct these problems, issue a 'clean -a' and then reconfigure and recompile. If it fails again, look for more errors, and continue to fix the modified code until you are able to compile successfully.