Skip to content

adaptive time step leads to early termination and dt=0 #1560

@lkugler

Description

@lkugler

Describe the bug
The use of adaptive time steps leads to WRF stopping before namelist's end of simulation with SUCCESS COMPLETE WRFand dt=0.

To Reproduce
Steps to reproduce the behavior:

  1. Use compiler and version
    icc version 19.1.0.166 (gcc version 4.8.5 compatibility)
mpif90 for the Intel(R) MPI Library 2019 Update 3 for Linux*
Copyright 2003-2019, Intel Corporation.
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC)
  1. To reproduce: Compile test case em_b_wave and use namelist options (add to existing &domains section)
 use_adaptive_time_step              = .true.,
 target_cfl                          = 1.2, 1.2, 1.2,
 max_step_increase_pct               = 5, 51, 51,
 starting_time_step                  = 600,
 max_time_step                       = 600,
 min_time_step                       = 100,
 step_to_output_time                 = .false.,
  1. Output is
Timing for main (dt=600.00): time 0001-01-01_02:50:00 on domain   1:    0.16676 elapsed seconds
Timing for main (dt=600.00): time 0001-01-01_03:00:00 on domain   1:    0.16646 elapsed seconds
Timing for main (dt=  0.00): time 0001-01-01_03:00:00 on domain   1:    0.16646 elapsed seconds
d01 0001-01-01_03:00:00 wrf: SUCCESS COMPLETE WRF

Also for other test cases, the simulation terminates after 3 hours, e.g. em_quarter_ss if you put more than 3 hours as simulation time.

Expected behavior
WRF should run until end_hour is reached (5 days for test/em_b_wave).

Screenshots
If applicable, add screenshots to help explain your problem.

Attachments
If applicable, attach supporting files: namelist.input, rsl.* files, etc.

Additional context
Add any other context about the problem here, such as:

  • This should be fixed by a bug fix in WRF4.3 as documented in the updates, right?
  • Tested in WRF4.3 and WRF4.2.2

configure.wrf.txt
namelist.input.txt

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions