Re: Minor bugs in new release (multiple tanks)
Posted: Mon Oct 09, 2023 9:43 am
Hi Mike,
I'm trying to replicate your experience based on the numbers you sent, but there are some inconsistencies. Specifically:
>>> Tank 1 is the same size. There was 2,444-2,108 = 1336 psi used, for 38.81 ft^3 gas used.
however your PSI values are inconsistent (2444-2108 = 336 not 1336). I tried adjusting the numbers so that the volume used matched your 1336 but I still don't get the 0.55 ft^3/min that you get in Dive Log (I get 0.66 ft^3/min which is much closer to your calculated value). So I suspect that the issue with Dive Log is related to your dive time.
The Shearwater (by default) adds 10 minutes to your profile time (we use the profile time and not the entered dive time for the air consumption calculation because it is based on the average depth during each segment of the dive based on recorded gas switches). We also calculate the average depth based on the dive profile. When I change the dive time to 60 minutes I do indeed get the 0.55 ft^3/min value that you are seeing. I suspect if you look at your profile you will see that your dive profile extends near the surface for about 10 minutes after the 50 minute mark in your dive. The Shearwater lets you adjust this "additional time" to any value you like. The idea is that it helps ensure that if you restart a dive after a period on the surface the dive with still be considered the same dive (note that Dive Log can append two dives if you exceed this Shearwater setting's time). Dive Log has a "feature" in setting that allows you to ignore shallow samples to eliminate this extra time at the end of the dive. I the case of downloading Shearwater computers this is generally a setting that you want to turn on.
The only catch is that this will not automatically recalculate average depth values for dives you have already downloaded. However, you can edit an exiting dive and clear out the average depth value (on iPhone just edit and then tap the "-" next to average depth, on iPad edit and tap the "x" next to average depth). This will cause Dive Log to calculate the average depth dynamically based on the current value of the "ignore shallow samples" setting. Hopefully that will get you closer to your expected 0.67 ft^3/min value.
As for Dive Log Manager, I suspect that you are running on macOS Sonoma (macOS 15). Unfortunately, Apple introduced a fairly significant bug in their number formatters in both iOS 17 and macOS 15 that causes all values to rounded to integer values (0.55 would round 1 in this case) using the APIs that we have been using for the last 15 years in Dive Log and Dive Log Manager. We have managed to get an updated version of iOS 17 released, but have not yet managed to update Dive Log Manager. Please let us know if you are not running macOS Sonoma/15 and we will take a closer look. Otherwise, the next update to Dive Log Manager should address this issue on that platform too. Note that there is a similar preference in Dive Log Manager to ignore shallow samples (although, given the macOS bug you will still see 1 ft^3/min for now).
I hope that helps, please let us know if you are still having difficulties and I will get you to send a diagnostics log from downloading your Shearwater so that we can investigate the issue with your actual profile data.
Cheers,
Greg
I'm trying to replicate your experience based on the numbers you sent, but there are some inconsistencies. Specifically:
>>> Tank 1 is the same size. There was 2,444-2,108 = 1336 psi used, for 38.81 ft^3 gas used.
however your PSI values are inconsistent (2444-2108 = 336 not 1336). I tried adjusting the numbers so that the volume used matched your 1336 but I still don't get the 0.55 ft^3/min that you get in Dive Log (I get 0.66 ft^3/min which is much closer to your calculated value). So I suspect that the issue with Dive Log is related to your dive time.
The Shearwater (by default) adds 10 minutes to your profile time (we use the profile time and not the entered dive time for the air consumption calculation because it is based on the average depth during each segment of the dive based on recorded gas switches). We also calculate the average depth based on the dive profile. When I change the dive time to 60 minutes I do indeed get the 0.55 ft^3/min value that you are seeing. I suspect if you look at your profile you will see that your dive profile extends near the surface for about 10 minutes after the 50 minute mark in your dive. The Shearwater lets you adjust this "additional time" to any value you like. The idea is that it helps ensure that if you restart a dive after a period on the surface the dive with still be considered the same dive (note that Dive Log can append two dives if you exceed this Shearwater setting's time). Dive Log has a "feature" in setting that allows you to ignore shallow samples to eliminate this extra time at the end of the dive. I the case of downloading Shearwater computers this is generally a setting that you want to turn on.
The only catch is that this will not automatically recalculate average depth values for dives you have already downloaded. However, you can edit an exiting dive and clear out the average depth value (on iPhone just edit and then tap the "-" next to average depth, on iPad edit and tap the "x" next to average depth). This will cause Dive Log to calculate the average depth dynamically based on the current value of the "ignore shallow samples" setting. Hopefully that will get you closer to your expected 0.67 ft^3/min value.
As for Dive Log Manager, I suspect that you are running on macOS Sonoma (macOS 15). Unfortunately, Apple introduced a fairly significant bug in their number formatters in both iOS 17 and macOS 15 that causes all values to rounded to integer values (0.55 would round 1 in this case) using the APIs that we have been using for the last 15 years in Dive Log and Dive Log Manager. We have managed to get an updated version of iOS 17 released, but have not yet managed to update Dive Log Manager. Please let us know if you are not running macOS Sonoma/15 and we will take a closer look. Otherwise, the next update to Dive Log Manager should address this issue on that platform too. Note that there is a similar preference in Dive Log Manager to ignore shallow samples (although, given the macOS bug you will still see 1 ft^3/min for now).
I hope that helps, please let us know if you are still having difficulties and I will get you to send a diagnostics log from downloading your Shearwater so that we can investigate the issue with your actual profile data.
Cheers,
Greg