-
Notifications
You must be signed in to change notification settings - Fork 21
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
phc v2.4.52 10 Apr 2018: timeout when used with sage 8.0 or 8.1 #23
Comments
Thanks for reporting this issue. At https://github.com/sagemath/sagelib/blob/master/sage/interfaces/phc.py Polyhedral homotopies with double double and quad double arithmetic |
Note that https://github.com/sagemath/sagelib is a snapshot The change suggested by @janverschelde was made, see line 760 in |
The best known effort of combining SageMath and PHCPack
The dockerfile reveals computop-sage is currently based on
|
Thanks @janverschelde and @slel. Line 760 at the link provided by Samuel still has the old code, i.e. 'n' instead of '0' in the third element of the first argument to If I manually apply both the change suggested by @janverschelde and the fix in trac 4411 to https://github.com/sagemath/sagelib/blob/master/sage/interfaces/phc.py, I am able to run the 3-line demo successfully. |
@DrXyzzy you are right, the change from 'n' to '0' was not made. Do you mean you undo that patch? Or apply another patch proposed in |
After installing phc binary from PHCpack download page and attempting the first example from Sage docs here, we see the following:
This is seen on Linux Ubuntu 16.04 with the 64-bit Linux phc binary using both sage-8.0 and sage-8.1 in CoCalc sagews and in command terminal, as well as on OS X running sage-8.1 in a terminal with the current macOS phc binary.
Would it be possible to download an earlier version of phc for 64-bit Linux to try to isolate the problem and offer a possible workaround? For example, according to this thread from sage-support, the sage interface to PHCpack was working in July of 2017.
The text was updated successfully, but these errors were encountered: