#19221: Some new (n,2^k,1)-BIBD
-------------------------------------------------+-------------------------
       Reporter:  ncohen                         |        Owner:
           Type:  enhancement                    |       Status:
       Priority:  major                          |  needs_info
      Component:  combinatorial designs          |    Milestone:  sage-6.9
       Keywords:                                 |   Resolution:
        Authors:  Nathann Cohen                  |    Merged in:
Report Upstream:  N/A                            |    Reviewers:  Vincent
         Branch:                                 |  Delecroix
  78d008dce6ad2f415dc703861b529f6fa0e95841       |  Work issues:
   Dependencies:                                 |       Commit:
                                                 |     Stopgaps:
-------------------------------------------------+-------------------------

Comment (by dimpase):

 Replying to [comment:25 ncohen]:
 > > but `labels` are meant to be user-defineable
 >
 > Whaaaat? I don't know what makes you think that. `labels=False` makes
 sense to me. There is nothing in that word that says 'user-defineable' or
 anything. If you want to change the labels, `.relabel` is there for you.

 well, `.relabel()` does relabel things in a user-defineable way (at least
 it has this option).



 >
 > > Calling a set of labels chosen by the implementation `labels` is
 unhelpful and uninformative, to say the least.
 >
 > It just means that the structure is not integer-labelled. Any way I
 cannot care less: if you chose to overlook that all our functions will
 have as many ways to call the same thing (labels, coordinate, ... do you
 see this end?) then I will not fight again, it's your win anytime because
 you are the reviewer and by Sage's laws you can make my life hell until I
 give up.

 I merely say that `coordinates` is more informative name for this
 parameter.
 Do you agree? If yes, I will change this on #19226, to make it uniform
 with !ProjectiveGeometryDesign.


 >
 > So add a commit.

 this ticket is closed, as you know. How about #19226?

 >
 > > > If I remember correctly, the explanation to that lies in the running
 times.
 > > Indeed, it's 50 times faster on PG(2,16). I wonder why...
 >
 > Surprising. Might be because we are multiplying the elements of the
 ground set using Sage, which is always slow for ... well, everything.
 Perhaps the way `PG` is called changed in the meantime, I do not remember.
 If you feel bad about it you can write a ticket, it's always good to see
 speed improvements.

 probably it's because it handles the case of 1-dimensional subspaces by
 generic code, which does linear algebra on matrices...

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

Reply via email to