Everyone! The NEOS Server is open free to the public. Some of the solvers may limit use, however.
First, you need to have your optimization problem formulated
in one of the input formats accepted by a solver. Look through
the solvers on the server-solvers
page to see what formats are available for your type of problem.
Most of the solvers have links to pages or Web sites that explain the
syntax of their input format. Once you have your input files ready,
you can go to the Web Form link on the solver page, fill in the
names of your files and any other information, and submit your job
to the Server. Later, you may look at the E-mail option or the
Submission Tool for Unix or Windows (or Macintosh when it
has a good Java runtime environment implementation).
The
NEOS Submission tool
is a high speed, socket-based interface for
that
provides easy access to all the optimization solvers
available with the NEOS Server.
This tool allows users to submit problems to the NEOS Server
directly from their local networks.
Results are displayed on the screen.
Yes! NEOS does not allow you to compress your entire submission, but if you want to compress the files individually (to accommodate large data files, for example), you can submit them via the Web or Submission Tool interfaces.
The
First of all, always give your email address so that the results can be sent to you more reliably. Sometimes when the execution takes a long time without producing any output, the Web server will cause the CGI script to time out. If you save the job password and number and enter them in the check-status.cgi form, it will give you intermediate or final results. If more than one day has passed since the job finished, however, the file with your results may have been deleted. Again, always give your email address for results forwarding.
Web servers place restrictions of the amount of data that can be uploaded. You should not have this problem if you use email or the Submission Tool. Some of the solvers have limits on the amount of data they can process, though.
Congratulations, you got the format for the
submission correct, and it was passed on to the solver. Usually a runtime
error means that the solver found a syntax error or a floating point
exception like an overflow or a subscript out of bounds. This type of error
should be detected by the solver, which will give an error message about the
problem.
We would appreciate hearing about it when the solver dies without any
message. Please send an email to the solver administrator via the
neos-comments screen for the solver page, mentioning the job number,
the submission interface you were using, and including the submission itself.
Check that the file you sent in contained no non-ASCII formatting
symbols from a composer such as Word or Word Perfect. By saving
your documents as
Some solvers have hard limits on the number of iterations they allow. In those cases, you will receive the results in terms of the best solution found in that number of iterations. The server has an automatic timeout set for one week, meaning that if your problem takes over one week of time on the solver, you will not receive a result. Really, though, any problem you expect to take that long should not rely on NEOS as a critical resource.
For Web submissions, the maximum number of bytes that may be submitted is currently 1048576. The limit for email submissions is set by our mail server, which may change without our knowledge. The Submission Tool has no hard-wired limit, but the NEOS Server will not send a job larger than 50000000bytes to any solver station.
If you have not received any response from the server within a reasonable amount of time (reasonable defined in terms of how fast your mail generally arrives), you probably will not. The
Extra text at the top of your email is harder to avoid with certain mailers and causes the server more problems. One known occasion when some mailers will pre-append information is when you "insert" a file rather than pasting the contents.
The NEOS server was not designed with the capabilities of a mail server, and the fact that it must use, and not merely display, email data limits the formats it can accept. If the first line cannot be parsed correctly, you should receive mail from the server with the offending line and the entire message below. There have been times, however, when the server could not respond to an email message at all. I suggest submitting a small test problem to see if the server can understand your mailer. You may choose one of the sample files on a "Sample Submission" page to send. They usually run only a few minutes.
You may need to refresh the NEOS pages in your browser. We are not above moving things around and have no way to give notice to people not on the neos-news mailing list. Also, solver administrators may choose to disable their solvers at any time without notice.
When you submit a job through the Web or submission tool interfaces, you should
not include the token delimiters you use with E-mail. These interfaces put
the tokens in for you.
Not necessarily. We've had problems like this in the past when the user data contained lines with only TAB characters in them. Try to make sure none of your files contain TABs, which can be added automatically by your editor. A strange fix, but it's worked before.
Your Fortran objective function can call other subroutines, but if the solver you are using indicates only one file, then the subroutines must all be located in that one file.
The paper by J. Czyzyk, M. Mesnier, and J. Moré,
The NEOS Server,
which appeared in
IEEE Journal on Computational Science and Engineering,
5 (1998), pages 68-75,
discusses the design and implementation of the NEOS Server.
The paper by W. Gropp and J. Moré,
Optimization Environments and the NEOS Server,
that appeared in Approximation Theory and Optimization,
M. D. Buhmann and A. Iserles, eds., pages 167-182,
Cambridge University Press, 1997,
discusses the NEOS Server as a problem-solving
environment that simplifies the formulation of
optimization problems and the access to computational resources.
The paper by M. Ferris, M. Mesnier, and J. Moré,
NEOS and Condor: Solving optimization problems over the Internet,
discusses the use of Condor,
a distributed resource management system, as a provider
of computational resources for NEOS.
You can download the paper in a
compressed postscript format.
The NEOS Server 4.0 Administrative Guide by E. Dolan
discusses the Server implementation and use in detail.
You can download the paper in a compressed postscript format.
We are currently using
ADIFOR
for Fortran programs, and
ADOLC
and
ADIC
for C programs. Consult
A Collection of Automatic Differentiation Tools
for additional information on automatic differentiation tools.
The first step is to contact us by sending email to .gz
,.z
,.zip
, and .Z
files.
.txt
files, you should be able to
get rid of the formatting symbols.