11-28-2014, 02:24 PM
Hi Kostas, Navid, sorry for coming in late ...
The pre-calculated result option is for demonstrating how optimisation works only. Everything in the table will be plotted as the gray cloud in the background, so you can see the whole search space and how the algorithm explores the solutions.
The format of the result table is like this:
- the first row (headers) is ignored
- column 1 is index of the rows
- column 2 is the job ids. These are jEPlus+EA job ids, which are slightly different to the jEPlus's. It starts with the project initial which is set in the .jep file. The rest part is indexes of the parameter values used in each case, separated by an underscore ('_'). Note that first index is for the IDF model. Weather file cannot be a design variable so it is not represented here. In the ET_PreCalc example, you see 11 digits in the job ids, representing the IDF model and the 10 jEPlus parameters.
- column 3 is ignored
- columns 4, 5 ... are objective function values, coming from the full parametric run or other sources.
Hope this will make it a bit clearer.
By the way, Kostas, why do you want to use this function?
Cheers,
Yi
The pre-calculated result option is for demonstrating how optimisation works only. Everything in the table will be plotted as the gray cloud in the background, so you can see the whole search space and how the algorithm explores the solutions.
The format of the result table is like this:
- the first row (headers) is ignored
- column 1 is index of the rows
- column 2 is the job ids. These are jEPlus+EA job ids, which are slightly different to the jEPlus's. It starts with the project initial which is set in the .jep file. The rest part is indexes of the parameter values used in each case, separated by an underscore ('_'). Note that first index is for the IDF model. Weather file cannot be a design variable so it is not represented here. In the ET_PreCalc example, you see 11 digits in the job ids, representing the IDF model and the 10 jEPlus parameters.
- column 3 is ignored
- columns 4, 5 ... are objective function values, coming from the full parametric run or other sources.
Hope this will make it a bit clearer.
By the way, Kostas, why do you want to use this function?
Cheers,
Yi
