Eduardo Eloy / modfire

Download as
Browse Code ยป

Commit c089aa543a23b8649f803329fd3b0dd609330f44

Authored by Eduardo Eloy
1 parent 9c830dc4
Exists in Standardized

fixed readme

Showing 1 changed file with 6 additions and 6 deletions   Show diff stats
README.md
  Diff comments   View file @c089aa5
... ... @@ -23,7 +23,7 @@ In general for every line in one of the files we assume a new Management Unit, a
23 23  
24 24  
25 25 ## external_init.txt
26   -###- This file serves to indicate how many Management Units exist in the forest, so each line should have a number to serve as an External identifier of each MU. There should be as many lines as there are MUs in the forest
  26 +### This file serves to indicate how many Management Units exist in the forest, so each line should have a number to serve as an External identifier of each MU. There should be as many lines as there are MUs in the forest
27 27  
28 28 Each of these External IDs have an Internal ID which corresponds to the index of their row starting from 0
29 29 -----------------EXAMPLE:
... ... @@ -43,7 +43,7 @@ So they have the following Internal IDs
43 43  
44 44  
45 45 ## area_init.txt
46   -###- This file sets up the area of each MU.
  46 +### This file sets up the area of each MU.
47 47  
48 48 -----------------Example:
49 49 42.60178
... ... @@ -53,7 +53,7 @@ So they have the following Internal IDs
53 53 ------------------------
54 54  
55 55 ## adj_init.txt
56   -###- This file sets up the adjacencies of each MU each line should list the Internal IDs of the MUs adjacent to the respective MU separated by a comma. If the MU has no adjacent MUs the line should just have a -1
  56 +### This file sets up the adjacencies of each MU each line should list the Internal IDs of the MUs adjacent to the respective MU separated by a comma. If the MU has no adjacent MUs the line should just have a -1
57 57  
58 58 -----------------Example:
59 59 1,2
... ... @@ -69,7 +69,7 @@ Internal Ids: External Ids:
69 69  
70 70  
71 71 ##border_init.txt
72   -###- This file sets up the lenght of the border of each adjacent MU, each line should list the lenght of the borders of each adjacency separated by a comma. If the MU has no adjacent MUs the should just have a -1
  72 +### This file sets up the lenght of the border of each adjacent MU, each line should list the lenght of the borders of each adjacency separated by a comma. If the MU has no adjacent MUs the should just have a -1
73 73  
74 74 -----------------Example:
75 75 259,151
... ... @@ -82,7 +82,7 @@ If borders aren't a factor is your data just put use 0s in place of real border
82 82  
83 83  
84 84 ##ugs_init.txt
85   -###- This file sets up the Prescriptions associated with each MU, each line should list the IDs of the Prescriptions associated with each MU
  85 +### This file sets up the Prescriptions associated with each MU, each line should list the IDs of the Prescriptions associated with each MU
86 86  
87 87 -----------------Example:
88 88 1,2,3
... ... @@ -92,7 +92,7 @@ If borders aren't a factor is your data just put use 0s in place of real border
92 92 ------------------------
93 93  
94 94 ##years_init.txt
95   -###- This file sets up the relation between Prescriptions and the years where those Prescriptions have Harvest actions.
  95 +### This file sets up the relation between Prescriptions and the years where those Prescriptions have Harvest actions.
96 96 ### Each line lists the years where the corresponding Prescription has Harvest actions separated by commas, if the MU has more than one Prescription then a "/" is followed by the next Prescription's harvest years. If a Prescription has no years of Harvest there should be a -1
97 97  
98 98 Before listing the years the line should have the Internal ID of the MU followed by a "|"
... ...