Hi, If the goal is to identify regressions, comparing the previously generated output data to the output of the changed code is sufficient. And for this we can simply compare the value by value difference since beside rounding errors the output should be very close. For that a simple value by value difference should be good enough.
For general work a quality check by comparing input and output properties like Glen suggested would be nice. Danilo > Am 17.09.2016 um 07:53 schrieb glen english <g...@cortexrf.com.au>: > > My video compression work tells me we almost need something else rather > than a bit for bit compares. > > something like a SN or difference merit > > Anyone familiar with video compression will understand this concept . > We would do an encode- decode and then look at the RMS, peak, and > various other stats difference between the input and output . > > The tools would line up / correlate the frames to get the compare > occurring at the right temporal location. > > On 17/09 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2
------------------------------------------------------------------------------
_______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
