#11340: Make nauty's geng work as a generator
----------------------------+-----------------------------------------------
   Reporter:  rbeezer       |          Owner:  jason, ncohen, rlm
       Type:  defect        |         Status:  needs_review      
   Priority:  minor         |      Milestone:  sage-4.7.1        
  Component:  graph theory  |       Keywords:                    
Work_issues:                |       Upstream:  N/A               
   Reviewer:                |         Author:  Rob Beezer        
     Merged:                |   Dependencies:                    
----------------------------+-----------------------------------------------

Old description:

> Output produced by nauty's geng program can be quite large.  Currently,
> an entire list is created and returned.  The 1,018,997,864 graphs on n=11
> vertices can overwhelm RAM when produced all at once.  This patch
> reorganizes the {{{nauty_geng()}}} command to produce a generator, so
> graphs can be created, tested and then discarded or saved - which would
> be the typical use of this command.  Of course, for smaller values of  n
> it is still possible to quickly build a list from the generator.
>
> This also upgrades the system call, since {{{os.popen()}}} is deprecated
> in Python.
>
> '''Apply:'''
>
>   1.  [attachment:trac_11340-nauty-geng-generator.patch]

New description:

 Output produced by nauty's geng program can be quite large.  Currently, an
 entire list is created and returned.  The 1,018,997,864 graphs on n=11
 vertices can overwhelm RAM when produced all at once.  This patch
 reorganizes the {{{nauty_geng()}}} command to produce a generator, so
 graphs can be created, tested and then discarded or saved - which would be
 the typical use of this command.  Of course, for smaller values of  n  it
 is still possible to quickly build a list from the generator.

 This also upgrades the system call, since {{{os.popen()}}} is deprecated
 in Python.

 '''Apply:'''

   1.  [attachment:trac_11340-nauty-geng-generator-v2.patch]

--

Comment(by rbeezer):

 Replying to [comment:2 ncohen]:
 > I just have a question : what about removing the options which change
 the output, as the method would not be able to cast them to Sage graph ?

 Nathann - thanks for having a look at this.  That's a good point - no
 reason to advertise options that would be harmful.  I had not taken such a
 close look at what I was putting there.

 v2 patch is standalone, it removes these options from the list, and adds a
 bit more commentary about these options.  I also spruced up the doctests a
 bit.  No changes to the code.

 Thanks,
 Rob

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11340#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to