#19712: strongly_regular_graph() crashes when mu=0
-------------------------------------+-------------------------------------
       Reporter:  ncohen             |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  critical           |    Milestone:  sage-6.11
      Component:  graph theory       |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Nathann Cohen,     |    Reviewers:
  Dima Pasechnik                     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:  public/19712       |  5bb551e4585722cb1be2fcb20c172b6f81262bae
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------
Changes (by {'newvalue': u'Nathann Cohen, Dima Pasechnik', 'oldvalue': 
u'Nathann Cohen'}):

 * priority:  major => critical
 * author:  Nathann Cohen => Nathann Cohen, Dima Pasechnik


Old description:

> Reported by Georgi Guninski:
>
> {{{
> sage: graphs.strongly_regular_graph(10,2,1)
> <crash>
> }}}
>
> This is because of a "<whatever>%0" somewhere in the code. Which should
> not happen, as in a strongly regular graph we have mu>0.
>
> Nathann

New description:

 Reported by Georgi Guninski:

 {{{
 sage: graphs.strongly_regular_graph(10,2,1)
 <crash>
 }}}

 (and more of these).

 This is because of a "<whatever>%0" and "<whatever>/0" in the code in
 several places. Which happened, as it was confusion over the corner cases
 mu=0 and mu=k.

--

--
Ticket URL: <http://trac.sagemath.org/ticket/19712#comment:21>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to