I am a bit late to this conversation and would like to address an older topic in this thread, the use of Ratio Deco in cases of accidentally going into deco on a planned No deco dive.
As one of the originators of RD, Jarrod Jablonski wrote to me during a private conversation, "RD is not an algorithm; it is a mnemonic device designed for use within a CONFINED set of parameters....Blindly using an inappropriate tool outside relational parameters is very much like blindly jumping off a high bridge into water with an entirely unknown depth. This can work a lot of times but is not necessarily a sustainable activity."
RD was created as a way of reproducing a decompression schedule that would have been produced by a standard program. In order to make it work reasonably well in such a simple format, the parameters have to be very narrow. You can't input a variety of gas mixes into it, as you can with a program like V-Planner or a mixed gas computer. It must be used with standard gases. Air is not one of those standard gases. In a well known (at least among DIR people on SB) case in Truk Lagoon, someone used RD for a fairly deep dive on air and ended up quite bent. It was not RD's fault. The dive was outside of the RD parameters.
Both GUE and UTD use a different system for dealing with the kind of dive described in this thread. It is called minimum deco, and it is similar to RD in nature. The problem with it is, once again, the parameters. The diver is supposed to be diving on EANx 32. When it is explained in the UTD class materials, it says clearly "This is not an air table."
It seems to me that if one goes into deco on a dive in which that was not in the plan, then the proper solution is to use the contingency plan offered by whatever system the diver was using in the first place. If the diver was using the PADI tables, then the PADI emergency deco system would be used. If the diver is using a computer, then the diver should know how to follow the deco directions the computer is providing.