Search results

  1. H

    Upper limit recommendation for the grid spacing of the coarsest domain

    Thanks for the valuable information. Regards
  2. H

    Upper limit recommendation for the grid spacing of the coarsest domain

    Yes, thanks for taking the time to explain. I understand how nesting and grid spacing works, but that wording in the first post confused me. Now it's OK :) So, this brings us to my main question in the title. How coarse can the outermost domain be? Is there some point after which increasing the...
  3. H

    Upper limit recommendation for the grid spacing of the coarsest domain

    Dear kwerner, Thanks for the answer. "5x the resolution" is vague for me, I can't be sure if it means a coarser or finer resolution. What I understand is this: d01 (the outermost coarsest domain) can't be too fine, it should be coarse enough to satisfy . So if the meteorological input grid...
  4. H

    Upper limit recommendation for the grid spacing of the coarsest domain

    In the best practices guide for WPS (link), it states that "It's best to keep the ratio of input data resolution to the coarsest grid resolution (on your domain) to no more than 1:10". So, my questions are: This imposes a lower limit for the grid spacing of the coarsest domain, in other words...
  5. H

    An easy way of checking the heights of eta levels

    Thanks Dr. Chen.
  6. H

    An easy way of checking the heights of eta levels

    Hi, If I don't define e_vert in the namelist.input, I can check the generated eta levels and their height, thickness information in the real log file rsl.out.0000 as such: using new automatic levels program 1 50.0000000 50.0000000 0.993814707 2 64.0000000...
  7. H

    Setting a time to start writing history files from

    Hi, I've already checked the NAMELIST.INPUT options but could not find a variable that controls the start/end date of the history files per se. I've thought that stopping the simulation at a specific time and restarting with history writing enabled might be a workaround. But again, I might be...
  8. H

    Setting a time to start writing history files from

    Hi, Is it possible to set a starting time for writing history files? For example, for a total of 24-hour long simulation, I'm only interested in the hours between 18-22. My goal is to save disk space. Thanks in advance
  9. H

    Unrealistic (?) PBLH results

    Dr. Chen, Upon your suggestion, I've installed WRF v4.4. I've basically treated the outer 2 and inner 2 domains separately in terms of the PBL settings. Following is the latest version of my namelist.input file with comments: &physics mp_physics = 4 , 4 , 4 , 4...
  10. H

    Unrealistic (?) PBLH results

    Dr. Chen, Thanks for your reply. (1) I've changed the time_step = 90 (2 and 3) I've omitted the physics_suite option entirely and entered the relevant parameters manually as you have suggested (please see it towards the end of this post). However: Setting km_opt = 5 returned an error since I...
  11. H

    Unrealistic (?) PBLH results

    Hello again, I've tried not defining the vertical levels (eta_levels) and letting WRF decide the levels. However, this also did not help much. If I'm making a very basic mistake in the namelist files, I'm not sure what it is. The settings which are relevant to PBL I've found are: &physics...
  12. H

    Unrealistic (?) PBLH results

    Dr. Ming Chen, The plots are for the innermost (finest) domain, i.e. d04. I've attached the namelist.wps and namelist.input files. By the way, those planes are not on the boundary of d04, they lie within the d04 domain. Such as:
  13. H

    Unrealistic (?) PBLH results

    Hi, As far as I know, PBL height is expected to be between 100-2000 m, roughly. However, I'm getting PBLH as low as ~5m. Moreover, when I interpolate the fields on vertical plane cuts, the pblh distribution seems to be quite erratic along neighboring planes: it varies from 5 to 800 meters...
  14. H

    Vertical Levels Adjustment

    Hi, I'm also in a similar situation (studying wind turbines below 200m). Mr. Ming Chen, you suggest running REAL first to create eta levels, which to my understanding, is required to get the minimum eta level (0.88 in your example) that is dictated by the p_top_requested variable, and the...
  15. H

    Required simulation time to get PBL results

    Mr. Ming Chen, Thanks for your input. I was expecting that it would depend on the length and time scales of the simulation, but starting with 6-9 hours and validating is indeed a good idea. Thanks!
  16. H

    Time output is written only to rsl.error.0000 and rsl.out.0000 log files in a parallel run

    Hi, I'm running real.exe and wrf.exe parallel on 20 cores. The time output (that is, the lines which look like: ... Timing for main: time 2021-11-14_00:57:52 on domain 4: 0.69735 elapsed seconds Timing for main: time 2021-11-14_00:57:52 on domain 4: 0.70016 elapsed seconds Timing for...
  17. H

    Required simulation time to get PBL results

    Hello, I'm interested in obtaining PBL (planetary boundary layer) related data; mainly the distribution of PBL height and vertical velocity profile with time. In terms of time and length scales: I'm after the velocity profiles in the first 150-200 meters for a timespan of ~ 1 hour over a 5km x...
  18. H

    (RESOLVED) Coordinate system (datum) compatibility between GFS/WPS/WRF/other sources

    Dear kwerner, Thanks for your reply. This makes everything clearer. By the way, I've run some pre/postprocessing tests using USGS EarthExplorer data and everything seems to be working in harmony so far. Regards
Top