Changes between Version 7 and Version 8 of doc/tut/examples/2012_maronga_LITFASS2003
- Timestamp:
- Oct 23, 2012 1:16:07 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/tut/examples/2012_maronga_LITFASS2003
v7 v8 2 2 3 3 === Purpose === 4 This example shows the development of the convective boundary layer in the LITFASS region on May 30, 2003. The example was generated in the course of the LITFASS-2003 project ([wiki:imuk/projects/2009_03 details]). 4 This example shows the development of the convective boundary layer in the LITFASS region on May 30, 2003. The example was generated in the course of the LITFASS-2003 project ([wiki:imuk/projects/2009_03 details]). The LITFASS area is heterogeneous and includes forest area as well as agricultural regions, grassland and lakes. Each land use has its own characteristics concerning temperature, humidity, roughness and surface fluxes. The developing boundary-layer shows signals of this heterogeneity all day long. The simulation starts in the early morning, when no turbulence is present (05 UTC) and ends with the evening transition (17 UTC). Results from this simulation were published in Maronga and Raasch (2012). 5 5 6 === Contact person(s) === 6 7 === Contact person(s) and References === 7 8 [[imuk/members/maronga|Maronga, Björn]], [[imuk/members/suehring|Sühring, Matthias]] 9 10 * ''' ''Maronga, B.'' and ''S. Raasch'', 2012: '''Large-Eddy Simulations of Surface Heterogeneity Effects on the Convective Boundary Layer During the LITFASS-2003 Experiment. ''Boundary-Layer Meteorol.'', doi: [http://dx.doi.org/10.1007/s10546-012-9748-z 10.1007/s10546-012-9748-z] \\ 11 8 12 9 13 === PALM version === … … 22 26 === Model run === 23 27 The basic command is\\\\ 24 {{{mrun -d LITFASS-2003 -r "d3# ts# pr# xy# 3d# restart" -T 8 -t 10800 -X 64}}}\\\\28 {{{mrun -d LITFASS-2003 -r "d3# ts# pr# xy# 3d# restart" -T 8 -t 10800 -X 64}}}\\\\ 25 29 Please set other options, such as {{{-h}}}, {{{-K}}}, and {{{-q}}} according to your needs. Note that this example will require 64 processors for at least two hours. If you want to carry out this job with less processors, please adjust the parameter file. You can also carry out restarts. 26 30