lairdb
Contributor
- Messages
- 710
- Reaction score
- 221
(Shearwater Cloud for iOS 2.11.3)
I've been working on using SurfGF and GF99 more consciously, which includes noting in my log what I call "EndGF" -- the GF99 when I reach the surface. (As a possible proxy for decompression stress.*)
The (minor) bug I'm seeing in the iOS version of Shearwater Cloud is that it won't display the last couple of data points; it cuts the chart off while there are still surface data points to display.
Here's an example. First, from Desktop. You can see it's decided the dive length is 50m31s, but it is displaying the 50m40s datapoint, which is the first one actually at 0.0ft.
In fact, it will actually display one further datapoint:
...where you can see that 10 seconds later the GF99 has already declined 5%. This is, in fact, the last datapoint shown in the UDDF export:
On SC for iOS, though, the last displayable datapoint is the 50m30s datapoint:
Although it almost looks as though there's one more datapoint available, no amount of precision touching will get the popup to appear any later than 50m30s.
(Told you it was a minor bug.)
CR: iOS app should display all recorded*** datapoints, or at least the same ones displayed by the Windows application.
(I don't really expect @Shearwater to respond here; I'm planning on putting this into an email to them -- but I'm curious if others have noticed and perhaps found a workaround on iOS.)
Edit to add: Not 5 minutes later, I found another highly relevant thread that included a screenshot showing that there's a display of "End Surface GF" available -- I've never noticed that. Interestingly, it's the GF from the 50m50s datapoint, which is down 5% from the 50m40s dp that first recorded 0 depth.
--
(*See discussions at
scubaboard.com
scubaboard.com
scubaboard.com
...and numerous others.**)
(**Incidentally, if anyone knows an easy way to extract max(SurfGF), please let me know; I'd like to be looking at that as well. It's not in the ui, and it's not in the UDDF or SW export. Subsurface displays a (calculated) SurfGF on its chart, but that's cumbersome.)
(***The SW XML export actually has even more post-dive datapoints; it runs all the way to 52m00s. Unlike the UDDF export, it doesn't include <gradientFactor> in the datapoints, though it does include <sac>, <gasTime>, and some other odds and ends.)
I've been working on using SurfGF and GF99 more consciously, which includes noting in my log what I call "EndGF" -- the GF99 when I reach the surface. (As a possible proxy for decompression stress.*)
The (minor) bug I'm seeing in the iOS version of Shearwater Cloud is that it won't display the last couple of data points; it cuts the chart off while there are still surface data points to display.
Here's an example. First, from Desktop. You can see it's decided the dive length is 50m31s, but it is displaying the 50m40s datapoint, which is the first one actually at 0.0ft.
In fact, it will actually display one further datapoint:
...where you can see that 10 seconds later the GF99 has already declined 5%. This is, in fact, the last datapoint shown in the UDDF export:
XML:
<waypoint>
<cns>4</cns>
<calculatedpo2>0.22</calculatedpo2>
<depth>0</depth>
<divetime>3050</divetime>
<tankpressure ref="T1">7074023.5</tankpressure>
<tankpressure ref="T2">6301810.5</tankpressure>
<tankpressure ref="T3">56247452</tankpressure>
<tankpressure ref="T4">56247452</tankpressure>
<temperature>296.15</temperature>
<gradientfactor>63</gradientfactor>
<nodecotime>5940</nodecotime>
</waypoint>On SC for iOS, though, the last displayable datapoint is the 50m30s datapoint:
Although it almost looks as though there's one more datapoint available, no amount of precision touching will get the popup to appear any later than 50m30s.
(Told you it was a minor bug.)
CR: iOS app should display all recorded*** datapoints, or at least the same ones displayed by the Windows application.
(I don't really expect @Shearwater to respond here; I'm planning on putting this into an email to them -- but I'm curious if others have noticed and perhaps found a workaround on iOS.)
Edit to add: Not 5 minutes later, I found another highly relevant thread that included a screenshot showing that there's a display of "End Surface GF" available -- I've never noticed that. Interestingly, it's the GF from the 50m50s datapoint, which is down 5% from the 50m40s dp that first recorded 0 depth.
--
(*See discussions at
What's your SurfGF and how does it compare to your (Rec) GFHi?
From what I see with my limited data, is that meandering/slow ascents (even on square-like profiles) have a large effect on reducing SurfGF (of the leading tissue) and whilst NDL has an effect, it seems it's not as large as I thought it would be. I've enjoyed watching and learning the behaviour...
Recreational Ascent Rate in the last 15 feet
With the advent of Surf GF, and threads like this one: What's your SurfGF and how does it compare to your (Rec) GFHi? , I think it's time to have another survey! :D Personally, having looked at the heat maps and the change in offgassing on my Perdix in the last 15 feet, I have markedly slowed...
Question about using SurfGF...
SurfGF tells me my GF if I were to be instantly transported to the surface. It was my original assumption that that value represented a theoretical maximum GF value since because in reality, as I ascend, I would be off-gassing during the ascent so the actual GF that I would have after surfacing...
(**Incidentally, if anyone knows an easy way to extract max(SurfGF), please let me know; I'd like to be looking at that as well. It's not in the ui, and it's not in the UDDF or SW export. Subsurface displays a (calculated) SurfGF on its chart, but that's cumbersome.)
(***The SW XML export actually has even more post-dive datapoints; it runs all the way to 52m00s. Unlike the UDDF export, it doesn't include <gradientFactor> in the datapoints, though it does include <sac>, <gasTime>, and some other odds and ends.)
