#91 Non-narrow-sense Reed-Solomon and Erasure Decoding

Next_Release
closed
None
4
2013-05-24
2012-12-11
No

After a lot of discussion, I commit a patch against current SVN that implements non-narrow-sense Reed-Solomon-Codes with narrow-sense parameter b != 1. The case b=0 is used e.g. in IEEE802.16d RS code.
Furthermore, the patch adds erasure decoding while maintaining backward compatibility.

For further info, see help thread: 802.16d Reed-Solomon

Discussion

  • Stephan Ludwig

    Stephan Ludwig - 2012-12-11

    revision 1923

     
  • Bogdan Cristea

    Bogdan Cristea - 2012-12-13

    Hi Stephan

    Just made an update from trunk and the current revision is 1919. Where is revision 1923 ?

     
  • Stephan Ludwig

    Stephan Ludwig - 2012-12-14

    Hi Bogdan,

    that is the revision shown to me by SVN. But I also noted the day before yesterday that the SVN repository shown by the sf page/code browser was messed up and showed revisions up to rev. 1919.

    My history shows the following revisions messages
    1923 - donludovico: added feature #91: erasure decoding with Reed-Solomon codes and non-narrow-sense RS codes. Added unit test cases that checks both features.
    1922 - mirsadcirkic: Created a proper test executable and its reference for the modulator_nd class.
    1921 - mirsadcirkic: Finished the new and fast complex-valued demodulators.
    1920 - eric_g_larsson: corrected degree distributions in tutorial
    1919 - cristeab: corrected cmake file for gtests

    Can't you see them?

     
  • Bogdan Cristea

    Bogdan Cristea - 2012-12-16

    Hi

    I can see your commits in the svn browser, but not when I do a
    svn checkout --username=cristeab svn+ssh://cristeab@svn.code.sf.net/p/itpp/svn/itpp/trunk trunk

    I am still at revision 1919. I will ask for help sourceforge admins.

    Bogdan

     
  • Bogdan Cristea

    Bogdan Cristea - 2012-12-20

    Hi Stephan
    Could you check again your commit. It seems that it does not appear in the code browser and that the last commit is indeed 1919.
    regards
    Bogdan

     
  • Stephan Ludwig

    Stephan Ludwig - 2012-12-21

    Hi Bogdan,

    I newly checked out the repository by using
    svn co https://itpp.svn.sourceforge.net/svnroot/itpp/itpp/trunk itpp_svn
    on Linux and I have all revisions up to 1923 including my changes.

    To me it seems as if there were two different repositories, one that stopped at 1919, which is visible online at
    https://sourceforge.net/p/itpp/svn/1919/tree/
    and the one that I used that went to 1923 meanwhile. erik_g_larsson and mirsadcirkic also committed on that repository rev. 1920-1922.

    I cannot check-out the online repository by using the commands given on that web page:
    svn checkout --username=donludovico svn+ssh://donludovico@svn.code.sf.net/p/itpp/svn/trunk itpp-svn
    -> URL ... does not exist
    The same for read-only and http access.

    What did the SF admins answer to that problem?

    I have no idea how to assist you in finding the cause of that problem. If I can do anything more, please let me know.

    Regards
    Stephan

     
  • Stephan Ludwig

    Stephan Ludwig - 2012-12-21

    OK, I changed my command to
    svn checkout --username=donludovico svn+ssh://donludovico@svn.code.sf.net/p/itpp/svn/itpp/trunk itpp-svn (note the second itpp after /svn/) and in deed have revision 1919 as latest.

    But what repository do we have on https://itpp.svn.sourceforge.net/svnroot/itpp/itpp/trunk ? Which one is relevant?

    We should change this to be the same. And the links on https://sourceforge.net/p/itpp/svn/1919/tree/ should be corrected such that they have the second itpp in their path.

    How can we do that, Bogdan?

    /stephan

     
  • Bogdan Cristea

    Bogdan Cristea - 2012-12-22

    Hi

    It seems that this url https://itpp.svn.sourceforge.net/svnroot/itpp/itpp/trunk is deprecated and should not be used. I have merged the changes from the old url to the new repository (https://svn.code.sf.net/p/itpp/svn/itpp/trunk). Also the displayed checkout url has been corrected and it should work now.

    Please update your repository settings to the new url and check that everything works as it should after the merge. It is a problem that the old url can be still used, but the changes don't appear in the new repository, I'll see with site admins for that (https://sourceforge.net/p/forge/site-support/2023).

    regards
    Bogdan

     
  • Bogdan Cristea

    Bogdan Cristea - 2013-05-23
    • status: open --> accepted
     
  • Bogdan Cristea

    Bogdan Cristea - 2013-05-24
    • status: accepted --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks