#15310: Wilson's construction of Transversal Designs/Orthogonal Arrays/MOLS
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.2
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
combinatorics | Work issues:
Keywords: | Commit:
Authors: | d74341411288315f13da3d4383e515b884ba7440
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/15310 |
Dependencies: |
#15287, #15431 |
-------------------------+-------------------------------------------------
Comment (by vdelecroix):
Hello,
Replying to [comment:31 ncohen]:
> > This is an important issue I started to discuss with Nathann in
#15431... and I am in favour of implementing all the code with OA
conventions.
>
> I hate useless abstraction. Look, for the moment there is some code left
in the constructor of MOLS but it will be removed soon, by the TD
construction. I am against forcing .... myself .... to translate every
construction of MOLS/TD into OA, because implementing code like that is
extremely tricky. I just spent two full days (no joke) because I
misunderstood one line of a construction, and I was helped by the guy who
actually first wrote it. I implemented code like #14562 and you wouldn't
believe the number of times I was convinced that the construction was
wrong. Look at the code, really. There is one line among those at which I
stared for 30 solid minutes. Only this line, nothing else. That's no joke,
and having to translate constructions from unclear papers can mean a lot
of headaches while you debug.
True. But on the other hand
- it is very hard to see what belongs to the OA/TD/MOLS and in few times
it will be hard to understand what happens to your input
- the `EmptySetError` raised in OA would also makes sense inside the TD.
It is better to do trivial check on the input before digging for a
construction. So if we want efficient code, we will have to copy paste all
sanity checks
>> look at ticket #16272. I will add those references to the description.
If you have other non-existence theorems please post them on #16272.
>
> Yep, non-existence results are good and the Unknown truth value really
helps here. We could also implement something funny : if a guy ever needs
to say in a paper that "this design exists", we could have Sage return
some information on the path used by the constructions.
>
> I mean. We can say where the basic constructions come from (we have the
references), and we can also say how the recursive constructions are
applied. Sooooo what we have is a way to say that this design can be
obtained by applying this or that constructions in this way,using the
following elementary blocks whose existence has been proved there and
there. Really, we can do that `:-)`
I like it. But I agree that it can be implemented later on.
> But that's nice things for later. What we need to do is beat the
Handbook's MOLS table while providing the actual MOLS. That would be
something we could boast about `:-P`
Nice challenge! You want it to be ready for next week?
--
Ticket URL: <http://trac.sagemath.org/ticket/15310#comment:34>
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.
