SW Cloud - improvements, feature requests, fixes etc. Let's help make it better.

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Concur with @Macan above. Just downloaded my week's dives from Key Largo, and the difference is quite apparent on the deep wrecks.
The 35% Surfacing GF that was recorded in the SW log for printing can be found somewhere very close to surfacing, by scrolling on the graph on Desktop Cloud. Yet GF99 as plotted on the graph contributes to rise for a minute or so as the software processes previous ascent data. I choose to record on my paper log the peak GF99 on that curve, until the expected descent in the curve from surfacing offgassing commences. As noted above, on a deeper rec dive, the difference can be as much as 15%, and my peak for one of the Vandenberg dives was 50%.
There just seems to be a lag in the GF99 display, as the peak GF99 and the Surfacing GF recorded for logging never agree. Peak plotted GF99 seems to be very close to SurGF as noted just before ascent, but I'm working from memory there.
 
The 'official' dive ends on both the Teric and Perdix at 0.9m. I'm wondering if there's two issues. One in Cloud and another one in the DC. I think the issue(s) might also be tied into Log Rates and End Dive Depth.

GF99 on the Cloud seems to present as it should (in terms of peaks). After updating Cloud, theEnd Surface GF now matches GF99 at the surface. (both pre and post screenshots below). What these numbers actually were on my DC I don't exactly know.

•Log Rate on the Teric is between 2 and 20 seconds - default is 10. IDK what this is on the Perdix.
•End Dive Delay on the Perdix is between 20 and 600 seconds (default 60) after End Depth.
•On the Teric it's between 10sec and 10min (default 10sec) after End Depth.
•End Depth on both is 0.9m.

Screen Shot 2020-03-02 at 6.37.09 am.png
Screen Shot 2020-03-02 at 6.37.39 am.png

 
My experience is just a shade different:
At the moment of surfacing, both GF99 and what the computer logs were the same at 37%
2020-03-02 (2).png

But about 8 sec later, the GF99 peaked at 47%, which was not logged as End Surface GF by Shearwater Cloud.
2020-03-02 (3).png

Perhaps we're trying to say the same thing, @Jay
There seems to be a fractional lag, and what Cloud is capturing as End Surface GF is not as high as the calculated value 8 sec later.
 
  • Like
Reactions: Jay
Interesting. On the particular dive I displayed I didn't have any small spike after depth = 0, but on other dives I see the same effect as you.

Do you recall what the DC was predicting SurfGF would be, and what the GF99's and SurfGF when depth = 0 was? (I'll try to look next week if I make it on the plane :)
 
@Shearwater Cloud. just updated the Mac to SW Cloud 2.5.10. Now SW Cloud on the Mac is no longer working. None of the buttons work.
Hello Macan, we've had a number of reports of this issue. For now, could you please downgrade to 2.5.9? You can download it from our website here: https://www.shearwater.com/wp-content/downloads/ShearwaterCloudInstaller_2.5.9.dmg
Our developers are actively working on this issue but we would appreciate it if you would email support@shearwater.com with more information about what version of Mac you have so we can try to pinpoint this issue.
 
My experience is just a shade different:
At the moment of surfacing, both GF99 and what the computer logs were the same at 37%
View attachment 571419
But about 8 sec later, the GF99 peaked at 47%, which was not logged as End Surface GF by Shearwater Cloud.
View attachment 571420
Perhaps we're trying to say the same thing, @Jay
There seems to be a fractional lag, and what Cloud is capturing as End Surface GF is not as high as the calculated value 8 sec later.
The 'official' dive ends on both the Teric and Perdix at 0.9m. I'm wondering if there's two issues. One in Cloud and another one in the DC. I think the issue(s) might also be tied into Log Rates and End Dive Depth.

GF99 on the Cloud seems to present as it should (in terms of peaks). After updating Cloud, theEnd Surface GF now matches GF99 at the surface. (both pre and post screenshots below). What these numbers actually were on my DC I don't exactly know.

•Log Rate on the Teric is between 2 and 20 seconds - default is 10. IDK what this is on the Perdix.
•End Dive Delay on the Perdix is between 20 and 600 seconds (default 60) after End Depth.
•On the Teric it's between 10sec and 10min (default 10sec) after End Depth.
•End Depth on both is 0.9m.

View attachment 571212 View attachment 571213
Thank you both for your screenshots! This helps us narrow down the issues you are having. We just received some new depth simulator test hardware in Software so we will be continuing to work on this GF issue.

Part of the issue is that the GF being calculated on the computer during the dive is a rolling average, so we want to ensure that gets taken into account when providing the surface GF number.

CSV file data import / export.
Cloud has the ability to export to CSV, but currently, no, we can't import CSV data yet. While we cannot promise anything, we would like to expand the import/export capabilities of the app, and we will add your comments to our ticketing system.
 
Cloud has the ability to export to CSV, but currently, no, we can't import CSV data yet. While we cannot promise anything, we would like to expand the import/export capabilities of the app, and we will add your comments to our ticketing system.

Currently you export only one dive per CSV file. I would like all dives in one CSV file with only the columns that I select.
 
Hello Macan, we've had a number of reports of this issue. For now, could you please downgrade to 2.5.9? You can download it from our website here: https://www.shearwater.com/wp-content/downloads/ShearwaterCloudInstaller_2.5.9.dmg
Our developers are actively working on this issue but we would appreciate it if you would email support@shearwater.com with more information about what version of Mac you have so we can try to pinpoint this issue.

@ Shearwater Cloud. Thanks. I’m using a MacBook Pro with macOS Mojave version 10.14.6. Let me know if you need more info for diagnosing the problem.
 
https://www.shearwater.com/products/teric/

Back
Top Bottom