#17034: New user interface for orthogonal arrays and a .explain_construction
method
-------------------------------------+-------------------------------------
Reporter: ncohen | Owner:
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.4
Component: combinatorial | Resolution:
designs | Merged in:
Keywords: | Reviewers:
Authors: Nathann Cohen | Work issues:
Report Upstream: N/A | Commit:
Branch: u/ncohen/17034 | 024f0b3bf6f01d2aa4c42151d0ea56ed7fd2fbcd
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
Yo !
> Does the function `largest_available_k`, `explain_construction`,
`OA_build`, `OA_exists` and `OA_is_available` are intended to be used by
programmers? I guess that it is not. So Why not defining them directly as
staticmethod in `OATabThing` (or `OAMainFunctions` that you dislike)...
and about the name, why not `OAPublicFunctions`?
I really don't care about any of those points. Do it if you like, or let
it stay like that.
This being said, I plan on adding new functions to "list all 'k' such that
there exists an `OA(k,n)`", or similar functions for incomplete orthogonal
arrays, and those functions may be used by both developpers and users.
> These are one line functions and it would cost nothing to make them not
call each other.
Why is it a problem if they call each other ?
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/17034#comment:17>
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.
