You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
tslist
- Thread starter kermarrec
- Start date
Hi,
I am also a new WRF user.
From what I understood, tslist output some fields at the nearest grid point. This point is determined at the beginning of the simulation, you have the indices of the points in the first line of the file if I remember well.
You can search in the forum, some questions about tslist have been answered
The output frequency is directly your simulation time step. I don't think you can change that. You may then post-process to get a value every hour.
I am using your topics to mention a small limitation of tslists :
If using a parent and a nest with a vertical nesting (nest having more eta levels than parent), the number of levels output (max_ts_levels) is limited by the parent number of eta levels (e_vert), even in the nest.
Mathieu
I am also a new WRF user.
From what I understood, tslist output some fields at the nearest grid point. This point is determined at the beginning of the simulation, you have the indices of the points in the first line of the file if I remember well.
You can search in the forum, some questions about tslist have been answered
The output frequency is directly your simulation time step. I don't think you can change that. You may then post-process to get a value every hour.
I am using your topics to mention a small limitation of tslists :
If using a parent and a nest with a vertical nesting (nest having more eta levels than parent), the number of levels output (max_ts_levels) is limited by the parent number of eta levels (e_vert), even in the nest.
Mathieu
Hi again,
I share here a quick modification of the code to allow time series profiles to be computed on a different number of levels between nested domains.
In particular this is useful when using vertical nesting since max_ts_level is currently limited to e_vert(1)-1 which might be lower to e_vert(2)-1 for example.
Note that I modified the default value of max_ts_locs to -1 and automatically reset -1 values to e_vert(i)-1 for each domain in module_check_a_mundo.
Mathieu
I share here a quick modification of the code to allow time series profiles to be computed on a different number of levels between nested domains.
In particular this is useful when using vertical nesting since max_ts_level is currently limited to e_vert(1)-1 which might be lower to e_vert(2)-1 for example.
Note that I modified the default value of max_ts_locs to -1 and automatically reset -1 values to e_vert(i)-1 for each domain in module_check_a_mundo.
Mathieu