-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frozenbits_generator_GA #12
Comments
Why would the frozen bits has anything to do with info bits? If you were to seek help here or aff3ct/aff3ct repo, clarify your question, show the community that you have searched the Google and precious closed issues, and attempted to do something, e.g. attach some code you were working on. Vague and disrespectful questions will only get the same answers in return. |
I am very sorry. You have mistaken the tone of my question. In all the research papers I have gone through so far, show that the frozen bits generated has a size N-K .But according to the code I can see that the size frozen bits generated is N. Could you please help me on how the encoding process has happened. |
Hi @Aishusiva, You're right, the number of frozen bits is N-K but in AFF3CT, we represent the frozen bits with a vector of size N. The idea is to have the position of the frozen bits in the codeword (N bits). When a value of the vector is I hope it helps. |
Thanks a lot for the clarification. |
How does the function Frozenbits_generator_GA produce the same set of frozen bits for all the input message bits?
The text was updated successfully, but these errors were encountered: