Indeed, chomp is installed but not in the list of "sage -t" optional packages.

$ sage -optional|grep -v not_installed|cut -d. -f1
[package]

arb
bliss
cbc
chomp
cryptominisat
d3js
database_cremona_ellcurve
database_gap
database_odlyzko_zeta
database_pari
database_stein_watkins
database_symbolic_data
extra_docs
gambit
gap_packages
git
guppy
kash3
lidia
lie
lrs
modular_decomposition
mpir
nauty
normaliz
nose
nzmath
ore_algebra
patchbot
plantri
pycryptoplus
python2
pyzmq
qhull
scons
sip
threejs
tides
topcom
zeromq

Vincent

On 14/06/15 10:32, Frédéric Chapoton wrote:
according to #16364, chomp could lead to this kind of things. But it is not
in your list !!

Le dimanche 14 juin 2015 10:29:33 UTC+2, Frédéric Chapoton a écrit :

For binary trees, I have made http://trac.sagemath.org/ticket/18698  that
needs review.

Le dimanche 14 juin 2015 10:19:22 UTC+2, Frédéric Chapoton a écrit :

Indeed, the failure for binary trees should come from canonical labeling.
It would be enough to
change the doctest so that they are no longer sensitive to that.

I am no longer that sure that TOPCOM is the other problem. What other
package is delaing with homology ? chomp ?

Frederic

Le dimanche 14 juin 2015 10:09:23 UTC+2, Nathann Cohen a écrit :

I would suspect that topcom should be responsible for the homology
errors.

No idea for what happens to binary trees. They seem to be reversed
(left-right symmetry ?)

That could be 'bliss'. It becomes the default algorithm to compute
automorphism groups of graphs and canonical representatives. Those
canonical representatives will be different from the previous ones,
though.

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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to