#20526: A benchmarking tool for linear codes
-------------------------------------+-------------------------------------
       Reporter:  dlucas             |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-7.2
      Component:  coding theory      |   Resolution:
       Keywords:                     |    Merged in:
        Authors:                     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/dlucas/benchmarking_tool         |  0ab93ecbf861c585b83bb162493afcaf5a2032c8
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by dlucas):

 Hello,

 Here's a change log for this ticket:

 - I removed `encoder` from this class. One cannot pass an encoder to a
 benchmark anymore, and all related methods have been deleted. Instead, I
 replaced the old call `Benchmark(E, D, Chan)` by `Benchmark(C, D, Chan)`.

 - Adding two empty benchmarks now returns an empty benchmark and no longer
 an exception.

 - I added better messages in case one tries to manipulate an empty
 benchmark: for instance. calling `Benchmark.run()` now returns a proper
 message which explains that nothing will be done.

 - I refined the notion of "success rate". It now considers decoding errors
 (when the decoder fails at returning anything) and decoding failures (when
 the decoder returns a codeword which is not the expected one). I also
 enhanced `decoding_success_rate`, which now allows the user to select
 between success rate wrt. failures or errors.

 - I globally improved the documentation.

 One problem remains: the experimental warning triggered by the decorator
 `@experimental` activates every time one creates a benchmark, which is
 annoying and also breaks all my doctests.
 This is quite weird as the
 
[http://doc.sagemath.org/html/en/reference/misc/sage/misc/superseded.html#sage.misc.superseded.experimental
 documentation for this decorator] says it will only be triggered
 once/session.
 Still investigating on this...

 David

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

Reply via email to