Closed CameronBodine closed 11 months ago
Yes I think it's how the max range is determined for each chunk.
Check load son or get scan chunk functions.
Fixed it. Need to call _getScanChunkSingle()
when loading sonar data into memory. This function then calls _loadSonChunk
. If not, then the maxPing
isn't calculated and will use the maxPing
in memory, which may be incorrect if the range changes throughout the recording.
Issue with rectification. Looks like an issue with range calculation. I think I have seen this before. Something to do with how PINGMapper handles when auto range changes.