Name Last Update
..
.idea Loading commit data...
Exports Loading commit data...
Mapas Loading commit data...
out Loading commit data...
res Loading commit data...
res_old Loading commit data...
src Loading commit data...
MODFIRE-Prototype.iml Loading commit data...
Makefile Loading commit data...
PaivaNSolution.csv Loading commit data...
PaivaSSolution.csv Loading commit data...
ParedesSolution.csv Loading commit data...
PenafielSolution.csv Loading commit data...
README.md Loading commit data...
choco-solver-4.10.5-jar-with-dependencies.jar Loading commit data...
create_map_file.py Loading commit data...
tudoMenosPenafielSolutioon.csv Loading commit data...

README.md

Input Files format

In general for every line in one of the files we assume a new Management Unit, a file with 10 lines would imply that there are 10 MUs, and since this has to be consistent then that means all 4 input files should have 10 lines.

ugs_init

In every line there is a list of integers separated by commas, each integer is a possible Prescription Value for the Management Unit the index of the line represents. So the integers on the first line of the file are the possible Prescription Value ids for the Management Unit with the internal id "1", and in the Constraint Variable array of the code (IntVar [ ] ugs) it is represented in the index 0 (1 - 1). The same goes for the rest of the files.

area_init

Every line contains a float value which represents the Area Value of the respective MU.

graph_init

Every line contains a list of integers (or a single integer) separated by commas which correspond to the internal Management Unit id of the MUs adjacent to the MU the line represents.

period_init

Every line contains lists of integers separated by commas. These lists themselves are separated by slashes. Every set of integers separated by the slashes correspond to a possible prescription value for the MU represented by the line. Therefore there should be as many of these sets of integers separated by slashes as there are Prescription Values in the "ugs_init" file.

These sets of integers and the possible prescription values share indexes, meaning that the first set of integers separated by commas in a line of the "period_init" file is related to the first prescription value in the "ugs_file" and so on.

The integers themselves then represent the years when, if this prescription values is applied, the MU will have Harvest Actions

For example with the following files

ugs_init

1,2,3

67

++++++++++++++

period_init

10,20/1,2/0

0

This means that the MU represented by the first line has 3 possible Prescriptions (1,2,3).

And that the first possible Prescription of this MU has a harvest action in the years 10, 20. The second possible one in the year 1, 2. And the third has no harvest actions (year 0)

The MU in the second line only has 1 possible prescription and that prescription has no harvest actions