Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a way to retrieve job results when the output is large #11

Closed
odow opened this issue Jul 26, 2016 · 3 comments
Closed

Find a way to retrieve job results when the output is large #11

odow opened this issue Jul 26, 2016 · 3 comments
Assignees

Comments

@odow
Copy link
Member

odow commented Jul 26, 2016

Job submitted by @healy-pa Job Number=4791864, Password=PdmVqbQA

#9 (comment)

There is a large quantity of log info and a large number of variables with non-zero values

@odow
Copy link
Member Author

odow commented Jul 26, 2016

@healy-pa you may want to try changing the display frequency to see if it reduces the output sufficiently.

s = NEOSCPLEXSolver()
addparameter!(s, "mip display", 0)

@odow
Copy link
Member Author

odow commented Nov 29, 2017

Attaching the archived job for future reference. 4791864.tar.gz

The model took approximately 25 minutes to solve, and had ~1700 lines of log information and ~1400 solution lines for the non-zero variables. Currently re-running to see what happens.

Edit: it's now been running for 3 hours with no result. Return email says

Job results too long for email. Download results from https://neos-server.org/neos/admin.html
Job Number=5726275, Password=qvrKkgJL

getFinalResults returns a page 2822 lines long. It looks as if the log gets truncated so that the solution is never displayed to the screen.

Have emailed NEOS support for advice.

@odow odow self-assigned this Nov 29, 2017
@odow
Copy link
Member Author

odow commented Dec 3, 2017

There are two issues here.

1. OP Issue: http pipe timed out

The original request waiting for getFinalResults timed out. The return email said results were too long, but getFinalResults will return the complete results. The timeout issue is now fixed (we poll getJobStatus although see #22 ).

2. NEOS time-limit

When I resubmitted the job, I got the same email, and the truncated log. From NEOS support:

That particular job actually hit the 8-hour limit, which explains why the output appears incomplete. getFinalResults is the appropriate way to retrieve results for a problem, though it obviously does not report back on time limit issues unfortunately.

I suggested they add a Error or TimeLimit status to getJobStatus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant