#15438: Fix elias_upper_bound
---------------------------------+----------------------------
Reporter: pmueller | Owner: pmueller
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-5.13
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+----------------------------
Comment (by ppurka):
Replying to [comment:7 pmueller]:
> I prefer a true but trivial bound instead, so that one does not have to
care about an allowed choice of parameters.
For `codesize_upper_bound`, I think it would be fine to return a trivial
bound that should be valid in all ranges of the minimum distance. But not
for the specific bounds such as `elias` or `plotkin` - those are really
''undefined'' for certain ranges of parameters.
In fact, the Elias bound should be valid till `d <= (q-1)/q * n. The
Plotkin should then take over from there since it needs `d > (q-1)/q * n`.
So, there shouldn't be any range for which the trivial bound `q^n` is
required. If it is being required, then the bounds need to be fixed.
> > I think the order of those commands should be fixed once and for all.
And a `warning` printed for a year (that is the usual period for
deprecation, but we can't deprecate anything here).
> I strongly disagree! If we change the order of arguments without
changing the function names, then code which was correct will become
incorrect in future versions of Sage. I just see another problem: In
elias_bound_asymp(delta, q) we *first* have d (via delta) and then q,
while in elias_upper_bound(n, q, d) it is the other way around. So maybe
we drop the redundant *upper* in the function names, and replace
elias/plotkin/etc_upper_bound(n, q, d) by elias/plotkin/etc_bound(n, d,
q). Then the naming is consistent with the asymptotic and the delsarte
functions.
Well, one way is to keep the current commands and put some warnings. Your
suggestion however seems good. We can name some new functions and
deprecate the old functions. The old functions can be removed after the
deprecation period is over.
--
Ticket URL: <http://trac.sagemath.org/ticket/15438#comment:8>
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/groups/opt_out.
