Correct. I'm not at all concerned about life-threatening violations, I'm looking at those skipped a minute because the computer won't clear and I'm fine by RT. I was not aware the Cobalt would not lock out given an ascent to the surface with deco remaining.The Cobalt doesn't "lock out" users who miss or don't complete a deco stop. It will display a prominent warning for 24 hours saying that a schedule was not completed and that the computer's schedules might not be valid, but it's up to the diver to determine if the violation was trivial or not. It basically keeps running the algorithm no matter what- at some level of violation it's no longer possible to generate a schedule that doesn't involve going deeper than the current depth, but I don't think massive violations are what you are concerned about.
OK! So I knew I wasn't crazy. I did not know what the Cobalt was doing, only that when one is the group of divers we get a different results after a single dive. I agree with your summation we can tweak our VPM and GF to match the proprietary RGBM magic running on the Cobalt and we do have to take this course of action in practice for everyone to play nicely. However, I noticed to make this work we have to make GF changes on our Tec computers and desktop software to match the proposed profiles generated for 1) deeper dives 2) repetitive decompression dives within a single day. My initial guess was the proprietary RGBM model appears to be somewhat close to 20/85 if you added a deep stop and a 3-minute safety stop. However, if you make a second deep decompression dive or a 150+ft plus dive there appears to be an accumulated deco penalty on the shallow stops. [I've actually wondered if the projected deep stop is at/near/below the off-gas depth but that might be an entirely different discussion.] It's as if you go from say 20/85 to maybe 30/70 + deep stop + safety stop for the repetitive dives. My actual solution was to purchase an iPad mini and load up V-Planner and Baltic Deco and I just take it on the boat with me viola. We use the software to cut tables and the computers become advisory only fully admitting we sometimes just put 30/70 in the Shearwaters and that just about guarantees we're behind the Cobalt's deco model for sure.As to matching the Cobalt's RGBM to another algorithm, the Cobalt has an onboard simulator that allows for very easy running and saving of profiles in a log of simulated dives, these could be matched up to other algorithms and settings tweaked to get general alignment. Cobalt uses a "folded" RGBM on dives shallower than 150' (calculation-wise, this would be more like GF), and switches to fully iterative RGBM on doves deeper than 150' (which would be closer to VPM). But the planner on the Cobalt will generate schedules for planned dives very easily, and will display the stop schedule onscreen so you can write it down, just as one would using a desktop computer. Since it knows your detailed actual previous dive profiles, history, and tissue state, it is arguably going to be more accurate than a desktop planner for generating tables. And it will certainly allow you to plan schedules the Cobalt will agree with.
My next thought should be prefaced by agreeing with your thesis and adding that any reasonably competent technical diver can handicap to the Cobalt as valid, as is the assertion the decompression profile for the repetitive dive might be more accurate. What I'd like to submit for consideration is that the profile the Cobalt creates could be the most aggressive for the repetitive dive. I don't know because I don't know where the model is in relation to the M-Value line. I'm a GF guy at heart, what can I say. Consider if you will non-Cobalt dive planners would have their prior obligations governed by fundamentally square/multi-level dive translated to a straight table (by using V-Planner/GAP/Baltic). Accordingly those profiles are going to assume the maximum possible loading versus precise load tracking the Cobalt performs unless the divers flawlessly executed the profile (we'll assume Tec divers never go deeper or miss the RT for sake of discussion). Does it matter? Maybe not, but this is a pretty productive conversation and I think it's worthy of a thought. Of course I realize the Tec computers have the ability to plan a dive right on your wrist, but I generally don't bother.
Say I'm using Baltic with 20/85 to plan and 20/85 on the Tec computer (we can of course switch models) if I swim the profile accurately, I can plan and cut tables with crazy accuracy. As you've surmised, I do not have a solid feel for how to equate this experience with a proprietary RGBM for all situations.
The Cobalt isn't going to be super-popular as a Trimix computer out of the gate, but I was suggesting giving my clients a path forward with their existing investment. Let's put some real thought toward how a computer like the Cobalt could stay with a diver for a longer period of time without being outgrown. There's little doubt the Cobalt could do more than it does, or in different ways to make an additional (I won't say broader to recognize the Tec market is niche) appeal.Agree. The Cobalt algorithm is fully capable of supporting trimix "under the hood" (or constant PPO2, for that matter). There are some mitigating factors. Atomic specifically wanted a version that was recreational diver friendly, that means a simpler interface- of course, we could provide two modes, much as we do now with gas switching, which must be enabled to become accessible during a dive. Right now, we don't have a user interface enabled that allows a fraction of He to be entered. And the general feeling was that a console version would not be that popular as a trimix computer. I wonder if you think this might be changing with changing standards?
This is a very interesting discussion.