#15431: Transversal Design TD(6,12)
-------------------------+-------------------------------------------------
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: | 47ffd9153b474fbf2b4f560e726b0cfdbcb0af53
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/15431 |
Dependencies: |
#15287 #15368 |
-------------------------+-------------------------------------------------
Comment (by vdelecroix):
Thank you for the explanations. But still, with your definition given in
the doc of TD, the functions TD and OA return particular cases of
transversal desings (since you do not let the user choose his sets V1, V2,
...). I found it very confusing having two functions basically doing the
same job.
Could you state in both documentations that an OA is a TD and vice versa ?
Could you put in the doc of TD that you choose to use the sets V1 =
[0,n-1], V2 = [n,2n-1], ... and it would be even nicer inside the doc to
have examples involving:
{{{
sage: oa_to_td = lambda x: return [[i*n + c for ...] ...]
sage: td_to_oa = lambda x: return [[(j-c)//n for ...] ...]
}}}
That way, it is clear that is just a convenience for the programmer.
--
Ticket URL: <http://trac.sagemath.org/ticket/15431#comment:18>
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.
