BlueM.Opt output files: Difference between revisions
(translation) |
(update for BlueM.Opt v2.1.0) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
<div style="float:right; margin:0 0 5px 5px;">__TOC__</div> | <div style="float:right; margin:0 0 5px 5px;">__TOC__</div> | ||
==Result database== | ==Result database== | ||
The result database is a Microsoft Access database containing the fitness values ("'''QWerte'''"), the constraint values ("'''Constraints'''") | The result database is a Microsoft Access database containing the fitness values ("'''QWerte'''"), the constraint values ("'''Constraints'''") and the optimization parameterts ("'''OptParameter'''") of each simulation carried out during the optimization process. | ||
The result database is stored in the directory containing the dataset with following filename: <br/> | |||
<code> | <code><datasetname>.BlueM.Opt.<timestamp>.mdb</code><br/> | ||
where<br/> | |||
:<code><datasetname></code> is the name of the dataset | |||
:<code><timestamp></code> is the timestamp when the optimization was started in format YYYYMMddHHmm | |||
=== Loading === | === Loading === | ||
You can load an existing result database for the | You can load an existing result database for the purposes of visualizing and analyzing the results. | ||
# Set ''App'', ''Dataset'' and ''Method''. These have to correspond to the settings used to produce the 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'' | # Click on ''Result - load result DB'' | ||
It is currently not possible to continue an optimization run using a loaded result database as the starting point. | |||
=== Structure === | === Structure === | ||
| Line 24: | Line 24: | ||
* '''Constraints''': Constraint values | * '''Constraints''': Constraint values | ||
* '''SekPop''': The pareto-front at each generation. | * '''SekPop''': The pareto-front at each generation. | ||
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>. | ||
Latest revision as of 02:57, 24 January 2023
BlueM.Opt | Download | Usage | Development
Result database
The result database is a Microsoft Access database containing the fitness values ("QWerte"), the constraint values ("Constraints") and the optimization parameterts ("OptParameter") of each simulation carried out during the optimization process.
The result database is stored in the directory containing the dataset with following filename:
<datasetname>.BlueM.Opt.<timestamp>.mdb
where
<datasetname>is the name of the dataset<timestamp>is the timestamp when the optimization was started in format YYYYMMddHHmm
Loading
You can load an existing result database for the purposes of visualizing and analyzing the results.
- Set App, Dataset and Method. These have to correspond to the settings used to produce the result database.
- Click on Result - load result DB
It is currently not possible to continue an optimization run using a loaded result database as the starting point.
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.
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!