At present, we do SDPT3 solves by using a webdriver to open Firefox, go to the NEOS website, and submit the problem there, simulating manual submission. We watch the output page long enough to scrape the job ID and password, then pick up from there to do the rest with Python.
Why is this happening? Because of a NEOS bug by which manual submission and XML-RPC submission work differently for SDPT3 -> in the XML-RPC the problem is accepted but no solve message is returned. Therefore we simulate the manual submission case so we can get back the result message.
At some point in the future when SDPT3 on NEOS fully supports XML-RPC submission, we can remove this workaround easily.
At present, we do SDPT3 solves by using a webdriver to open Firefox, go to the NEOS website, and submit the problem there, simulating manual submission. We watch the output page long enough to scrape the job ID and password, then pick up from there to do the rest with Python.
Why is this happening? Because of a NEOS bug by which manual submission and XML-RPC submission work differently for SDPT3 -> in the XML-RPC the problem is accepted but no solve message is returned. Therefore we simulate the manual submission case so we can get back the result message.
At some point in the future when SDPT3 on NEOS fully supports XML-RPC submission, we can remove this workaround easily.