Algebraic modeling language

The core elements of an AML are: • a modeling language interpreter (the AML itself) • solver links • user interfaces (UI) • data exchange facilities == Design principles ==

Most AML follow certain design principles: • a balanced mix of declarative and procedural elements • open architecture and interfaces to other systems • different layers with separation of: • model and data • model and solution methods • model and operating system • model and interface Data driven model generation Most modeling languages exploit the similarities between structured models and relational databases table handlers for AMPL). With the refinement of analytic technologies applied to business processes, optimization models are becoming an integral part of decision support systems; optimization models can be structured and layered to represent and support complex business processes. In such applications, the multi-dimensional data structure typical of OLAP systems can be directly mapped to the optimization models and typical MDDB operations can be translated into aggregation and disaggregation operations on the underlying model ==History==

Algebraic modelling languages find their roots in matrix-generator and report-writer programs (MGRW), developed in the late seventies. Some of these are MAGEN, MGRW (IBM), GAMMA.3, DATAFORM and MGG/RWG. These systems simplified the communication of problem instances to the solution algorithms and the generation of a readable report of the results. An early matrix-generator for LP was developed around 1969 at the Mathematisch Centrum (now CWI), Amsterdam. Its syntax was very close to the usual mathematical notation, using subscripts en sigmas. Input for the generator consisted of separate sections for the model and the data. It found users at universities and in industry. The main industrial user was the steel maker Hoogovens (now Tata Steel) where it was used for nearly 25 years. A big step towards the modern modelling languages is found in UIMP, where the structure of the mathematical programming models taken from real life is analyzed for the first time, to highlight the natural grouping of variables and constraints arising from such models. This led to data-structure features, which supported structured modelling; in this paradigm, all the input and output tables, together with the decision variables, are defined in terms of these structures, in a way comparable to the use of subscripts and sets. This is probably the single most notable feature common to all modern AMLs and enabled, in time, a separation between the model structure and its data, and a correspondence between the entities in an MP model and data in relational databases. So, a model could be finally instantiated and solved over different datasets, just by modifying its datasets. The correspondence between modelling entities and relational data models, made then possible to seamlessly generate model instances by fetching data from corporate databases. This feature accounts now for a lot of the usability of optimization in real life applications, and is supported by most well-known modelling languages. While algebraic modelling languages were typically isolated, specialized and commercial languages, more recently algebraic modelling languages started to appear in the form of open-source, specialized libraries within a general-purpose language, like Gekko or Pyomo for Python or JuMP for the Julia language. == Notable AMLs==

Specialized AMLs • AIMMS • AMPL • GAMS • MathProg • MiniZinc • OPL AML Packages in Generic Programming Languages • FlopC++ for C++ • OptimJ for Java • JuMP for Julia • GBOML for Python • Pyomo for Python ==References==