#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 | 8726309399d3e77214b98c66f2a093bba925d574
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by dlucas):
Hello,
I made some changes:
- I removed the code, the encoder, the decoder and the channel from the
dictionary `experimental_data`, as this never changes through the tests
for a given benchmark.
- I strengthened how empty benchmarks are managed in addition. Consider
`B1` and `B2` two benchmarks. If:
- `B1` and `B2` are empty, an exception is returned,
- `B1` or `B2` are empty, the empty benchmark is ignored.
This is still under new state as there's some remaining bugs (e.g.
"experimental" warning is called everytime a Benchmark is constructed,
even inside the same session).
--
Ticket URL: <http://trac.sagemath.org/ticket/20526#comment:4>
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.
