#13546: Bug in is_perfect
-------------------------------------------+--------------------------------
Reporter: azi | Owner: jason, ncohen, rlm
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-5.7
Component: graph theory | Resolution:
Keywords: is_perfect,graph theory | Work issues:
Report Upstream: N/A | Reviewers: Jernej Azarija,
Sébastien Labbé
Authors: Nathann Cohen | Merged in:
Dependencies: #8952 | Stopgaps:
-------------------------------------------+--------------------------------
Comment (by azi):
Eeeh... I should refrain from posting things late at night - I am writing
confusing stuff...
Anyhow. I am aware of the sparse6 issue but in my opinion that is an issue
of how we currently handle sparse6 strings! So if we enforce the
simplicity rule in is_perfect then at some point someone will perhaps get
annoyed and want an option of the form
{{{
Graph('sparse6_string',force_simplicity=True)
}}}
instead of Sage having to guess if the user sent a sparse6 graph that was
converted to a non-simple graph etc... Or perhaps the Graph() constructor
could check if the resulting graph is simple and automatically flag it as
such.
Thank you for taking my comment into relevance!
As far as I see, the patch need not remove loops and multiple edges from
the complement now?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13546#comment:23>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
