<h1 id="optimisation-optimisation-proposal">Optimisation Optimisation Proposal<a aria-hidden="true" class="anchor-heading icon-link" href="#optimisation-optimisation-proposal"></a></h1>
<p>Right now the scenarios panel is quite cluttered with a bunch of random things, including:</p>
<ul>
<li>Optimisation</li>
<li>Steady/MSS/Dynamics variables</li>
<li>Enable/disable initialisation</li>
<li>Enable/disable rating mode</li>
<li>choosing a solver</li>
</ul>
<p>It basically has become a dumping ground for features that don't fit cleanly in any other place.</p>
<p>We need to think about how to improve it. Do we even need scenarios? are there better places or implementations of these features?</p>
<h2 id="optimisation">Optimisation<a aria-hidden="true" class="anchor-heading icon-link" href="#optimisation"></a></h2>
<p>Right now, setting up optimisation involves choosing a bunch of options from a lot of different input fields - which property you want to minimise/maximise, what degrees of freedom there are, and so forth. How could we make it more connected to the main flowsheet? Some ideas include:</p>
<ul>
<li>Showing additional context on the flowsheet in optimisation view, so the units with a degree of freedom are in a different color, or the free properties are shown on the flowsheet below the unit operation</li>
<li>Having a unit operation/property picker tool if you want to pick a property for a field</li>
<li>possibly moving solver choice as a generic setting rather than scenario-specific, and the same for initialisation</li>
</ul>

Optimisation Optimisation Proposal

thesis

# Notes

Browse topics using the links or search above.