[sage-devel] Re: Sage's C/C++ libraries

[AndyNovo]

We do some pretty cool optimizations for the ranges that impact
polynomial factorization.  Namely I do everything possible to always
get away with double precision in the floating-point parts, a lot of
this is new mathematically as we're really creating alternative paths
to reduced bases which are more numerically stable.  As a result we
are much faster for lattices of large dimension and/or large bits, but
I'm not sure how far that stretches.

The reason I suspect that there might be another cut-off (for
extremely large dimensions...) is that fpLLL picks its starting
precision early on rather than attempt anything greedy, if it's too
high then it uses mpfr at the proved precision.  We have a back-up
mpfr-based LLL which is supposed to catch any situations when our
optimizations fail.  Ours starts at a precision of 53 bits and
increases the precision until it works.  I have spent almost no time
optimizing our mpfr-LLL, since needing mpfr was a terrible thing for
any real factoring timings, and the strategy I mention above was
chosen before I understood that.

Some testing could make a heuristic for when FLINT's LLL wins and when
fpLLL is more suitable if such situations exist or are not too common.

On Oct 5, 10:48 pm, Bill Hart  wrote:
> Difficult question. The difficulty is that it uses FLINT matrices.
> Otherwise the answer would probably be yes, I think. But I'll check
> with Andy Novocin on that. He is more aware of how the performance
> will compare for wider classes of problems than the ones we've been
> specifically attacking.
>
> Bill.
>
> On 5 Oct, 12:24, Martin Albrecht 
> wrote:
>
> > On Tuesday 05 October 2010, Bill Hart wrote:
>
> > > I also think the bit about Magma using an old fpLLL may be out-of-
> > > date. Damien Stehle recently did quite a bit of work for the Magma
> > > group. I'm not 100% sure it's been updated in the latest released
> > > Magma, but I would be surprised to find it hadn't been.
>
> > > Not to worry though, Damien has been a great source of help and
> > > information for Andy Novocin and I as we've been improving our own
> > > version of fpLLL in FLINT. My understanding is that for certain
> > > problems at least, the FLINT version of fpLLL will be faster again.The
> > > developments in LLL are currently pretty hard to keep up with. It's a
> > > field that is developing at breakneck pace! I imagine FLINT's version
> > > of fpLLL will be completely outdated within 24 hours of release, LOL
> > > (yes, we still haven't released it, but we are nearly there)!
>
> > Is your LLL a complete (more or less) drop in replacement for fpLLL? Should 
> > we
> > use this instead of fpLLL in Sage?
>
> > Cheers,
> > Martin
>
> > --
> > name: Martin Albrecht
> > _pgp:http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> > _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
> > _www:http://martinralbrecht.wordpress.com/
> > _jab: martinralbre...@jabber.ccc.de

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage mailing lists

[koffie]

And don't forget the sage-flame list ;)

http://groups.google.com/group/sage-flame

On Oct 6, 5:00 am, Minh Nguyen  wrote:
> Hi Mitesh,
>
> On Wed, Oct 6, 2010 at 10:29 AM, Mitesh Patel  wrote:
> > Have I missed any?
>
> The group debian-sage [1] seems to be reviving lately. Recent
> discussions (in the last few days) have been about fixing the
> packaging of Sage in Debian. There's also sagemath-users [2]. It's not
> "active", but should be kept track of.
>
> [1]http://groups.google.com/group/debian-sage
>
> [2]http://groups.google.com/group/sagemath-users
>
> --
> Regards
> Minh Van Nguyen

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Help getting started with Hopf algebras in Sage

[jvkersch]

Hi Niles,

Like John, I would like to be cc'd on any tickets about this.  Apart
from the obvious mathematical importance, I'm quite interested in
finding out the right way of implementing these structures.  I don't
know if I'll be able to contribute immediately, but I'm looking
forward to seeing how this goes.

Incidentally, for the DifferentialForms class I took the
implementation of the Steenrod algebra as my starting point.  Maybe
having a better understanding of the categorical framework, etc.  will
help me out with my DifferentialForms too.

All the best,
Joris


On 5 okt, 14:41, Niles  wrote:
> Hello all,
>
> I'm interested in implementing some computational algebraic topology
> using Hopf algebroids.  As a warm-up, I thought I would see what
> functionality exists in Sage for coalgebras, comodules, Hopf algebras,
> etc.  What currently exists seems to be placeholder categories (e.g.
> [1], [2]), and some implementation for group algebras (see [3]).  I've
> read through the Category Theory Primer (Draft) [4] and the Categories
> Tutorial (Draft) [5], but none of this leaves me with a good sense of
> how to proceed.  It's clear that someone has a vision of how new
> functionality (like computations with Hopf algebroids) should be added
> to Sage, but it's not clear to me what that vision is (beyond step
> one, which seems to be "make a placeholder category for it").
>
> If I just want to extend Sage's capabilities for, say, Hopf algebras
> (build some new classes for Hopf algebras other than group algebras,
> and add some new generic functionality), what would be the right place
> to start? Or the right example to follow?  Or is there another source
> I should be looking at?  Whatever answer you give me, does the same
> answer hold for comodules over coalgebras, and the like?
>
> thanks,
> Niles
>
> p.s.  Just before sending this, I remembered that I should also look
> in existing open-source software for an implementation of these things
> which I could import into Sage; I'll do that, but if you already know
> of one, maybe you could let me know :)
>
>  [1]:http://www.sagemath.org/doc/reference/sage/categories/coalgebras.html
>  [2]:http://www.sagemath.org/doc/reference/sage/categories/hopf_algebras_w...
>  [3]:http://trac.sagemath.org/sage_trac/ticket/8589
>  [4]:http://www.sagemath.org/doc/reference/sage/categories/primer.html
>  [5]:http://www.sagemath.org/doc/reference/sage/categories/tutorial.html

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Sage mailing lists

[Minh Nguyen]

Hi Mitesh,

On Wed, Oct 6, 2010 at 10:29 AM, Mitesh Patel  wrote:
> Have I missed any?

The group debian-sage [1] seems to be reviving lately. Recent
discussions (in the last few days) have been about fixing the
packaging of Sage in Debian. There's also sagemath-users [2]. It's not
"active", but should be kept track of.


[1] http://groups.google.com/group/debian-sage

[2] http://groups.google.com/group/sagemath-users

-- 
Regards
Minh Van Nguyen

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Where is the source for sage.matrix.matrix_modn_sparse.Matrix_modn_sparse.__eq__?

[François Bissey]

> I would like to see the source code of
> sage.matrix.matrix_modn_sparse.Matrix_modn_sparse.__eq__(), but I have
> no idea where to look.  The following doesn't work::
> 
> sage: L1 = matrix(GF(43), 3, 3, range(9), sparse=True)
> sage: L1.__eq__??
> Error getting source: arg is not a module, class, method, function,
> traceback, frame, or code object
> Type:   method-wrapper
> Base Class: 
> String Form: sage.matrix.matrix_modn_sparse.Matrix_modn_sparse object at 0x5bb2dd0>
> Namespace:  Interactive
> Docstring [source file open failed]:
> x.__eq__(y) <==> x==y
sage/matrix/matrix_modn_sparse.pyx ?

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Sage mailing lists

[Mitesh Patel]

Is there a complete list of "active" public Sage mailing lists at
sagemath.org or the Sage wiki?  I'm aware of

sage-algebra
http://groups.google.com/group/sage-algebra
sage-announce
http://groups.google.com/group/sage-announce
sage-combinat-devel
http://groups.google.com/group/sage-combinat-devel
sage-devel
http://groups.google.com/group/sage-devel
sage-edu
http://groups.google.com/group/sage-edu
sage-finance
http://groups.google.com/group/sage-finance
sage-grid
http://groups.google.com/group/sage-grid
sage-marketing
http://groups.google.com/group/sage-marketing
sage-notebook
http://groups.google.com/group/sage-notebook
sage-nt
http://groups.google.com/group/sage-nt/
sage-release
http://groups.google.com/group/sage-release
sage-solaris
http://groups.google.com/group/sage-solaris
sage-support
http://groups.google.com/group/sage-support
sage-windows
http://groups.google.com/group/sage-windows
sage-trac
http://groups.google.com/group/sage-trac

Have I missed any?

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Help getting started with Hopf algebras in Sage

[John H Palmieri]

On Oct 5, 2:41 pm, Niles  wrote:
> Hello all,
>
> I'm interested in implementing some computational algebraic topology
> using Hopf algebroids.  As a warm-up, I thought I would see what
> functionality exists in Sage for coalgebras, comodules, Hopf algebras,
> etc.  What currently exists seems to be placeholder categories (e.g.
> [1], [2]), and some implementation for group algebras (see [3]).  I've
> read through the Category Theory Primer (Draft) [4] and the Categories
> Tutorial (Draft) [5], but none of this leaves me with a good sense of
> how to proceed.  It's clear that someone has a vision of how new
> functionality (like computations with Hopf algebroids) should be added
> to Sage, but it's not clear to me what that vision is (beyond step
> one, which seems to be "make a placeholder category for it").
>
> If I just want to extend Sage's capabilities for, say, Hopf algebras
> (build some new classes for Hopf algebras other than group algebras,
> and add some new generic functionality), what would be the right place
> to start? Or the right example to follow?  Or is there another source
> I should be looking at?  Whatever answer you give me, does the same
> answer hold for comodules over coalgebras, and the like?

First, you might want to post this on sage-combinat-devel and/or sage-
algebra, as well as sage-devel.

Second, I think having something with Hopf algebroids would be great!
Please cc me on any ticket.

Third, the file devel/sage/sage/categories/examples/
hopf_algebras_with_basis.py is an instructive, although brief,
application of the basic Hopf algebra structure.  At least you can see
how to use CombinatorialFreeModule combined with a method like
"antipode_on_basis" to define an antipode.

Fourth, if you want to review , you'll see how I used the Hopf algebra stuff in Sage to
rewrite the implementation of the Steenrod algebra.  (Don't feel any
obligation, but I'm not sure who else to ask to do this...)

A while ago, I polled people about topological ideas that might get
added to Sage: see .  Unfortunately
there seems to be nothing about Hopf algebroids (although formal group
laws were mentioned).  If you feel like adding to that page, please
do.

--
John

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Help getting started with Hopf algebras in Sage

[Niles]

Hello all,

I'm interested in implementing some computational algebraic topology
using Hopf algebroids.  As a warm-up, I thought I would see what
functionality exists in Sage for coalgebras, comodules, Hopf algebras,
etc.  What currently exists seems to be placeholder categories (e.g.
[1], [2]), and some implementation for group algebras (see [3]).  I've
read through the Category Theory Primer (Draft) [4] and the Categories
Tutorial (Draft) [5], but none of this leaves me with a good sense of
how to proceed.  It's clear that someone has a vision of how new
functionality (like computations with Hopf algebroids) should be added
to Sage, but it's not clear to me what that vision is (beyond step
one, which seems to be "make a placeholder category for it").

If I just want to extend Sage's capabilities for, say, Hopf algebras
(build some new classes for Hopf algebras other than group algebras,
and add some new generic functionality), what would be the right place
to start? Or the right example to follow?  Or is there another source
I should be looking at?  Whatever answer you give me, does the same
answer hold for comodules over coalgebras, and the like?



thanks,
Niles

p.s.  Just before sending this, I remembered that I should also look
in existing open-source software for an implementation of these things
which I could import into Sage; I'll do that, but if you already know
of one, maybe you could let me know :)


 [1]: http://www.sagemath.org/doc/reference/sage/categories/coalgebras.html
 [2]: 
http://www.sagemath.org/doc/reference/sage/categories/hopf_algebras_with_basis.html
 [3]: http://trac.sagemath.org/sage_trac/ticket/8589
 [4]: http://www.sagemath.org/doc/reference/sage/categories/primer.html
 [5]: http://www.sagemath.org/doc/reference/sage/categories/tutorial.html

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Where is the source for sage.matrix.matrix_modn_sparse.Matrix_modn_sparse.__eq__?

[Jeroen Demeyer]

I would like to see the source code of
sage.matrix.matrix_modn_sparse.Matrix_modn_sparse.__eq__(), but I have
no idea where to look.  The following doesn't work::

sage: L1 = matrix(GF(43), 3, 3, range(9), sparse=True)
sage: L1.__eq__??
Error getting source: arg is not a module, class, method, function,
traceback, frame, or code object
Type:   method-wrapper
Base Class: 
String Form:
Namespace:  Interactive
Docstring [source file open failed]:
x.__eq__(y) <==> x==y

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: [debian-sage] Sympy version 0.6.7: issues with upgrading?

[Ondrej Certik]

On Sat, Oct 2, 2010 at 11:22 AM, cjfsyntropy  wrote:
> Sage currently ships v. 0.6.4 of sympy
> (http://www.sagemath.org/packages/standard/sympy-0.6.4.p0.txt).
>
> I found the hint below in another thread.  But what are the issues
> with
> upgrading sympy to v. 0.6.7?  I could not find a ticket in trac (did I
> miss
> it)?

I just tried to upgrade it and run tests and it didn't work. I
currently don't have time to investigate further. If someone could
make the upgrade, it'd be great. I'll help with resolving any
potential issues.

Thanks,
Ondrej

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage's C/C++ libraries

[Bill Hart]

Difficult question. The difficulty is that it uses FLINT matrices.
Otherwise the answer would probably be yes, I think. But I'll check
with Andy Novocin on that. He is more aware of how the performance
will compare for wider classes of problems than the ones we've been
specifically attacking.

Bill.

On 5 Oct, 12:24, Martin Albrecht 
wrote:
> On Tuesday 05 October 2010, Bill Hart wrote:
>
> > I also think the bit about Magma using an old fpLLL may be out-of-
> > date. Damien Stehle recently did quite a bit of work for the Magma
> > group. I'm not 100% sure it's been updated in the latest released
> > Magma, but I would be surprised to find it hadn't been.
>
> > Not to worry though, Damien has been a great source of help and
> > information for Andy Novocin and I as we've been improving our own
> > version of fpLLL in FLINT. My understanding is that for certain
> > problems at least, the FLINT version of fpLLL will be faster again.The
> > developments in LLL are currently pretty hard to keep up with. It's a
> > field that is developing at breakneck pace! I imagine FLINT's version
> > of fpLLL will be completely outdated within 24 hours of release, LOL
> > (yes, we still haven't released it, but we are nearly there)!
>
> Is your LLL a complete (more or less) drop in replacement for fpLLL? Should we
> use this instead of fpLLL in Sage?
>
> Cheers,
> Martin
>
> --
> name: Martin Albrecht
> _pgp:http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
> _www:http://martinralbrecht.wordpress.com/
> _jab: martinralbre...@jabber.ccc.de

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] segfault while running sage

[Burcin Erocal]

Hi Johannes,

On Tue, 05 Oct 2010 16:54:29 +0200
Johannes  wrote:


> using Sage Version 4.5.3, Release Date: 2010-09-04
> 
> running sage -gdb leads to this:
> 
> sage: filter(lambda x:  all([item.denominator()._cmp_(1) for item in
> x]), [[coordinate.subs(c=0).subs(b=0) for coordinate in item] for item
> in wi ])
> 
> Program received signal SIGSEGV, Segmentation fault.
> GiNaC::basic::compare (this=0x8416bb0, other=...) at basic.cpp:838
> 838 basic.cpp: No such file or directory.
> in basic.cpp
> 
> it seems to be a bug in the _cmp_ function.

This sounds very similar to the problem at #9880. Jean-Pierre Flori has
been working on a patch to fix the comparison functions in pynac. 

The fix won't make it to Sage 4.6, but it should be ready in time to be
reviewed for Sage 4.6.1.

Cheers,
Burcin

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: German translation of the tutorial / Übersetzung des Tutorials in Deutsch

[maldun]

When I find some time this weekend, I can do some proofreading.

Hope you get along with austrian german as well ;-)

greez,
maldun

On Oct 5, 12:10 am, Philipp Schneider 
wrote:
>  Dear Sage community,
>
> Michael Mardaus and I are happy to announce that we have finished
> translating the complete Sage tutorial to German.
>
> Now we need the help of as many German speaking users as possible to
> proofread our translation.
> If you happen to belong to this group and have some minutes to speak, we
> would be happy if you could send us corrections or improved formulations.
>
> you can find the current version of the translation in html format 
> at:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/ht...
>
> or in pdf format 
> at:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/pd...
>
> You can either send me the corrections per email, or you can post them
> to sage trac at:http://trac.sagemath.org/sage_trac/ticket/9725
>
> Thank you,
> Philipp Schneider
>
> 
>
> Liebe Sage-Community,
>
> Michael Mardaus und ich sind gl cklich dar ber, dass wir verk nden
> k nnen, dass wir das komplette Sage-Tutorial in Deutsch bersetzt haben.
>
> Nun ben tigen wir die Hilfe beim Korrekturlesen unserer bersetzung von
> m glichst vielen deutschsprachigen Sage-Nutzern .
> Falls Sie sich angesprochen f hlen und etwas Zeit haben, w rden wir uns
> freuen, wenn Sie uns auf Fehler aufmerksam machen, oder verbesserte
> Formulierungen schicken w rden.
>
> Sie k nnen die aktuelle Version der bersetzung hier im html-Format 
> finden:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/ht...
>
> oder im pdf-Format 
> unter:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/pd...
>
> Sie k nnen mir die Verbesserungen entweder per Email schicken, oder Sie
> k nnen diese auf Sage-trac 
> unter:http://trac.sagemath.org/sage_trac/ticket/9725
> eingeben.
>
> Vielen Dank,
> Philipp Schneider

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] segfault while running sage

[Johannes]

Hi,
i just got my sage crashed with theis following command

sage: filter(lambda x:  all([item.denominator()._cmp_(1) for item in
x]), [[coordinate.subs(c=0).subs(b=0) for coordinate in item] for item
in wi ])



Unhandled SIGSEGV: A segmentation fault occurred in Sage.
This probably occurred because a *compiled* component
of Sage has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).



Process SAGE exited abnormally with code 1


using Sage Version 4.5.3, Release Date: 2010-09-04

running sage -gdb leads to this:

sage: filter(lambda x:  all([item.denominator()._cmp_(1) for item in
x]), [[coordinate.subs(c=0).subs(b=0) for coordinate in item] for item
in wi ])

Program received signal SIGSEGV, Segmentation fault.
GiNaC::basic::compare (this=0x8416bb0, other=...) at basic.cpp:838
838 basic.cpp: No such file or directory.
in basic.cpp

it seems to be a bug in the _cmp_ function.

greatz Johannes

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: German translation of the tutorial / Übersetzung des Tutorials in Deutsch

[maldun]

When I find some time this weekend I will make a little bit
proofreading.

greez,
maldun

On Oct 5, 12:10 am, Philipp Schneider 
wrote:
>  Dear Sage community,
>
> Michael Mardaus and I are happy to announce that we have finished
> translating the complete Sage tutorial to German.
>
> Now we need the help of as many German speaking users as possible to
> proofread our translation.
> If you happen to belong to this group and have some minutes to speak, we
> would be happy if you could send us corrections or improved formulations.
>
> you can find the current version of the translation in html format 
> at:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/ht...
>
> or in pdf format 
> at:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/pd...
>
> You can either send me the corrections per email, or you can post them
> to sage trac at:http://trac.sagemath.org/sage_trac/ticket/9725
>
> Thank you,
> Philipp Schneider
>
> 
>
> Liebe Sage-Community,
>
> Michael Mardaus und ich sind gl cklich dar ber, dass wir verk nden
> k nnen, dass wir das komplette Sage-Tutorial in Deutsch bersetzt haben.
>
> Nun ben tigen wir die Hilfe beim Korrekturlesen unserer bersetzung von
> m glichst vielen deutschsprachigen Sage-Nutzern .
> Falls Sie sich angesprochen f hlen und etwas Zeit haben, w rden wir uns
> freuen, wenn Sie uns auf Fehler aufmerksam machen, oder verbesserte
> Formulierungen schicken w rden.
>
> Sie k nnen die aktuelle Version der bersetzung hier im html-Format 
> finden:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/ht...
>
> oder im pdf-Format 
> unter:http://wwwcip.informatik.uni-erlangen.de/~snphschn/sage/doc/output/pd...
>
> Sie k nnen mir die Verbesserungen entweder per Email schicken, oder Sie
> k nnen diese auf Sage-trac 
> unter:http://trac.sagemath.org/sage_trac/ticket/9725
> eingeben.
>
> Vielen Dank,
> Philipp Schneider

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Decorators degrading documentation

[jason-sage]

On 10/5/10 6:48 AM, Johan S. R. Nielsen wrote:

On Sep 23, 2:57 pm, Jason Grout  wrote:

On 9/23/10 7:13 AM, Johan S. R. Nielsen wrote:




Hi



I find the generic version of the function definitions less than
satisfactory.  I'd guess it would be had to make Sphinx pickup the
more detailed info in these situations?  I'd also guess the decorators
could maybe manipulate the docstring and inject some information based
on the arguments of the decorator?  Either way, could the effect of
these decorators on the documentation be improved?



I agree that this is completely unacceptable. I have created Trac 9976
and
written a patch for Sage's custom version of Sphinx. This essentially
checks if
a function/method to be documented is a decorator by looking for the
attribute
"_sage_decorating". If a function/method is actually a decorated
version of
another callable, then this callable should be referenced to in
_sage_decorating. With my patch, Sphinx then constructs the signature
from this
callable instead.


In the case of an @options decorator, it would be really cool if the
function signature could be modified to show the options, or in the case
of a @suboptions decorator, show the suboptions.  Is there an easy way
to have a decorator change the signature in the docs?  For example,
could we make a _sage_signature attribute that the decorator could
change, and use that for the docs?

Thanks,

Jason


Hi Jason
Ok, I succeeded in writing a slightly less intuitive version of the
patch which allows for something like the suggested for the @options
and @suboptions decorators. For example, the Sphinx-built argument
line for the function sage.plot.contour_plot.contour_plot becomes

sage.plot.contour_plot.contour_plot(f, xrange, yrange, axes=False,
linestyles=None, frame=True, labels=False, plot_points=100,
linewidths=None, colorbar=False, contours=None, fill=True, **options)

However, this does not fix everything at once. For example, the
function sage.plot.contour_plot.implicit_plot accepts two arguments
which are defaulted to None (linewidth and linestyle), so the author
did not care to add them to the options-decorator. Therefore, they
will not show up in any documentation.

If this sounds like what you wanted, I can clean up the code, test it
some more and add a new patch to #9976.




That sounds great!  I've been looking at the decorator patches over the 
last few days, but haven't had time to do a complete review yet.  I hope 
to review them by the deadline for 4.6.


Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: [debian-sage] building a Sage package on Debian

[CJ Fearnley]

On Mon, Oct 04, 2010 at 02:26:39PM -0700, Ondrej Certik wrote:
> On Sat, Oct 2, 2010 at 9:34 AM, CJ Fearnley  wrote:
> >
> > Sympy is only OK (for Sage) up to version 0.6.6.  0.6.7 in sid will break
> > (note from François Bissey).
> 
> It's some problem in Sage vs sympy and it should probably be fixed
> upstream, either in Sage or in sympy. If someone has time to work on
> that, it'd be great.

Has anyone characterized the problem enough to write a bug report?

I don't even know what we should be looking for.

-- 
We are on a spaceship; a beautiful one.  It took billions of years to develop.
We're not going to get another.  Now, how do we make this spaceship work?
  -- Buckminster Fuller

CJ Fearnley|  Explorer in Universe
c...@cjfearnley.com |  "Dare to be Naive" -- Bucky Fuller
http://www.CJFearnley.com  |  http://blog.remoteresponder.net/

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Decorators degrading documentation

[Johan S. R. Nielsen]

On Sep 23, 2:57 pm, Jason Grout  wrote:
> On 9/23/10 7:13 AM, Johan S. R. Nielsen wrote:
>
>
>
> > Hi
>
> >> I find the generic version of the function definitions less than
> >> satisfactory.  I'd guess it would be had to make Sphinx pickup the
> >> more detailed info in these situations?  I'd also guess the decorators
> >> could maybe manipulate the docstring and inject some information based
> >> on the arguments of the decorator?  Either way, could the effect of
> >> these decorators on the documentation be improved?
>
> > I agree that this is completely unacceptable. I have created Trac 9976
> > and
> > written a patch for Sage's custom version of Sphinx. This essentially
> > checks if
> > a function/method to be documented is a decorator by looking for the
> > attribute
> > "_sage_decorating". If a function/method is actually a decorated
> > version of
> > another callable, then this callable should be referenced to in
> > _sage_decorating. With my patch, Sphinx then constructs the signature
> > from this
> > callable instead.
>
> In the case of an @options decorator, it would be really cool if the
> function signature could be modified to show the options, or in the case
> of a @suboptions decorator, show the suboptions.  Is there an easy way
> to have a decorator change the signature in the docs?  For example,
> could we make a _sage_signature attribute that the decorator could
> change, and use that for the docs?
>
> Thanks,
>
> Jason

Hi Jason
Ok, I succeeded in writing a slightly less intuitive version of the
patch which allows for something like the suggested for the @options
and @suboptions decorators. For example, the Sphinx-built argument
line for the function sage.plot.contour_plot.contour_plot becomes

sage.plot.contour_plot.contour_plot(f, xrange, yrange, axes=False,
linestyles=None, frame=True, labels=False, plot_points=100,
linewidths=None, colorbar=False, contours=None, fill=True, **options)

However, this does not fix everything at once. For example, the
function sage.plot.contour_plot.implicit_plot accepts two arguments
which are defaulted to None (linewidth and linestyle), so the author
did not care to add them to the options-decorator. Therefore, they
will not show up in any documentation.

If this sounds like what you wanted, I can clean up the code, test it
some more and add a new patch to #9976.

Cheers, Johan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Sage's C/C++ libraries

[Martin Albrecht]

On Tuesday 05 October 2010, Bill Hart wrote:
> I also think the bit about Magma using an old fpLLL may be out-of-
> date. Damien Stehle recently did quite a bit of work for the Magma
> group. I'm not 100% sure it's been updated in the latest released
> Magma, but I would be surprised to find it hadn't been.
> 
> Not to worry though, Damien has been a great source of help and
> information for Andy Novocin and I as we've been improving our own
> version of fpLLL in FLINT. My understanding is that for certain
> problems at least, the FLINT version of fpLLL will be faster again.The
> developments in LLL are currently pretty hard to keep up with. It's a
> field that is developing at breakneck pace! I imagine FLINT's version
> of fpLLL will be completely outdated within 24 hours of release, LOL
> (yes, we still haven't released it, but we are nearly there)!

Is your LLL a complete (more or less) drop in replacement for fpLLL? Should we 
use this instead of fpLLL in Sage? 

Cheers,
Martin

-- 
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://martinralbrecht.wordpress.com/
_jab: martinralbre...@jabber.ccc.de

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-support] German translation o f the tutorial / Übersetzung des Tutorials in Deutsch

[Minh Nguyen]

Hi,

2010/10/5 Philipp Schneider :
>  Dear Sage community,
>
> Michael Mardaus and I are happy to announce that we have finished
> translating the complete Sage tutorial to German.

Your contribution to the world-wide Sage community is simply awesome!
Thank you very much!


> Now we need the help of as many German speaking users as possible to
> proofread our translation.
> If you happen to belong to this group and have some minutes to speak, we
> would be happy if you could send us corrections or improved formulations.

I have updated the Sage Math Facebook [1] and Twitter [2] pages.
Hopefully more people would be able to help out with reviewing your
translation.


[1] http://www.facebook.com/pages/Sage-Math/26593144945

[2] http://twitter.com/sagemath

-- 
Regards
Minh Van Nguyen

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage's C/C++ libraries

[Bill Hart]

I also think the bit about Magma using an old fpLLL may be out-of-
date. Damien Stehle recently did quite a bit of work for the Magma
group. I'm not 100% sure it's been updated in the latest released
Magma, but I would be surprised to find it hadn't been.

Not to worry though, Damien has been a great source of help and
information for Andy Novocin and I as we've been improving our own
version of fpLLL in FLINT. My understanding is that for certain
problems at least, the FLINT version of fpLLL will be faster again.The
developments in LLL are currently pretty hard to keep up with. It's a
field that is developing at breakneck pace! I imagine FLINT's version
of fpLLL will be completely outdated within 24 hours of release, LOL
(yes, we still haven't released it, but we are nearly there)!

Bill.

On 5 Oct, 10:35, Bill Hart  wrote:
> Just a minor correction. Paul Zimmermann's name is misspelled.
>
> On 5 Oct, 00:48, William Stein  wrote:
>
>
>
> > Hi Sage-Devel,
>
> > "Every copy of Sage includes many free open source C/C++ libraries,
> > which can also be used standalone without Sage. They got into Sage
> > because enough people really cared about using them, and felt it was
> > worth the effort to convince other people that these should be
> > included in Sage. Thus every single library also provides some key
> > functionality to Sage. Thus understanding the main points about these
> > libraries should be of interest to anybody who knows C/C++ who wants
> > to do mathematical computation. Moreover, most of these libraries were
> > written in C/C++ because the authors had already mastered the
> > underlying algorithms, and really wanted an implementation that was
> > extremely fast, often potentially orders of magnitude faster than what
> > they might implement using only an interpreter, such as Python, Maple
> > or Magma." -- for more, 
> > seehttp://sagemath.blogspot.com/2010/10/standalone-cc-libraries-that-are...
>
> > --
> > William Stein
> > Professor of Mathematics
> > University of Washingtonhttp://wstein.org

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Sage's C/C++ libraries

[Bill Hart]

Just a minor correction. Paul Zimmermann's name is misspelled.

On 5 Oct, 00:48, William Stein  wrote:
> Hi Sage-Devel,
>
> "Every copy of Sage includes many free open source C/C++ libraries,
> which can also be used standalone without Sage. They got into Sage
> because enough people really cared about using them, and felt it was
> worth the effort to convince other people that these should be
> included in Sage. Thus every single library also provides some key
> functionality to Sage. Thus understanding the main points about these
> libraries should be of interest to anybody who knows C/C++ who wants
> to do mathematical computation. Moreover, most of these libraries were
> written in C/C++ because the authors had already mastered the
> underlying algorithms, and really wanted an implementation that was
> extremely fast, often potentially orders of magnitude faster than what
> they might implement using only an interpreter, such as Python, Maple
> or Magma." -- for more, 
> seehttp://sagemath.blogspot.com/2010/10/standalone-cc-libraries-that-are...
>
> --
> William Stein
> Professor of Mathematics
> University of Washingtonhttp://wstein.org

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org