If I understand the documentation correctly, both cases should call the same Singular function (`groebner` in this case), with the only difference that one is called through the C interface and the other via the Pexpect interface. When I enable the protocol by passing `prot=True`, I get the exact same output, except that one prints faster than the other, which suggests that in both cases the same computation is run by Singular.
Actually, I was planning to add an option to Sage for calling the Singular function `modStd` for the modular approach you mention, when I found this speed difference. None of the current options in Sage seem to allow to make use of modular computations, except when using Giac. Am Samstag, 15. Juni 2019 21:34:03 UTC+2 schrieb Bill Hart: > > I would guess that `libsingular' is the C++ kernel of Singular which does > not implement all strategies for GB's over Q. There are additional > strategies implemented both in Singular library code and in the Singular > interpreter. Presumably the `singular' interface is using the interpreter, > if not a Singular library, which makes use of more advanced strategies. In > particular there is a library for a modular approach. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/9c034d11-15e0-4ae1-a689-751e039285be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
