dotnet add package OOOT --version 22.214.171.1242
NuGet\Install-Package OOOT -Version 126.96.36.1992
<PackageReference Include="OOOT" Version="188.8.131.522" />
paket add OOOT --version 184.108.40.2062
#r "nuget: OOOT, 220.127.116.112"
// Install OOOT as a Cake Addin #addin nuget:?package=OOOT&version=18.104.22.1682 // Install OOOT as a Cake Tool #tool nuget:?package=OOOT&version=22.214.171.1242
A library (.dll) of various linear, nonlinear, and stochastic numerical optimization techniques. While some of these are older than 40 years, many have yet to take advantage of an object-oriented programming model. This toolbox was originally created to aid in the automated design of various engineering artifacts.
The following “class diagram” shows the main optimization methods that have currently been implemented – as well as some insight into organization of classes and objects. The best way to understand how to use OOOT, is through examples. There are two basic types of methods implemented so far: methods for continuous variables and methods for discrete variables. Approaches for mixed methods such as Branch-and-Bound are planned but not currently included.
ClassDiagram1Many of the optimization methods for real valued decision variables will require that a line-search method be specified (Arithmetic Mean, Golden Section, DSC-Powell) and a search direction method (Cyclic Coordinate Search, Steepest Descent, Powell’s Method, Fletcher-Reeves, or Broyden-Fletcher-Goldfarb-Shanno).
With this modular design it is possible to reconfigure these to create 80 unique algorithms. In addition to these there are also ten different convergence criteria that can be added individually or in any combination to these 80 algorithms. Read more about convergence methods here.
But, one of the biggest advantages of the toolbox is the way that objective functions, equalities and inequalities can be easily added to the optimization process. Most (if not all open source approaches) optimization codes requires the problem specific details to be compiled along with the algorithm. Here, the problem formulation can be in another library or exe and can be customized at run-time instead of compile time. It is even possible to have the optimization algorithm change in response to the nature of the design variables and the number of constraints. Read more about problem formulation
|Product||Versions Compatible and additional computed target framework versions.|
|.NET||net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed.|
|.NET Core||netcoreapp3.0 was computed. netcoreapp3.1 was computed.|
|.NET Standard||netstandard2.1 is compatible.|
|MonoAndroid||monoandroid was computed.|
|MonoMac||monomac was computed.|
|MonoTouch||monotouch was computed.|
|Tizen||tizen60 was computed.|
|Xamarin.iOS||xamarinios was computed.|
|Xamarin.Mac||xamarinmac was computed.|
|Xamarin.TVOS||xamarintvos was computed.|
|Xamarin.WatchOS||xamarinwatchos was computed.|
- StarMath (>= 126.96.36.199)
This package is not used by any NuGet packages.
This package is not used by any popular GitHub repositories.