Recent content by cross

Hi Demian, As you are modeling over complex terrain you should set w_damping = 1 and increase the epssm value (try to not go over 0.7). I usually run models over the Andes up to 1km and those are the best option to check after the time step (I think 1 is too low if you are running a 15km...

I tried to do that, but it didn't work. I was using SMS-3DTKE, so I changed it for the Shin-Hong scheme and worked, now it's running more stable.

Yes, is over the Andes. My problem is not getting CFL errors, I have to deal with that in this area, but the problem was I wasn't getting an error message and the process was still running. I compiled WRF with intel compiler + OpenMPI, and now I get an error message. So, I think I might be...

I've made some tests. And the problem seems to be the intel compiler or intel MPI. At the same time it freezes, I get CFL error using gcc and OpenMPI

In my case, I use different parameters. But the best options to avoid the cfl errors, I think would be changing to mp_physics=3 and some brute force way would be increasing the epssm value.

First try turning on w_damping and if it doesn't work, change the time_step.

Try setting the HDF5 library paths like this before configure: and then check that HDF5 is correctly linked in configure.wrf I think these are all the references in the file:

io_form_history = 2 io_form_restart = 2 io_form_input = 2 io_form_boundary = 2 io_form_auxinput1 = 2 io_form_auxhist2 = 2 debug level = 0 / I think always...

I think that's a netcdf problem and not the intel compiler. Try compiling with classic data model from netCDF-3, without compression. If you want to use compression, build netcdf with hdf5 without activating parallel I/O.

It has happened in two different computers, using WRF 4.3.3 and 4.4. Now I will start running a new model, if it freezes again I'll upload the namelist.input. The rsl files just stop writing, doesn't show any error. I thought it could be some memory or disk errors, but seems that everything...

I've been having random errors where WRF process keeps running, but it doesn't write the output data (wrfout, wrfrst, rsl). The only way to fix it is to change the timestep or change the microphysics parametrization (ie. from 6 to 3). This happens randomly, different servers, different...

Yes, it's also set auto_levels_opt = 2

Thanks! that's what I was thinking about the SMS-3DTKE scheme. I'll do some tests to check the different options.

Those eta levels are the calculated by wrf, I didn't specify it in the input file. I have it configured like this: e_vert = 44, 44, 44, 44, p_top_requested = 5000, num_metgrid_levels = 38, num_metgrid_soil_levels = 4, dx...

I want to set up a model over a complex terrain at high altitude (between 3000m and 5000m). The main problem here is that sometimes the surface wind field is forced by the model to make a wind direction daily cycle, instead of one steady direction (mainly from the north). So, I most of the time...