Step 1: Necessary Setup Files 6 files need to be prepared in the following manner The examples show a forest with only 4 MUs external_init.txt - 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 Each of these External IDs have an Internal ID which corresponds to the index of their row starting from 0 -----------------EXAMPLE: 1 2 3 4 ------------------------- So they have the following Internal IDs ---------------- 0 1 2 3 ---------------- area_init.txt - This file sets up the area of each MU. -----------------Example: 42.6017806736 8.26386417601 6.03153252031 26.9439445316 ------------------------ adj_init.txt - 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 -----------------Example: 1,2 0 0,1 -1 ------------------------ FAZER DESENHO AQUI border_init.txt - 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 -----------------Example: 259,151 490 102,653 -1 ------------------------ ugs_init.txt - This file sets up the Prescriptions associated with each MU, each line should list the IDs of the Prescriptions associated with each MU -----------------Example: 1,2,3 19 19,20,21 500,501,502,503,500600,500601 ------------------------ years_init.txt - This file sets up the relation between Prescriptions and the years where those Prescriptions have Harvest actions. 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 Before listing the years the line should have the Internal ID of the MU followed by a "|" -----------------Example: 0|2026,2056,2066/2027,2049,2060/2028,2040,2052,2064 1|2022,2032,2042 2|2026,2046/2060/-1 3|2052/2057/-1/2067/2052/2052 ------------------------ Step 2: Criteria Files There can be a maximum of 10 optimizable criteria in the program represented by these files, these files are crit_file0-10.txt and their format is the same. Each line corresponds to an MU similarly to previous files and the contents are separated by commas, the contents are the values of the objective criteria associated with each Prescription of the respective MU -----------------Example: 34,30.99,3.363 1568.630 565.79,146,1692 4966,6310,7,87,49,496 ------------------------ Step 1: Necessary Setup Files 6 files need to be prepared in the following manner The examples show a forest with only 4 MUs external_init.txt - 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 Each of these External IDs have an Internal ID which corresponds to the index of their row starting from 0 -----------------EXAMPLE: 1 2 3 4 ------------------------- So they have the following Internal IDs ---------------- 0 1 2 3 ---------------- area_init.txt - This file sets up the area of each MU. -----------------Example: 42.6017806736 8.26386417601 6.03153252031 26.9439445316 ------------------------ adj_init.txt - 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 -----------------Example: 1,2 0 0,1 -1 ------------------------ FAZER DESENHO AQUI border_init.txt - 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 -----------------Example: 259,151 490 102,653 -1 ------------------------ ugs_init.txt - This file sets up the Prescriptions associated with each MU, each line should list the IDs of the Prescriptions associated with each MU -----------------Example: 1,2,3 19 19,20,21 500,501,502,503,500600,500601 ------------------------ years_init.txt - This file sets up the relation between Prescriptions and the years where those Prescriptions have Harvest actions. 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 Before listing the years the line should have the Internal ID of the MU followed by a "|" -----------------Example: 0|2026,2056,2066/2027,2049,2060/2028,2040,2052,2064 1|2022,2032,2042 2|2026,2046/2060/-1 3|2052/2057/-1/2067/2052/2052 ------------------------ Step 2: Criteria Files There can be a maximum of 10 optimizable criteria in the program represented by these files, these files are crit_file0-10.txt and their format is the same. Each line corresponds to an MU similarly to previous files and the contents are separated by commas, the contents are the values of the objective criteria associated with each Prescription of the respective MU -----------------Example: 34,30.99,3.363 1568.630 565.79,146,1692 4966,6310,7,87,49,496 ------------------------