BlueM.Opt output files: Difference between revisions

From BlueM
Jump to navigation Jump to search
(aktualisiert r778)
(update for BlueM.Opt v2.1.0)
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Ergebnisdatenbank==
{{BlueM.Opt_nav}}
[[Bild:EVO Ergebnis-Buttons.gif|thumb|Ergebnis-Buttons in EVO.NET]]
<div style="float:right; margin:0 0 5px 5px;">__TOC__</div>
Die Ergebnisdatenbank enthält die Qualitätswerte ("'''QWerte'''"), die "'''Constraints'''" und die zugehörigen Optimierungsparameter ("'''OptParameter'''") jeder Simulation, die während der Optimierung ausgeführt wurde.  
==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.  


Die Optimierungsergebnisse werden standardmäßig in eine temporäre Ergebnisdatenbank geschrieben. Diese wird unter <br/>
The result database is stored in the directory containing the dataset with following filename: <br/>
<code>C:\Dokumente und Einstellungen\BENUTZERNAME\Lokale Einstellungen\Temp\EVO.mdb</code><br/>
<code><datasetname>.BlueM.Opt.<timestamp>.mdb</code><br/>
abgelegt. Falls diese schon vorhanden ist, wird sie überschrieben.
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


Um die Ergebnisdatenbank abzuspeichern, auf den Button ''Ergebnisdatenbank speichern'' klicken.
=== 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.


Eine bestehende Ergebnisdatenbank kann auch wieder angebunden werden:
=== Structure ===
# Anwendung, Datensatz und Methode auswählen
[[File:ErgebnisDB_Tables.png|thumb|300px|Tables]]
# Auf den Button ''Optimierungsergebnis aus Datenbank laden'' klicken
The result database contains several tables:
Wichtig: Der eingelesene Datensatz muss mit der Datenbank übereinstimmen!
* '''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.


[[Kategorie:EVO Ausgabedateien]]
All tables can be linked using the common column <code>'''Sim_ID'''</code>.
 
[[File:ErgebnisDB_Queries.png|thumb|300px|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]]!
 
[[Category:BlueM.Opt output files]]

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"