# Access Ping360 data for post processing, Python

**URL:** <https://discuss.bluerobotics.com/t/access-ping360-data-for-post-processing-python/10416>\
**Category:** Ping Sonar Devices\
**Tags:** sonar, ping360\
**Created:** [August 12, 2021, 1:31pm UTC](https://discuss.bluerobotics.com/t/access-ping360-data-for-post-processing-python/10416 "2021-08-12T13:31:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [August 17, 2021, 11:16pm UTC](https://discuss.bluerobotics.com/t/access-ping360-data-for-post-processing-python/10416/5 "2021-08-17T23:16:37Z")

</div>

> [@EliotBR](#):
>
> > [@Winter](#):
> >
> > am I correct in assuming that the intensity signals are the volumetric backscattering strength in decibel? (usually referred to as “S\_v” in fishery acoustics literature).
> 
> I’m actually not certain what the intensity signal measurement unit is (I suspect it may just be the ADC value from the measured voltage of the transducer). I’ve asked about it internally and will get back to you when I’ve got a response 🙂

Update on this, the returned intensity data is in fact from the measured voltage, and we don’t have a known/calibrated conversion between the measurement and a physical quantity/unit of intensity. The transducers we use are custom, and the amplification circuitry involved for receiving further complicates a potential theoretical estimate.

I’m told we’re aiming to get experimental calibration data, which should include the relevant conversion factors and also map out the transmit and receive profiles across direction and sound frequency, but there isn’t yet a definitive timeline on when that will be completed 🙂

---

_[View the full topic](https://discuss.bluerobotics.com/t/access-ping360-data-for-post-processing-python/10416)._