If AMPL appears to hang after a
solve command but before any output from a solver, then it may be taking much more time to generate your problem than you expected. Try setting
option times 1, gentimes 1 to get more output recording AMPL’s progress, as explained in the FAQ question regarding insufficient memory.
The same advice applies if AMPL hangs after some other command, such as
expand, that forces a lot of variables or constraints to be generated.
If AMPL appears to hang after a command that produces a listing, such as
display, then the listing may be much longer than you expected. Usually it is possible to make a quick estimate of the size of the listing, in order to determine whether this could be the difficulty.
If AMPL appears to hang after a line or more from the solver, then your optimization problem may be taking much more time to solve than you expected. Try setting solver directives that provide more output recording progress toward an optimum. Some solvers may also respond to a “break” sequence (such as Ctrl-C) by returning the best solution found so far. These features differ from one solver to the next and even from one algorithm to the next within the same solver; see the solver-specific documentation for details.
Posted in: Errors and Messages