Hello Yes test vectors could be useful, but it's not easy since a lot of values are floating point. Also, intermediate values and model internal parameters.
I mean, small ones, just enough data to feed the analysis steps and produce output, 320 samples if I understand correctly. I have started to write a document after looking at Steve's java code, It seems to be a close translation from C code. I will have a look at your C code in the coming days but I have a busy DIY schedule. I will ask questions on this list. Thanks for the support. Sebastien Le 20/03/2017 à 18:16, David Rowe a écrit : > Hello Sebastien, > >> I think that writing a specification myself is the best possible action to >> achieve this goal. > I'm happy to advise on teh structure and review it for you. As an > intermediate step, more "how it works" documentation would be useful. > > A way to verify implementations would be useful, like test vectors of > the codec input/output and internal processing steps. I do quite a lot > of that when I port algorithms from Octave to C. > > Cheers, > > David > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
