#6641: [with patch, needs work] switch the poset antichains method to use
GenericBacktracker and add antichains_iterator.
---------------------------+------------------------------------------------
 Reporter:  saliola        |       Owner:  saliola       
     Type:  enhancement    |      Status:  new           
 Priority:  major          |   Milestone:  sage-combinat 
Component:  combinatorics  |    Keywords:                
 Reviewer:                 |      Author:  Franco Saliola
   Merged:                 |  
---------------------------+------------------------------------------------
Changes (by ddrake):

  * type:  task => enhancement


Comment:

 I like using the backtracker code, and I'm the one who showed it to Franco
 and said it was all great and stuff...but I think this is "needs work".
 I've done a bunch of testing, and this patch is consistently 30-50% slower
 than the current code. For some things, it was only about 15-20% slower,
 but mostly it's 30-50%. Here's what I tested:

   * antichain posets 5 and 10 elements
   * symmetric group Bruhat order 3, 4
   * chains with 10-14 elements
   * random posets: 100 elements and 500 elements, with probabilities .05,
 .2, and .5. The .sobj files for these are in my home directory on
 sage.math.

 A slowdown might be acceptable if there's a big win in code clarity,
 memory use, ease of doctesting, etc, but I'm not sure we get any of that,
 except maybe the memory usage. Thoughts?

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