Changes between Version 7 and Version 8 of vamper_main

Timestamp:

08/19/14 20:37:38 (10 years ago)

Author:

dkitover

Comment:

Adding 3rd "issue"

vamper_main

@@ -28 +28 @@
 == Additional issues == 
 ''Note: some of these issues are covered when using the checklist supplied in the attached html file'' [[BR]] 
-1. Due to coupling evolution, there is a definition of the number of vertical layers in VAMPER that is called '''x_num''' in VAMPER (see __vamper/sources/parameters.f90__). The same parameter exists in LBM in ''i''LOVECLIM (see in __lbm/sources/comland.h__), but is not coherently passed through. Thus one needs to check manually if the two values are identical. An error message will occur during the compiling and/or experiment when the x_num values are not indentical.[[BR]]
+1. Due to coupling evolution, there is a definition of the number of vertical layers in VAMPER that is called '''x_num''' in VAMPER (see __vamper/sources/parameters.f90__). The same parameter exists in LBM in ''i''LOVECLIM (see in __lbm/sources/comland.h__), but is not coherently passed through. Thus one needs to check manually if the two values are identical. An error message will occur during the compiling and/or experiment when the x_num values are not identical.[[BR]]
 2. For a semi-coupled version (meaning only ''i''LC gives temps to VAMPER but VAMPER does not give any variable back), the htop=0 (approx. line 504 in __lbm/sources/landmodel0.f__) SHOULD NOT BE commented out. For full coupling this SHOULD BE commented out. [[BR]]
-This will likely change in future versions. 
+3. You must use the same frequency interval value in the VAMPER model ("rec_int" parameter in parameters.f90) as in the iLOVECLIM restart interval value, which is the -r option when starting a run. If not, an error message will occur at the beginning of the experiment letting you know these are not equal.
+
+These are temporary solutions which hopefully change in future (and improved) versions.
 
 == Controlling VAMPER parameters ==