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

Search results

  1. M

    WRF running very slow after new compile

    Hi Ming, When I set the history_interval_h to 6, the output would be created in 6-hour intervals, but WRF was still running slowly. I compiled WRF using a GCC compiler. I will say that I was able to get WRF running on another colleague's version of WRF in their directory without issue. You can...
  2. 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...
  3. M

    Failure to run ungrib after HPC OS update: libjasper.so.1 not found

    Hi all, I tried running what mgduda suggested, but that didn't work. Instead, I had to recompile WRF and its running successfully now. I will say that it runs significantly slowly than it did before, and I'm not sure why. I'll be making a post in the Running WRF forum to see if I can get some...
  4. M

    Failure to run ungrib after HPC OS update: libjasper.so.1 not found

    Yes, another person set up most of WRF for me. I will take a look at those guides and see if I can get it running.
  5. M

    Failure to run ungrib after HPC OS update: libjasper.so.1 not found

    Hi there, Thanks for your reply. What would be the first step in recompiling WPS?
  6. M

    Failure to run ungrib after HPC OS update: libjasper.so.1 not found

    Hello all, I run WRF on an HPC system whose OS was recently updated. I attempted to run WPS for the first time after the OS update but it only generated the geo_em files. After looking through some files, I found the culprit for the unsuccessful WPS run: ./ungrib.exe: error while loading...
  7. M

    (RESOLVED) WRF crashes with "forrtl: severe (174): SIGSEGV, segmentation fault occurred"

    Hi, I was able to successfully run WRF by increasing the number of nodes from 6 to 9 in my run_wrf file. I did not make any further changes to the domain dimensions to get it to run.
  8. M

    (RESOLVED) WRF crashes with "forrtl: severe (174): SIGSEGV, segmentation fault occurred"

    Hi all, I am attempting to run WRF with a 12 km parent domain and 4 km nested domain. I recently increased the size of my 4 km nested domain and adjusted its location inside the parent domain and I'm now having issues while running wrf.exe. When I run wrf.exe, WRF only outputs one file for...
Top