...
Info |
---|
Prior to using Insight, ensure that you have created and saved a Source project containing one scenario only. |
- Open Insight and click Browse (as shown in Figure 1) to choose the directory containing the project(s);
- Click Load to populate the left panel with all the objective functions that were created in the loaded projects;
- For each of the panels on the right, use the appropriate button to add or remove objectives or variables from the main objectives list to the individual panel. For example, click Add objective » to add an objective to the Objectives panel. Moreover, to move a discrete decision variable back to the main list of objective functions, click « Remove discrete decision variable.
- In the Objectives panel, the Multi-project Aggregation Method drop-down menu allows you to choose how you want to aggregate the individual time-step results. The Aggregate over full timeseries checkbox allows you to choose how to setup the objectives. If enabled, the objective needs to be set up so that all values of the global expression are used (via the selected statistical function) to give the objective value. If not, the last value of the global expression gives the objective value. You can also remove an objective from the Objectives panel by choosing it from the list and clicking . This will move the objective back to the main objectives list.
- Choose the number of generations and the population size of each generation. These parameters define how many simulation runs are performed by the optimiser. The required values will depend on the complexity of the optimisation project. If the number of runs is too small, the optimiser will not be given sufficient time to search for the multi-objective optimal set of results.
- Specify whether to run the optimisation on your local machine (enable the Run Source optimisation locally radio button), or across server endpoints (using the Run Source optimisation on endpoints radio button). Server endpoints allow you to run the optimisation across several machines simultaneously.
...
- Load the endpoints settings file by clicking Load Endpoints and point Insight to the appropriate file. If running Source optimisation on a local machine, set the number of cores to use with the Local server limit scroll button. The number of cores to use depends on the machine you will are using.
- Save your project settings using File » Save Settings. This creates a settings file, which can be used later, either in the command line or in the interface.
Info | ||
---|---|---|
| ||
Note: The difference between Objectives and tracked variables are that the former are optimised, whereas the latter are not. Tracked variables are a set of secondary objectives that may affect decision-making, but do not get optimised. |
...
Once you have nominated the location of Source, the Source project to optimise, and the objectives and decision variables, click Run to begin the optimisation.
The results can be saved for future use using File » Save results.
Using the command line
Insight can be configured, set up (to create a settings file) and run using the command line as well.
...
RiverSystem.CommandLine.exe -m server -a net.tcp://localhost:8594/insight
Setting up
...
endpoints using PowerShell script
...
You can also set up endpoints using the included PowerShell script.
Info | ||
---|---|---|
| ||
Note: If Source is installed in your Program Files folder, you will need to run PowerShell as administrator every time you set up endpoints. In the Start menu, right click on the PowerShell icon and choose Run as Administrator. |
Do the following on every machine that you wish to set up as an endpoint/s:
- Ensure that the RunSourceServersForInsight.ps1 file is in the same folder as RiverSystems.CommandLine.exe;
- Open PowerShell (Click on the Start menu (Windows 7), search for PowerShell, and press Enter);
- This method of setting up endpoints requires a change to the execution policy for each machine you wish to use as an endpoint. At the PowerShell command prompt, enter Set-ExecutionPolicy RemoteSigned. You will be asked to confirm the change (you can read more about this by selecting the relevant help topic). Choose Yes. Note that this needs to be done only once;
- Change the directory to the location of the RunSourceServersForInsight.ps1 file;
- Run the PowerShell script with ./RunSourceServersForInsight.ps1;
- The PowerShell script has automatically set up endpoints for you. Make a note of each endpoint, as these will be required when running the optimisation. Repeat this step across every machine that you wish to use as an endpoint. By default, the PowerShell script sets up two endpoints. To change the number of endpoints on the same computer, add the number of endpoints after the run command. For example: ./RunSourceServersForInsight.ps1 4 indicates 4 endpoints;
Info | ||
---|---|---|
| ||
Note: To find out more about execution policies, |
...
enter help about_execution_policy at the PowerShell command prompt |
...
. |
Running the optimisation
Once you have entered the parameters for each of the items listed in Table 2, press enter to begin the optimisation run.
As Insight computes the optimisation for each popluation, a completion notification is displayed in the command line. Figure 3 shows an example of this.
Viewing optimisation results
Results from a previous optimisation run (including those run from a command line) can be loaded using File » Load results.