<snip>......
With whiz-bang gizmo computers, what we find are all sorts of model interpretations by programmers under the direction of product liability lawyers. You can search for a fascinating conversation I had with RonR here on ScubaBoard about the Atomic Cobalt. The Cobalt runs "Proprietary RGBM" (whatever that means) and I observed it did weird and highly unpredictable things beyond 150ft. Turns out, the manufacturer indeed included a "Folded Model" (whatever that means) and it does modify the model (how we'll never know) in real time at greater depths. Okay. No Problem. How do we plan a technical dive with your "multi-gas" computer accurately? Anyone who's ever spent time around a Suunto computer knows about the "Suunto Minute", also a recreational interpretation of "Proprietary RGBM".
Now I know by now people are going to jump on me for picking on bubble model, but don't waste your time. I'm not picking on bubble model, what I'm doing is pointing out that when the manufacturers or their lawyers manipulate the model we can't understand where we started or what we need to adapt our processes to best utilize it.
It is my belief these features exist to convolute the dive planning process and limit legal recovery. I can imagine that a diver using one of these devices with a half dozen settings has a reduced opportunity to sue/recover damages upon being injured. I can visualize the manufacturer's attorney saying, "You failed to set the computer to morbidly obese as shown on page 134 paragraph 2, therefore you didn't do it correctly, sue your instructor who failed to teach you how to use this properly and oh btw learn to read the manual."
I've no desire to get into the fray here, except to say that I'm skeptical about the marketing of features when there isn't really a clear basis for knowing what to do with the information. But when this thread jumped over to the Computers forum I saw I had been mentioned. I will try to clarify points above.
The Cobalt has two algorithms inside. As the Cobalt's dad, present from birth to graduation, I can guarantee that lawyers had nothing at all to do with this or any other functional decision concerning the development of the Cobalt. They did review the manual.
At normal recreational depths, everything shallower than 150', Cobalt uses folded RGBM. "Folded" RGBM is a term that gets applied to Haldanian algorithms that take the information from a fully iterative bubble model, and "fold" that into the Haldanian method of calculation (i.e. using m-values, tissue half times, etc.), adding in factors designed to minimize bubble formation. It's what essentially all recreational "RGBM" computers are, including Suunto, and very much analogous to adding bubble factors to the computers that use Buhlmann algorithms. That is to say, marketing and buzzwords aside, it's about what almost all current dive computers do. The biggest reasons for doing this rather than just using the fully iterative algorithm are that 1) the fully iterative bubble models are very computationally intensive, and doing them in real time in a dive computer just was not feasible until low power processors got faster, and 2) the folded methods tend to yield good results at shallow depths, with an excellent track record. You still need to generate no-stop times for recreational divers, so fully iterative calculations (which essentially only do deco schedules) at recreational depths just represent more overhead for no gain.
The "proprietary" part really just refers to the fact that each manufacturer can dial in their own preferences for overall conservatism, or add features they think will help them sell computers- yep, marketing. Atomic wanted to go very middle of the road (not the most conservative or the most liberal) for overall baseline conservatism, add adjustments for expected workload (diver determined), age, and offer three levels of user desired conservatism adjustments. That's really what makes it "proprietary".
We did not tie the algorithm to gender or gas consumption or water temperature, because those factors are much harder to reliably correlate with real world risks in any useful way. I can be freezing cold in warm water, and overheated in cold water. I could be a big person, very relaxed, using lots of air, or a tiny person, working hard, but with low consumption. I use more air in cold water even with a low workload. And air consumption is not a direct measure of actual muscle effort, which is the concern. We can't tell what you will be doing when you get out of the water- another risk factor. Basically we opted to keep things simple rather than offer what, in my opinion, is a false sense of precision- and complicate the user interface. All dive computers are imperfect guides. I'm with HIGHwing in that understanding the limitations is preferable to a false sense of precision. We do provide onboard calculation of SCFM (or l/min) consumption in the log because it is a useful metric for the diver to evaluate their performance.
When the diver goes below 150' the Cobalt switches to a fully iterative RGBM algorithm. This depth is arbitrary, based on not wanting to confuse recreational divers by the schedule shift. The full schedules will start deeper, generally, and look a lot like a very slow ascent. They are based on the Cobalt modeling, in real time, the known physics of bubble formation and trying to minimize that bubble formation through a controlled ascent. On deeper dives, deco is a given, so the limitations above don't apply and we calculate schedules using the full iterative model. While I don't in any sense think of the Cobalt as a Tech computer, this crosses over a bit onto the border lands. So far as I know, the Cobalt is the only recreational computer to incorporate a fully iterative bubble model, though both RGBM and VPM are now available for some tech computers.
Both these algorithms are included in the Cobalt's onboard planner, and are available in third party planning software as well. I'm not happy about the fact that RGBM itself is closed and proprietary as opposed to open and available, but having seen both sides I can say that generally algorithms are more alike in their results than they are different. My own feeling is that algorithms get too much attention, they have all worked pretty well, and the things that probably matter more to the diver, like the user interface, get too little focus.
Ron