Changes between Version 8 and Version 9 of Branches/Driver_Atm_Lev

Timestamp:

2012-06-01T16:10:03+02:00 (12 years ago)

Author:

jpolcher

Comment:

--

Branches/Driver_Atm_Lev

@@ -6 +6 @@
 == Current situation ==
 
-The driver reads the height of the atmospheric forcing variables (Temperature, humidity and wind) from the run.def. These are the variables '''HEIGHT_LEV1''' (for T and Q) and '''HEIGHT_LEVW''' (for wind). This is done in routine forcing_grid from file readdim2.f90.
+The driver reads the height of the atmospheric forcing variables (Temperature, humidity and wind) from the run.def. These are the variables '''HEIGHT_LEV1''' (for T and Q) and '''HEIGHT_LEVW''' (for wind). This is done in routine forcing_grid in file readdim2.f90.
 
 The scalar values obtained are then copied onto the global gird (i.e. iim x jjm in size).
@@ -20 +20 @@
   1. We impose the same value for the heigh of the atmospheric forcing variables to all points of the globe (except in the case of WATCHOUT).
 
-  2. As the height of the forcing variable is in the run.def the user can change forcing data and forget to provide the changed height of the variables. This can only be solved if the height of the forcing data is in the file containing the data itself.
+  2. As the height of the forcing variable is in the run.def the user can change forcing data and forget to provide the new height of the variables. This can only be solved if the height of the forcing data is in the file containing the data itself.
 
   3. The height of the variables cannot change over time. But this is the case if the atmospheric variable come from a model which uses some type of pressure coordinate.