mmexset.c: Using sets in Mosel (requires burglari.bim)

• retrieve a set by its model name
• get the set size
• get first and last set element
• get the name or index of a set element

mmexarr.c: Using arrays in Mosel (requires trans.bim)

• compare index tuples
• retrieve an array by its model name
• get array size and number of dimensions
• get indices of first and last array entries
• get (value of) array entries
• check whether an index tuple lies in the range of an array

mmexas.c: Using arrays with index sets (requires trans.bim)

• get indexing sets of an array
• get array type
• enumerate array entries in usual and transposed order
• enumerate true array entries

mmexlst.c: Using lists in Mosel (requires euler.mos and euler.dat)

• retrieve a list by its model name
• get the list size
• enumerate the list elements
• get value of list element

mmexrec.c: Using records in Mosel (requires burglar_rec.mos and burglar_rec.dat)

• retrieve an array of records (user type) by its model name
• retrieve the record field information (field name, type, and number)
• enumerate the array of records
• for each array entry (record) get the value of all its fields

mmexprob.c: Accessing problems and solution information with Mosel (requires blend2.bim)

• export problem to a file (MPS or LP format)
• get problem status
• get objective function value
• get primal/dual solution values, and constraint activity

Note that these examples require the provided mos files to be pre-compiled.

Further explanation of this example: 'Mosel Library Reference Manual', Section 1.2 Post processing interface

! Data file for `burglar_rec.mos'

I: [("camera") [15 2] ("necklace") [100 20] ("vase") [90 20]
    ("picture") [60 30] ("tv") [40 40] ("video") [15 30] 
    ("chest") [10 60] ("brick") [1 10]]