BlueM.Opt output files: Difference between revisions
m (Froehlich moved page BlueM.Opt Ausgabedateien to BlueM.Opt output files: translation) |
(translation) |
||
Line 1: | Line 1: | ||
{{BlueM.Opt_nav}} | {{BlueM.Opt_nav}} | ||
<div style="float:right; margin:0 0 5px 5px;">__TOC__</div> | <div style="float:right; margin:0 0 5px 5px;">__TOC__</div> | ||
== | ==Result database== | ||
The result database is a Microsoft Access database containing the fitness values ("'''QWerte'''"), the constraint values ("'''Constraints'''") und and the optimization parameterts ("'''OptParameter'''") of each simulation carried ouzt during the optimization process. | |||
By default, the result database is stored in the following location: <br/> | |||
<code>C:\ | <code>C:\Users\[USERNAME]\AppData\Local\Temp\EVO.mdb</code><br/> | ||
If the result database already exists, it is overwritten when starting a new optimization. | |||
=== | === Saving === | ||
To save the result database to a user-specified location, click on ''Result - Save result DB'' after the end of the optimization run or while the optimization is paused. | |||
=== | === Loading === | ||
You can load an existing result database for the purpose of visualizing and analyzing the results. It is currently not possible to continue an optimization run using a loaded result database. | |||
# Set ''App'', ''Dataset'' and ''Method''. These have to correspond to the settings used to produce the result database. | |||
# | # Click on ''Result - load result DB'' | ||
=== Structure === | === Structure === | ||
Line 22: | Line 20: | ||
The result database contains several tables: | The result database contains several tables: | ||
* '''Sim''': The simulations that were performed (IDs only) | * '''Sim''': The simulations that were performed (IDs only) | ||
* '''QWerte''': Objective | * '''QWerte''': Objective function values | ||
* '''OptParameter''': Optimization parameter values | * '''OptParameter''': Optimization parameter values | ||
* '''Constraints''': Constraint values | * '''Constraints''': Constraint values | ||
* '''SekPop''': The pareto-front at each generation. | * '''SekPop''': The pareto-front at each generation. | ||
* '''Pfad''': | * '''Pfad''': [[CES]] only | ||
All tables can be linked using the common column <code>'''Sim_ID'''</code>. | All tables can be linked using the common column <code>'''Sim_ID'''</code>. | ||
Line 35: | Line 33: | ||
e.g. '''OptimierungsErgebnis_PES (nur letzte SekPop)''' gives you the parameter values, objective function values, and constraint values for all members of the last computed pareto front (i.e. the final result). | e.g. '''OptimierungsErgebnis_PES (nur letzte SekPop)''' gives you the parameter values, objective function values, and constraint values for all members of the last computed pareto front (i.e. the final result). | ||
;Note: The result database does not contain the model parameter values as defined in the [[ | ;Note: The result database does not contain the model parameter values as defined in the [[MOD-file]]! | ||
[[ | [[Category:BlueM.Opt output files]] |
Revision as of 04:56, 22 January 2018
BlueM.Opt | Download | Usage | Development
Result database
The result database is a Microsoft Access database containing the fitness values ("QWerte"), the constraint values ("Constraints") und and the optimization parameterts ("OptParameter") of each simulation carried ouzt during the optimization process.
By default, the result database is stored in the following location:
C:\Users\[USERNAME]\AppData\Local\Temp\EVO.mdb
If the result database already exists, it is overwritten when starting a new optimization.
Saving
To save the result database to a user-specified location, click on Result - Save result DB after the end of the optimization run or while the optimization is paused.
Loading
You can load an existing result database for the purpose of visualizing and analyzing the results. It is currently not possible to continue an optimization run using a loaded result database.
- Set App, Dataset and Method. These have to correspond to the settings used to produce the result database.
- Click on Result - load result DB
Structure
The result database contains several tables:
- Sim: The simulations that were performed (IDs only)
- QWerte: Objective function values
- OptParameter: Optimization parameter values
- Constraints: Constraint values
- SekPop: The pareto-front at each generation.
- Pfad: CES only
All tables can be linked using the common column Sim_ID
.
Some queries are already predefined:
e.g. OptimierungsErgebnis_PES (nur letzte SekPop) gives you the parameter values, objective function values, and constraint values for all members of the last computed pareto front (i.e. the final result).
- Note
- The result database does not contain the model parameter values as defined in the MOD-file!