Defining stratum state variables from LAI (lairead) - Revision history

Jchoate at 04:27, 13 February 2012

2012-02-13T04:27:50Z

Jchoate at 04:27, 13 February 2012

2012-02-13T04:27:24Z

Jchoate at 04:24, 13 February 2012

2012-02-13T04:24:55Z

Jchoate at 04:23, 13 February 2012

2012-02-13T04:23:50Z

Jchoate at 04:23, 13 February 2012

2012-02-13T04:23:03Z

Jchoate at 04:22, 13 February 2012

2012-02-13T04:22:27Z

Jchoate at 04:21, 13 February 2012

2012-02-13T04:21:20Z

Jchoate at 04:20, 13 February 2012

2012-02-13T04:20:21Z

Jchoate at 04:18, 13 February 2012

2012-02-13T04:18:54Z

Jchoate at 04:16, 13 February 2012

2012-02-13T04:16:29Z

@@ Line 80: / Line 80: @@
      0     0        0          0       0          0      0        0      0
      1     1.83     0.0141     1.5     0.7071     40     82.4     50     333.3333333
     1     1.83     0.0141     1.5     0.7071     40     82.4     50     333.3333333

@@ Line 75: / Line 75: @@
 The resultant file ‘allometric.txt’ will look something like this:
-       0       0       0       0       0       0       0       0       0
+    0     0        0          0       0          0      0        0      0
-       0       0       0       0       0       0       0       0       0
+    1     1.83     0.0141     1.5     0.7071     40     82.4     50     333.3333333
+    1     1.83     0.0141     1.5     0.7071     40     82.4     50     333.3333333
-      1       1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333

@@ Line 75: / Line 75: @@
 The resultant file ‘allometric.txt’ will look something like this:
--6
--0       0       0       0       0       0       0       0       0       0
+       0       0       0       0       0       0       0       0       0
--1       0       0       0       0       0       0       0       0       0
+       0       0       0       0       0       0       0       0       0
--2       0       0       0       0       0       0       0       0       0
+       0       0       0       0       0       0       0       0       0
--4       1       1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
+       1       1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
--25      17    1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
+      17    1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
--27      0       0       0       0       0       0       0       0       0
+      0       0       0       0       0       0       0       0       0
-           hill
-           patch
+     1     1.83     0.0141
            zone
            vegid

@@ Line 89: / Line 89: @@
 -27      0       0       0       0       0       0       0       0       0
- - hill
+          hill
-        - patch
+          patch
-        - zone
+          zone
-        - vegid
+          vegid
-        - lai
+          lai

← Older revision		Revision as of 04:23, 13 February 2012
Line 88:		Line 88:

	-27 0 0 0 0 0 0 0 0 0		-27 0 0 0 0 0 0 0 0 0
		+
		+	- hill
		+	- patch
		+	- zone
		+	- vegid
		+	- lai

← Older revision		Revision as of 04:21, 13 February 2012
Line 100:		Line 100:

	lairead -pre (prefix of images) -old existing_worldfile -redef new_redefine_worldfile -allom allometric.txt		lairead -pre (prefix of images) -old existing_worldfile -redef new_redefine_worldfile -allom allometric.txt
		+
		+	(command line example)

	U> lairead -pre ws -old world.example –redef world.example.Y2000M10D2H1		U> lairead -pre ws -old world.example –redef world.example.Y2000M10D2H1

@@ Line 99: / Line 99: @@
 (Format)
-lairead   -pre (prefix of images)   -old  existing_worldfile
+lairead   -pre (prefix of images)   -old  existing_worldfile -redef  new_redefine_worldfile   -allom  allometric.txt
 U> lairead  -pre ws  -old world.example  –redef world.example.Y2000M10D2H1

@@ Line 48: / Line 48: @@
 Each of the successive rows in the allometric text file (a row for each vegetation entry) will include 10 values – one value for each of the above entries for each vegetation type.  While you will include a value for each entry, you will not include the headings in the allometric text file.
 Column definitions:
 . vegetation ID – the stratum_default_ID in the vegetation definition file
 . sla – specific leaf area, found in the vegetation definition file
 Columns 3-6 are defined by allometric relationships and are DIFFERENT than what is in the vegetation definition file - which specifies NEW carbon allocation, while the lairead program requires values for the existing carbon allocation on a fully formed tree:
 . leaf:root  - allometric relationship found in literature, assume if cannot find another value
 . leaf:stem  - allometric relationship, varies by type, important to get from literature if possible
 . stem:coarseroot – allometric relationship found in literature
 . livestem:deadstem – allometric relationship found in literature
 Columns 7-10 reflect C:N ratio values; these you can base on the values in the veg def file:
 . cn_leaf - carbon to nitrogen ratio
 . cn_froot - carbon to nitrogen ratio
 . cn_livewood - carbon to nitrogen ratio
 . cn_deadwood - carbon to nitrogen ratio (same value can be for all veg types (333.333))
 The resultant file ‘allometric.txt’ will look something like this:
        0       0       0       0       0       0       0       0       0
        0       0       0       0       0       0       0       0       0
        0       0       0       0       0       0       0       0       0
        1       1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
       17    1.83    0.0141  1.5     0.7071  40      82.4    50      333.3333333
       0       0       0       0       0       0       0       0       0
 III. You must have an existing worldfile (it can have values for the stratum state variables or they can all be 0, it doesn't matter as these will change after using lairead)
@@ Line 76: / Line 96: @@
 IV. Call the lairead program:
 (Format)
 lairead   -pre (prefix of images)   -old  existing_worldfile
   -redef  new_redefine_worldfile   -allom  allometric.txt
 U> lairead  -pre ws  -old world.example  –redef world.example.Y2000M10D2H1
 -allom  allometric.txt
 This will give you a new redefine worldfile with the name you specified on the -redef option on the lairead command line.  This is a redefinition worldfile and will not have a header.  If you open it up, you should see the value of -9999 for all state variables except those under stratum.  Under the stratum level should be the new values based on the info you put into the allometric table. (The redefinition worldfile will contain the same name as the existing worldfile being changed, followed by a date extension designating the day the redefine will occur.)
 V. Use the redefinition worldfile in a very short simulation in order to incorporate the new redefinition stratum values into the existing worldfile you want to change.
 . Make sure both the worldfile you want to change and the redefinition worldfile have the same name, but the redefinition worldfile will also include a date extension on it, i.e.:
 world.example
 world.example.Y2000M10D2H1
 (format for the date extension is Year, Month, Day, Hour)
@@ Line 93: / Line 120: @@
 Example file - tec.redef:
 10 2 1 redefine_world
 10 3 1 output_current_state
 . Run RHESSys to redefine the ‘world’ using the worldfile you want to change (i.e. world.example) and the tecfile with the redefinition command (tec.redef) in the RHESSys command line.  Regarding the command line start and end dates of the simulation, recommend simply starting/running the simulation for the first day, redefining the world on the second day, then output the new worldfile on the third day, and end the simulation on the fourth day. That way all processes that update only once in a 24-hour period are able to complete, i.e. (on the command line):
 -st 2000 10 1 1
 -ed 2000 10 4 1
@@ Line 103: / Line 134: @@
 As a result, you will get a new worldfile including a date extension that matches the output_current_state event date in the TEC file (the third day of simulation), i.e.:
 world.example.Y2000M10D3H1 - this is the worldfile that you use to start subsequent spin up’s or simulations.  Just change the name of this new worldfile so you don't have the cumbersome date extension included in the name (i.e. world.lairead).
 (Note: this process will assign the stratum state variable in each patch/stratum across the landscape the same associated value (i.e. cs_leafc, etc… will be assigned the same value for every patch/stratum); therefore, recommend running at least a few years of ‘spin up’ with this new worldfile to allow the vegetation to adjust spatially in response to its’ environment).

@@ Line 25: / Line 25: @@
 The subsequent rows will consist of ten columns for the following items:
 ) vegetation id
 ) SLA