...another point: I tried to understand as much as possible from http://abelian.org/ebnaut/results.shtml 16k is convincing. What about 32K? No significant additional advantage or not practicable for
No reason why not. I can put one together by combining a couple of good rate 1/8 K=21 polynomials. I'll try to do that this week. They take a little while to test and measure performance. The excuse
A quick trial of 16K19: I just put together my best two rate 1/8 K=19 codes to make a 1/16 K=19 polynomial set and ran a comparison test using 12 char messages at -0.5dB Eb/N0. Decode success rates w
The search for a good rate 1/16 K=19 code continues without success. I improved the code search program. It examines 2 million polynomials per CPU second. After some hundreds of CPU hours it finds ab
One thing is certain. Both Paul and Stefan know FAR more than most of us! Keep up the great work "pushing the boundaries". 73s Roger G3XBM On 6 March 2017 at 21:35, Paul Nicholson <[email protected]
