See also: Analysis View, Transformation Analysis, Introduction to Optimization, Specifying Capacity Data
This variable is used to control whether a module's calculations for a given scenario are carried out using LEAP's optimization or simulation methodologies.
You can control which scenarios use optimization by simply editing the Optimize variable in LEAP in any given scenario. When this variable is set to Yes, the default optimization framework and solver will be used (currently OSeMOSYS with the free GLPK solver). When set to No, LEAP will use its accounting and simulation calculations. For finer grade control, you can even make use of different frameworks and solvers to calculate different scenarios. This can be useful for checking that different frameworks and solvers yield the same results. In some rare cases they may yield slightly different results (most often due to optimizations of the solver code designed to speed up calculations). The allowable keywords used for the Optimize variable are currently as follows:
Yes: Optimize using OSeMOSYS and GLPK
No: Use LEAP's own accounting and simulation calculation methods
OSeMOSYS(GLPK): Optimize using OSeMOSYS and GLPK: Equivalent to "yes"
OSeMOSYS(CPLEX): Optimize using OSeMOSYS and the CPLEX solver
NEMO(GLPK): Optimize using NEMO and the GLPK solver
NEMO(Cbc): Optimize using NEMO and the Cbc solver
NEMO(CPLEX): Optimize using NEMO and the CPLEX solver
NEMO(GUROBI): Optimize using NEMO and the GUROBI solver
NEMO(MOSEK): Optimize using NEMO and the MOSEK solver
NEMO(XPRESS): Optimize using NEMO and the Fico XPress solver
Note that the commercial solvers CPLEX, and GUROBI must be purchase installed separately from LEAP and NEMO. MOSEK is installed with NEMO but you must have a properly purchased and installed license file for MOSEK in order for it to calculate. Use the orange Exp button () in the data entry table to quickly choose a framework and solver from among those installed (as shown on right).
Note that you cannot conduct optimization calculations for Current Accounts and so this variable is only available in scenarios (not in Current Accounts).