Helloooooooo !!!
I got permission from Brinkmann and Brendan McKay to add code to Sage. The
> code is written in C.
>
HMmmm... Permission ?.. Which kind ?
The problem we met with Bendan McKay's Nauty is that the license is not
GPL-compatible (because he does not want his software to be used for
killing machines, and the GPL does not allow that). If he agrees to license
his code under some GPL-compatible license no problem, but if he does not
we cannot include it O_o
Non-GPL-compatible Free code can still be used in Sage (like Nauty) but as
an optional package. You can easily install it (sage -i nauty) but you
cannot assume that the users have it.
The code is much faster, about one second compared to one day with current
> Sage.
>
> However, Sage does not give a list of posets, but an iterator over them;
> hence memory requirements are almost none for code that searches for some
> kind of posets.
>
That's cool !
So what should we do with the code? Add something like "algorithm=fast" or
> "format=iterator" -option to Posets(n)?
>
It depends.. If it is (legally) possible to make this code the default one
(i.e. if it is GPL-compatible) then we can just change the default of
Posets(n), and keep the old code as an alternative choice (if we need to
check something specific) or just remove it.
And on the way it would be good to change that:
sage: Posets("What the Hell ?...")
Posets containing What the Hell ?... vertices
Nathann
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
