Home

Context Navigation

chapter_3.0.html @ 765

Last change on this file since 765 was 97, checked in by raasch, 17 years ago

New:
---
ocean version including prognostic equation for salinity and equation of state for seawater. Routine buoyancy can be used with both temperature and density.
+ inipar-parameters bc_sa_t, bottom_salinityflux, ocean, sa_surface, sa_vertical_gradient, sa_vertical_gradient_level, top_salinityflux

advec_s_bc, average_3d_data, boundary_conds, buoyancy, check_parameters, data_output_2d, data_output_3d, diffusion_e, flow_statistics, header, init_grid, init_3d_model, modules, netcdf, parin, production_e, prognostic_equations, read_var_list, sum_up_3d_data, swap_timelevel, time_integration, user_interface, write_var_list, write_3d_binary

New:
eqn_state_seawater, init_ocean

Changed:

inipar-parameter use_pt_reference renamed use_reference

hydro_press renamed hyp, routine calc_mean_pt_profile renamed calc_mean_profile

format adjustments for the ocean version (run_control)

advec_particles, buoyancy, calc_liquid_water_content, check_parameters, diffusion_e, diffusivities, header, init_cloud_physics, modules, production_e, prognostic_equations, run_control

Errors:

Bugfix: height above topography instead of height above level k=0 is used for calculating the mixing length (diffusion_e and diffusivities).

Bugfix: error in boundary condition for TKE removed (advec_s_bc)

advec_s_bc, diffusion_e, prognostic_equations

Property svn:keywords set to Id

File size: 5.4 KB

Rev	Line
[5]	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
[62]	2	<html><head>
[97]	3	<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 3.0</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Marcus Oliver Letzel"> <meta name="CREATED" content="20040723;15213734"> <meta name="CHANGED" content="20041112;13170538"> <meta name="KEYWORDS" content="parallel LES model"> <style>
[62]	4	<!--
	5	@page { size: 21cm 29.7cm }
	6	-->
	7	</style></head>
	8	<body style="direction: ltr;" lang="en-US"><h2 style="font-style: normal; line-height: 100%;"><font size="4">3.0
[5]	9	Execution of model runs</font></h2>
	10	<p style="line-height: 100%;">Given that the model was
	11	installed by the user (look at <a href="chapter_5.0.html">chapter
[62]	12	5.0</a>) and that it is clear, which phenomenon is to be
	13	simulated,
[5]	14	there is a whole set of questions which must be answered before
	15	executing
	16	the actual application run, e.g.: </p>
[62]	17	<ul> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
[5]	18	large does the model domain have to be and what grid size does
[62]	19	phenomenon to be simulated require? </p> </li> <li>
	20	<p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
[5]	21	long is the time which should be simulated, i.e. which typical time
[62]	22	scale does the phenomenon have? </p> </li> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which
[5]	23	boundary conditions and initial conditions are to be selected? </p>
[62]	24	</li> <li> <p style="font-style: normal; line-height: 100%;">Which model
[5]	25	output data are necessary at which points in time, in order to be able
[62]	26	to analyze the phenomenon afterwards? </p> </li>
	27	</ul><p style="line-height: 100%;">The answers to
	28	these questions
[5]	29	substantially determine the choice of values for the most important
	30	model parameters, with which the model run is steered. All possible
	31	parameters are described in chapters <a href="chapter_4.1.html">4.1</a>,
	32	<a href="chapter_4.2.html">4.2</a>
	33	and <a href="chapter_4.3.html">4.3</a>.
	34	The basic steering of the model with these parameters is explained in
	35	the introduction to <a href="chapter_4.0.html">chapter
[62]	36	4</a>. The user will rarely use all model parameters, since many
	37	are
[5]	38	preset with consistent default values and therefore do not have to be
	39	changed by the user. Some of the most important parameters are not
	40	preset with default values and must be adjusted by the user in each
[97]	41	case. Such a typical, minimum parameter set is described in <a href="chapter_4.4.1.html">chapter
	42	4.4.1</a>. For the subsequent analysis of model runs, graphical
[62]	43	visualization of model data is particularly important. <a href="chapter_4.5.html">Chapter
[5]	44	4.5</a> describes, how such outputs are produced with the model. </p>
[62]	45	<p style="line-height: 100%;">The selected parameters and
	46	their values
[5]	47	have to be supplied to the model as an input file. The
[62]	48	structure of this file is described in the introduction to <a href="chapter_4.0.html">chapter
	49	4</a>. The data, produced by the model, are located in a number
	50	of
[5]	51	different output files. The model works with relative file names
	52	(i.e. without absolute path information). Thus all input and output
	53	files are
	54	expected and put in the directory, in which the actual model (the
	55	executable program created from the FORTRAN source code) is started
	56	(but also see next paragraph).
[62]	57	All user-relevant input and output files are described in <a href="chapter_3.4.html">chapter
[5]	58	3.4</a>. </p>
[62]	59	<p style="line-height: 100%;">The actual model (the
	60	executable
[5]	61	program) is not started directly via the user, but with the help of
[62]	62	the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which
[5]	63	can be called by the user. This script takes over the entire pre- and
	64	postprocessing work, which is necessary for a model run. In addition
	65	to this, it generates e.g. automatically batch jobs for model runs on
	66	remote computers, provides for the appropriate file transfers of the
	67	input and output files to these computers, secures data on existing
	68	archives systems, starts if necessary restart jobs, and much more.
[62]	69	<span style="font-weight: bold;">mrun</span> allows
	70	to specify
[5]	71	individual path names for each simulation and
	72	for the different types of input/output files. The start of model runs
	73	with <b>mrun</b> is described in <a href="chapter_3.1.html">chapter
	74	3.1</a>. </p>
[62]	75	<p style="line-height: 100%;">The implementation of user
	76	code
[5]	77	extensions in
	78	the model is made possible by a set of defined interfaces. You will
[62]	79	find references to the programming of such extensions in <a href="chapter_3.5.html">chapter
	80	3.5</a>. Frequently errors arise during the execution of the
	81	model
[5]	82	after such changes, which can often be found only by interactive
	83	model steering and error tracing (debugging), which are described in
	84	<a href="chapter_3.6.html">chapter
	85	3.6</a>. </p>
[62]	86	<hr><p style="font-style: normal; line-height: 100%;"><br>
	87	<font color="#000080"><font color="#000080"><a href="chapter_2.0.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.1.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
	88	</p><p style="font-style: normal; line-height: 100%;"><span style="font-style: italic;">Last change:</span>
	89	$Id: chapter_3.0.html 97 2007-06-21 08:23:15Z raasch $<br>
	90	</p></body></html>

Note: See TracBrowser for help on using the repository browser.

Context Navigation

source: palm/trunk/DOC/app/chapter_3.0.html @ 765

Download in other formats: