continued by the statement:
“Adding 1/2 of the size of a bin to the theoretical contaminated depth enables us to be conservative in order to make sure that the data in the first bin below the contaminated depth hasn't been computed from any contaminated signal.”
However, in the function imosSideLobeVelocitySetQC.m the calculation is:
cDepth = distanceTransducerToObstacle - (distanceTransducerToObstacle * cos(sample_data.meta.beam_angle*pi/180) - nBinSize*BinSize);
preceded by the statement:
“by default substraction of 1/2*BinSize to the non-contaminated height in order to be conservative and be sure that the first bin below the contaminated depth hasn't been computed from any contaminated signal”>
So the documentation and the calculation do not agree.
For me it seems, the latter approach (substraction) is more conservative. What do you think?
Question sent via email on 28/01/2022 to AODN
Need investigation and clarification in the wiki and/or(?) in the code