Solver Interface

The information about the problem and its structure as processed by SML is stored in a tree of ExpandedModel objects.

The solver can be called by

SML_OOPS_driver(em)

where 'em' is the ExpandedModel representing the root node.

Bug:

This behaviour should be changed. Rather we should do something like Amplsolver:

• Either, compile SML into a library that provides a call of the form

ExpandedModel *SML_process_model(char *model_file_name, char *data_file_name)

• Or, pass the name of the solver to SML as a command line argument

  sml name-of-smlfile name-of-datafile name-of-solver 
  

  and SML would then finish with a final call of the form

  SML_<name-of-solver>_driver(em);
  

Each ExpandedModel object represents one node of the Expanded Model tree. It roughly corresponds to a child in a decomposition scheme applied to solve the problem. It gives information about the variables and constraints local to this node as well as links to any children.

It further provides an interface to AMPL that provides functions to ask AMPL to evaluate constraint functions on this node.