When processing very small chunks of data nFrames is set to zero. However, there is a discrepancy in how the dimensions of the output matrix are set in the processChunk() method from crosscorrelationProc vs. the function frameData().
processChunk() uses max(1, nFrames) while frameData() uses max(0, nFrames) for the first dimension of the output matrix. This is only relevant when the chunk is very small resulting in nFrames < 1.
This changes processChunk() to set the first dimension of the output matrix using max(0, nFrames) the same way as done in frameData() when padding is switched off.
When processing very small chunks of data nFrames is set to zero. However, there is a discrepancy in how the dimensions of the output matrix are set in the
processChunk()
method fromcrosscorrelationProc
vs. the functionframeData()
.processChunk()
uses max(1, nFrames) whileframeData()
uses max(0, nFrames) for the first dimension of the output matrix. This is only relevant when the chunk is very small resulting in nFrames < 1.This changes
processChunk()
to set the first dimension of the output matrix using max(0, nFrames) the same way as done inframeData()
when padding is switched off.