BlueM.Opt output files: Difference between revisions

From BlueM
Jump to navigation Jump to search
(update for BlueM.Opt v2.1.0)
 
(2 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'''") und and the optimization parameterts ("'''OptParameter'''") of each simulation carried ouzt during the optimization process.  
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.  


By default, the result database is stored in the following location: <br/>
The result database is stored in the directory containing the dataset with following filename: <br/>
<code>C:\Users\[USERNAME]\AppData\Local\Temp\EVO.mdb</code><br/>
<code><datasetname>.BlueM.Opt.<timestamp>.mdb</code><br/>
If the result database already exists, it is overwritten when starting a new optimization.
where<br/>
 
:<code><datasetname></code> is the name of the dataset
=== Saving ===
:<code><timestamp></code> is the timestamp when the optimization was started in format YYYYMMddHHmm
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 ===
=== Loading ===
Line 25: Line 24:
* '''Constraints''': Constraint values
* '''Constraints''': Constraint values
* '''SekPop''': The pareto-front at each generation.  
* '''SekPop''': The pareto-front at each generation.  
* '''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>.

Latest revision as of 03:57, 24 January 2023

EVO.png BlueM.Opt | 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.

  1. Set App, Dataset and Method. These have to correspond to the settings used to produce the result database.
  2. 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

Tables

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.

Queries

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!
Retrieved from "https://wiki.bluemodel.org/index.php?title=BlueM.Opt_output_files&oldid=7725"