Hello Everyone,
I have gone through the gr-fec API and the relevant code for the GSoC project "Standardized high throughput FEC Code". I have also looked at the past projects which implemented other FEC Codes along with their VOLK Optimizations.
I intend to focus on the implementation of standardized LDPC Codes for my project.
I wanted to know if the community has any particular modifications or additions in mind with respect to LDPC Codes in gr-fec. I would then look into them and start working on my proposal.
Thanking You,
Mayank.
On Thu, Mar 7, 2019 at 10:17 PM Mayank Jhamtani <mayank26.bitsgoa@gmail.com> wrote:
Hi Johannes,Thank you for your detailed response.I would look into the two approaches you suggested, and get back once I have something concrete.I also welcome any suggestions as to which approach might be more suitable.-Cheers,MayankOn Thu, Mar 7, 2019 at 2:42 PM Johannes Demel <demel@ant.uni-bremen.de> wrote:Hi Mayank,
I'm glad you're interested in optimized codes.
There are quite a lot of comms standards out there. They all come with
their standardized codes. Unlike their general definition, standards use
a small subset of all possible configurations a code might have.
e.g. in general frozen bits in polar codes just need to have fixed
values. In practice, frozen bits are all set to '0'. This simplifies
decoders. Also, you could identify possible decoder functions that would
benefit from specialization. This might be facilitated via templates or
different implementations. Probably a combination of different
techniques will be applied.
This project may be approached in 2 different ways. Others may comment
on these options.
1. Choose a specific standard code and implement it such that encoder
and decoder exhibit maximum throughput/ minimum latency.
2. Find high performance implementations of standard codes and integrate
them into the FECAPI. Make sure they seamlessly integrate into FECAPI.
This might encompass discussions on how to integrate these
implementations. Technical issues might come up but also license issues.
Also, it would be challenging to add multiple new dependencies to GNU Radio.
In most cases FEC in comms standards include:
- encoder
- decoder
- puncturing
- interleaver
All in all, an information word goes into the encoder and a 'rate
matched' codewords is emitted. On the decoder side a received vector
represented as LLRs goes into the decoder and a decoded information word
goes out.
Clearly, the focus should be on the decoder in terms of performance
because we expect this component to be the one with the heaviest load.
Though, the other parts of the FEC standard should be implemented as well.
Cheers
Johannes
Am 06.03.19 um 18:52 schrieb Mayank Jhamtani:
> Hello all,
> My name is Mayank, and I am interested to participate in GSoC'19 as a
> student.
>
> I would want to work on the project "Standardized High Throughput FEC
> Codes". This project interests me because I have been studying coding
> theory for the past two years, and I would love to work on implementing
> the same. I also have decent experience of coding in C++.
> I am currently familiarizing myself with GNU Radio, and the gr-fec API
> in particular.
>
> Also, I would be grateful if someone could clarify the exact expected
> outcomes of the project idea, or give any other useful pointers, so that
> I can better orient my efforts.
>
> Regards,
> -Mayank
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
No comments:
Post a Comment