Correcting depth anomaly
Correcting depth anomaly
On two of 19 imported dives I have two dives with depth spikes down to 641.9m. As you might be able to guess these are anomalies. The software must recognise them as such as it summarises the correct maximum depth for the dives. Is it possible to manually edit these anomalies out to correct the profile?
Re: Correcting depth anomaly
Hi,
It is not possible to edit profile data directly on the iPhone/iPad using Dive Log (although it is possible to do using some of the compatible desktop applications).
Could you provide a few details about how you downloaded your dive computer (on a desktop app or directly using Dive Log via Bluetooth LE) and which dive computer you are using? There are a few dive computers with particularly basic communication protocols that can produce data errors when downloading that can't be detected (due to the fact that there is no error detection in their download protocols) but generally, downloading the computer again will get the data correctly (you can download the dives and import them in such a way that just the profile data is replaced). I can prove more information about the best approach once I know which computer you are using and how you are downloading it.
Also, if you want, I'd be happy to edit the anomalous data from your profiles if it comes to that. Please feel free to contact us directly via email at our support email address (support 'at' moremobilesoftware 'dot' com) and we can work through the details for your specific case.
Each dive computer is different and some of them prove the maximum depth separately where we need to calculate it from the profile for others. So your maximum depth may be correct because the dive computer provided it's notion of the maximum depth. We don't attempt any data analysis of the downloaded data in the profile during download.
Cheers,
Greg
It is not possible to edit profile data directly on the iPhone/iPad using Dive Log (although it is possible to do using some of the compatible desktop applications).
Could you provide a few details about how you downloaded your dive computer (on a desktop app or directly using Dive Log via Bluetooth LE) and which dive computer you are using? There are a few dive computers with particularly basic communication protocols that can produce data errors when downloading that can't be detected (due to the fact that there is no error detection in their download protocols) but generally, downloading the computer again will get the data correctly (you can download the dives and import them in such a way that just the profile data is replaced). I can prove more information about the best approach once I know which computer you are using and how you are downloading it.
Also, if you want, I'd be happy to edit the anomalous data from your profiles if it comes to that. Please feel free to contact us directly via email at our support email address (support 'at' moremobilesoftware 'dot' com) and we can work through the details for your specific case.
Each dive computer is different and some of them prove the maximum depth separately where we need to calculate it from the profile for others. So your maximum depth may be correct because the dive computer provided it's notion of the maximum depth. We don't attempt any data analysis of the downloaded data in the profile during download.
Cheers,
Greg
Re: Correcting depth anomaly
Appreciate the help and I've emailed you. 
Re: Correcting depth anomaly
Thanks!
We've received your email and will get this sorted out ASAP and get back to you.
Cheers,
Greg
We've received your email and will get this sorted out ASAP and get back to you.
Cheers,
Greg