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

Bad value during integer read at module_date_time

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.

A

alainF

Member
Hello,
I have an error at the beginning of the run.
The logs of real and wrf are attached. In addition, I get the following messages on the screen :
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 1 grid%oid 1
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
At line 777 of file module_date_time.f90
Fortran runtime error: Bad value during integer read

Error termination. Backtrace:
#0 0x7fddb1475dfd in ???
#1 0x7fddb1476995 in ???
#2 0x7fddb147717d in ???
#3 0x7fddb1678296 in ???
#4 0x7fddb167c4dc in ???
#5 0x7fddb167d68c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7fddb0517554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
#0 0x7f2e745f6dfd in ???
#1 0x7f2e745f7995 in ???
#2 0x7f2e745f817d in ???
#3 0x7f2e747f9296 in ???
#4 0x7f2e747fd4dc in ???
#5 0x7f2e747fe68c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7f2e73698554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
#0 0x7ffa30fc6dfd in ???
#1 0x7ffa30fc7995 in ???
#2 0x7ffa30fc817d in ???
#3 0x7ffa311c9296 in ???
#4 0x7ffa311cd4dc in ???
#5 0x7ffa311ce68c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7ffa30068554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
#0 0x7f07587ebdfd in ???
#1 0x7f07587ec995 in ???
#2 0x7f07587ed17d in ???
#3 0x7f07589ee296 in ???
#4 0x7f07589f24dc in ???
#5 0x7f07589f368c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7f075788d554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
#0 0x7ffbd9b5bdfd in ???
#1 0x7ffbd9b5c995 in ???
#2 0x7ffbd9b5d17d in ???
#3 0x7ffbd9d5e296 in ???
#4 0x7ffbd9d624dc in ???
#5 0x7ffbd9d6368c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7ffbd8bfd554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
#0 0x7fbe5f6c7dfd in ???
#1 0x7fbe5f6c8995 in ???
#2 0x7fbe5f6c917d in ???
#3 0x7fbe5f8ca296 in ???
#4 0x7fbe5f8ce4dc in ???
#5 0x7fbe5f8cf68c in ???
#6 0x1212aa4 in ???
#7 0x12e669f in ???
#8 0x13532d6 in ???
#9 0x1357d7a in ???
#10 0x46ff25 in ???
#11 0x405871 in ???
#12 0x404d73 in ???
#13 0x7fbe5e769554 in ???
#14 0x404dcb in ???
#15 0xffffffffffffffff in ???
Click to expand...

Thank you for you help.
 

Attachments

  • namelist.wps
    1.4 KB · Views: 51
  • namelist.input
    8 KB · Views: 62
  • wrf.log
    9.8 KB · Views: 58
  • real.log
    424.4 KB · Views: 58
real.exe is done successfully for your case.
wrf.exe was actually running but was interrupted for some reason. There is no error message in your log file.

Please let me know how you build and run WRFV4.2. The log file indicates that you ran this case with only a single processor. The following output in your log file looks weird:
real_em: SUCCESS COMPLETE REAL_EM INIT
real_em: SUCCESS COMPLETE REAL_EM INIT
Timing for output 2 s.
Timing for loop # 57 = 6 s.
real_em: SUCCESS COMPLETE REAL_EM INIT
Timing for output 2 s.
Timing for loop # 57 = 6 s.
real_em: SUCCESS COMPLETE REAL_EM INIT
Timing for output 2 s.
Timing for loop # 57 = 7 s.
real_em: SUCCESS COMPLETE REAL_EM INIT
 
Hello,
I have attached the compile log file. I have compiled with smpar option. Actually, I could compile and run successfully in dmpar option but the run is quite slow. So I wanted to test the build in smpar mode.
I run real with : mpirun -np 5 ./real.exe
wrf with : mpirun -np 6 ./wrf.exe

I run real with 5 CPUs instead of 6 because it uses a lot of RAM memory.
 

Attachments

  • compile.log.txt
    708.4 KB · Views: 61
If you build the code in smpar mode, then the command for running real.exe and wrf.exe should be different to that when running the executable files built in dumper mode. I am suspicious this is the reason why I saw those weird output information n your log file. Please talk to your computer manager about how to run codes built in smpar mode.
 
You must log in or register to reply here.
Top