> > >> You can help sage by filing a bug report. > > I would be willing to 1) submit a bug report, and even 2) try to solve > it if somebody would assist me with whole process of submitting a track > (maybe in #sagemath channel on freenode. That would be a fantastic > opportunity to collaborate with the Sage development. I would be very > happy to have the option of integrating this kind of functions in Sage.
Great! We always welcome new help of any kind :) You should definitely go to http://trac.sagemath.org/sage_trac/ and follow instructions to get an account there, then fill out a new defect request ticket with the information you have in your original post (and/or some of the information in my and Nils' posts, as relevant). A few different examples (such as the desolve_laplace one) would be helpful too. As I point out, I think this is indeed there (see http://trac.sagemath.org/sage_trac/ticket/385), it's just somehow not connecting with the output here for some reason. You could start finding it by following the code for desolve - you could put in some print statements after the 'soln' is found to see what it looks like. I think that here the problem is probably that taylor and laplace coerce into SR, which forces the 'at' substitution, while the desolvers all use soln.sage(), which bypasses this. We need to unify our Maxima conversions (and get a lot of them out of calculus.py, where they don't really belong) but it's been a back-burner issue since it's usually easier to do little fixes here and there. - kcrisman -- 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 URL: http://www.sagemath.org
