wrf.exe

  1. G

    Segmentation Error

    Hello All I hope you're doing well I am doing a simulation on WRF 4-3.2 but wrf.exe fails just i am running for 30 hours (6 hours spinup time) I get the following error: Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0...
  2. B

    ACM2 error :RIBX never exceeds RIC

    I use pxlsm and can successfully run the ACM2 scheme with three levels of nesting (36.12.04km). But when I run 12km and 04km separately, I got this error. 36km can run successfully. Model crashed immediately FATAL CALLED FROM FILE: <stdin> LINE: 415 RIBX never exceeds RIC, RIB(i,kte) =...
  3. M

    WRF running very slow after new compile

    Hello all, I recently had to recompile WRF because the HPC environment I run WRF on had its OS updated which caused many files WRF depended on to be updated and renamed. I created a thread on this issue and it can be found here.. While I was able to successfully recompile and run WRF, it now...
  4. H

    Change the value of the "nens" parameter of SPPT in namelist.input

    I'm going to change the value of "nens" parameter of SPPT in namelist.input, but the result is exactly the same. The related Settings of namelist.input are as follows. 1st: rand_perturb = 1,1,1, sppt = 1,1,1, lengthscale_sppt...
  5. S

    wrf fails run with ECMWF model forcing data

    Dear Colleges, I am using ECMWF high-resolution analysis downloaded from https://rda.ucar.edu/datasets/ds113.1/ to run the WRF model. I had difficulties with preprocessing the ECMWF by ungrib for some of surface variables which is a known issue...
  6. P

    WRF with WSM5 as microphysics stops at first nested domain

    When using WSM5 (mp_physics=4) in a nested domain, WRF stops at the creation of the 1st nested domain without any error. To be exact d02 2007-05-27_12:00:00 alloc_space_field: domain 3 , 36606528 bytes allocated is the last line. I have provided a rsl.error.0000 file with debug set to 1000. The...
  7. W

    (RESOLVED) Git not found???

    WRF V4.4 MODEL No git found or not a git repository, git commit version not available. Trying to run the WRF and i run into this issue in the rsl.error.0000 Haven't seen this before and I can't find any reference in other user posts. Any suggestions or reccomendations?
  8. N

    Model crashing at radiation time step

    WRF-4.1.3 Model is crashing at radiation time step with BouLac PBL scheme, but runs successfully with other PBL schemes. Tried changing radt to other values but seeing similar crashing with similar error. Any help would be appreciated. &time_control run_days = 0...
  9. A

    NLCD40 WRF run crashes because of module_sf_noahdrv.f90 (unit = 19, file = 'VEGPARM.TBL')

    Hello, I am trying to simulate a heatwave over California using WRF (NLCD Landuse). In order to make it work with NLCD, I added the line: geog_data_res = 'nlcd2011_30m+5m', 'nlcd2011_30m+2m', 'nlcd2011_30m+urbfrac_nlcd2011+30s', to my namelist.wps. I then did the following remapping procedure...
  10. H

    wrf.exe crash when using the new GEFS 0.5 data

    Hello Wrfhelp, We used GEFS 1 deg to initialize WRF V4.1.2 and it works for months without any problem. However when those data are replaced by GEFS 0.5 deg WRF starts to crash and returns the error which obviously related to the lw_physics schema. we are using those data ...
  11. L

    WRF stopped when incorporating WUDAPT into uWRF-BEP

    Dear WRF community, When incorprating WUDAPT urban datasets into WRF/BEP model, a problem was encountered when ./wrf.exe. The WRF source code (module_sf_urban.F,module_surface_driver.F,module_sf_noahdrv.F,module_sf_bep.F,module_sf_bep_bem.F) is adopted for 10 new urban classifications...
  12. C

    wrf.exe in dm+sm mode

    Dear colleagues, how to run wrf.exe if it is compiled in dm+sm mode?
  13. M

    wrf.exe error. Segmentation fault - invalid memory reference.

    Hello all, I am doing a simulation on WRFV3.9 but wrf.exe fails 20 days before finishing (I am running 2 months). I get the following error: Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x7F130EFF9347 #1 0x7F130EFF995E #2...
Top