Missing pO2 samples from CCR download [was: 4.7.8: a couple of questions]

Long, Martin martin at longhome.co.uk
Thu Jun 21 03:26:28 PDT 2018


This is great. See screenshot... the green line.

Great worn Anton, and thanks all for getting this sorted.



On 21 June 2018 at 00:55, Dirk Hohndel <dirk at hohndel.org> wrote:

> Hi Davide,
>
> We just merged the patches from Anton, a new test build should show up in
> https://github.com/Subsurface-divelog/subsurface/releases/tag/continuous
> soon.
> This link always gets you the latest test installer - and sometimes it may
> be
> missing because it's just being built (or because there was an error in the
> build). If that's the case (a) wait 10 minutes and (b) if it's still
> missing, send
> an email to the list so we know to kick it :-)
>
> On Jun 18, 2018, at 9:15 PM, Davide DB <dbdavide at gmail.com> wrote:
>
> I'm sure that this problem will solved.
>
>
> The frustrating part is that it took so long. And that is definitely my
> fault
> because as I said, I didn't pay enough attention to the issue.
>
> As you see my report is dated back on december 2017. I cannot blame
> nobody except my self for being lenient checking my profiles after
> discovering that bug. On the other side I know well how open-source
> projects works. People write code or generally help (like me) for what
> is important for themselves and not so quickly for other things that
> are not so important for themselves. No one gets paid for the work, so
> one cannot force anybody.
>
>
> So true
>
> Hence this bug was thought provoking for me. I've been always a
> minority but with a divecan shearwater controller I thought I was
> mainstream but I was wrong. This bug hit me hard. I have over 60 ccr
> maniacally logged dives with completely wrong or missing pO2 samples.
>
>
> I am reasonably certain that we can rectify this.
>
> Please make a copy of your dive data (simply export them to an XML
> file), open that XML file, and then re-download from the Shearwater.
> In the Download dialog check the two boxes (sorry, English text, I'm
> sure you can figure out the Italian version):
> "Force download of all dives"
> "Always prefer downloaded dives"
>
> With these options checked it should keep all of your other data like
> notes, buddies, etc, but replace the downloaded data with the new
> version which we assume will be corrected with the fix in place.
>
> So this should be reasonably easy to recover from.
>
> A CCR dive without pO2 samples is like a cake with no sugar. If I
> still have them on my Petrel (I never investigated how many profiles
> it stores) I should import everything from scratch into Subsurface and
> compile everything again. Not a nice perspective for the future. Right
> now I'm diving two/three times per week so the count will increase
> rapidly. I've tons of notes, wrecks positions, all dives have GPS
> locations...
>
>
> See above - you should be able to do this without having to manually
> re-edit all of this work!
>
> I think I will use Shearwater desktop for the time being
> and leave old dives in Subsurface. When a complete solution will be
> found I will evaluate how much effort is needed to realign everything
> because I do not see a real solution coming soon.
>
>
> This is where my ignorance shows. I thought Anton's fix solves the problem
> for you. Can you explain in non-CCR diver terms what is still missing?
>
> Anton (and now Aaron) patches are blessed workarounds but  don't solve
> the inner problem:  for some mysterious reason, on some devices we
> cannot use/decode Shearwater data.
>
>
> If someone can extract this as one or two sample dives that show the
> problem and add words that make enough sense to me, I'll reach out
> to Shearwater again to see if they have suggestions. I know I sent them
> one of the earliest exchanges on this topic but neither they nor I really
> understood the problem and it got dropped
>
> Moreover other questions remained unanswered; In one year my unique
> Petrel was identified as 3 different devices with random number of
> sensors. My logbook is a mess and nobody knows the reason.
>
>
> Also something I can ask about if you give me more information.
>
> Frankly speaking I think nobody with a shearwater petrel ccr
> controller knowing in advance this bug  would use Subsurface as their
> logbook. My profiles shows 2,1 bar of pO2 at 80 meters. Nothing you
> would show to anybody.
>
>
> That would be, err, unsafe. Even I know that.
>
> Months ago, given your good relationship with Shearwater, I warmly
> recommended to contact them privately asking info on this nasty
> behaviour of some devices.
>
>
> I will look again if there are more emails that I've missed.
>
> Again, all I can do is apologize. You've done so much for Subsurface
> and we have not taken good care of you. I hope you'll consider the
> option I outlined above.
>
> All the best
>
> /D
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180621/72870ce3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_062118_112422_AM.jpg
Type: image/jpeg
Size: 476225 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180621/72870ce3/attachment-0001.jpg>


More information about the subsurface mailing list