Hi Mike, That makes sense. Thanks. I think I've managed to understand something small about how this kind of interface works in Sage. Overall I'm very impressed how easy it is to do things with symmetric poly's in Sage. It kills Maple :)
Thanks, -BFJ On Jan 20, 5:25 pm, "Mike Hansen" <[EMAIL PROTECTED]> wrote: > Hello, > > It turns out that symmetrica internal representation of the result has > three variables (although the last one isn't used). The wrappers for > symmetrica live under sage/libs/symmetrica . I've made > thishttp://trac.sagemath.org/sage_trac/ticket/1873and posted a patch > there. The solution was to provide a way to override the > "autodetection" of the number of variables. You can see this at the > end of the patch (the changes were made to symmetrica.pxi). > > --Mike > > On Jan 20, 2008 12:34 PM, BFJ <[EMAIL PROTECTED]> wrote: > > > > > After looking into this a little bit, and getting my hands dirty > > looking through the code, I've tracked the problem to the following > > example. The expand() method in > > SymmetricFunctionAlgebraElement_elementary calls > > symmetrica.compute_elmsym_with_alphabet([3],3,'x') and it seems to me > > that the return value of the call is being interpreted in a ring > > that's too big. Consider: > > > sage: r=symmetrica.compute_elmsym_with_alphabet([3],3,'x') > > sage: r > > x0*x1*x2 > > sage: r.parent() > > Multivariate Polynomial Ring in x0, x1, x2, x3 over Integer Ring > > > Maybe someone can look into this, or if everyone is busy, maybe > > someone can tell me where to look at how values returned from > > symmetrica are interpreted and perhaps I can provide a patch. > > > Thanks, > > BFJ --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
