Hi again, thanks for your help > You are definitely not using libSingular but the Singular pexpect interface. > libSingular is the C++ interface to a subset of Singular (the kernel). Then, how do I use libSingular ? Is it used if work directly with the types implemented in sage, like R = QQ['x,y,z'] I = (x^2-y*z, z^7-x^2) * R I.primary_decomposition() ... and so on ?
> I can reproduce the discrepancy only to some extend: > > Singular > real 0m22.033s > user 0m21.026s > sys 0m0.856s > > Sage: > real 0m23.251s > user 0m0.846s > sys 0m0.303s Did you use my example ? How can there be such a discrepancy on my machine ? If it's as small as in your case I could easily live with it. > Some overhead is unavoidable because data has to be exchanged between > Singular > and Sage. Since the radical command is only available as a Singular script > (rather than in the kernel) I don't see an immediate way around it. an ideal in sage has the method .radical(), does that mean the pexpect interface is called in this case ? Summarizing, what is the smartest way to use Singular from within Sage ? cheers Thomas
signature.asc
Description: This is a digitally signed message part
