#9894: Group cohomology spkg, version 2.1
----------------------------------------------------------------------------+
   Reporter:  SimonKing                                                     |   
    Owner:  tbd                                
       Type:  enhancement                                                   |   
   Status:  needs_review                       
   Priority:  major                                                         |   
Milestone:  sage-4.6                           
  Component:  optional packages                                             |   
 Keywords:  modular group cohomology solaris t2
     Author:  Simon King                                                    |   
 Upstream:  N/A                                
   Reviewer:                                                                |   
   Merged:                                     
Work_issues:  Is the code independent of the computer's newline character?  |  
----------------------------------------------------------------------------+

Comment(by SimonKing):

 Replying to [comment:22 kcrisman]:
 > > and `./sage -f` it again, and hopefully all will be well in the
 morning.  I have to say, five hours to install and test - that's quite an
 spkg, quite the computation!

 Ouch! Five hours is really much. On my desktop computer, the total time
 for the tests is {{{2812.09 sec}}}, and installation takes maybe 10
 minutes.

 By the way, the test skript runs *all* doctests. So, it always includes
 the ones marked long. Perhaps in the next version I should provide the
 possibility to only run the short tests.

 But what is the point of having tests that take so long? This is due to
 the fact that often I was not able to find smaller examples that show the
 benefit of a particular method.

 How to find the doctests? Well, you had a timeout in pGroupCohomology. So,
 you are in the lucky situation that the test is in a Python file, namely
 (if you untar'd the package) in
 {{{p_group_cohomology-2.1/src/pGroupCohomology/__init__.py}}}. You could
 run {{{sage -t -verbose -long}}} on that file (that wouldn't work for the
 Cython files). Using the "verbose" option would show exactly what part of
 the test takes so long.

 It is surprising to me that the two lists in the little {{{split}}} test
 are equal. But anyway, I think {{{[t.strip() for t in
 singular.eval('print(%s)'%I.name()).split(',')]}}} is cleaner than
 {{{singular.eval('print(%s)'%I.name()).split(',\n')}}}

 Cheers,

 Simon

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9894#comment:25>
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