As I suggested earlier, if a ratio deco plan creates a profile that matches an established, reliable algorithm, I have no problem with it, and I would have no more problem following it on a dive than I would following that algorithm.
The fundamental problem with planning a dive using either ratio deco or desktop software is what I described earlier--it is based upon the assumption that the humans who created the plan will be able to follow it as planned. Here is an example of a DCS case that hit a buddy team of friends of mine. They went to their planned depth for the planned time, ascended to their planned first deep stop, and then followed the planned ascent profile from there to the surface. They used bottom timers and a computer in gauge mode to guide them. They thought they had done everything perfectly, and they were surprised to get bent. Because they had used a computer in gauge mode, they had a computer log of the dive, and it showed that they had not done the dive they thought they had done. They had strayed below their planned maximum depth a number of times, something I see happening frequently on decompression dives. They had taken longer than planned to reach their first deep stop, and they had not realized that they were beginning their decompression profile from there several minutes later than they should have been. They had somehow miscounted their minutes on their final stop, leading them to surface a little early.
I am willing to bet a lot of people have made errors like that during their dives and were either lucky enough not to get bent or they did get bent but did not have a computer log to show them where they had messed up. There is enough wiggle room in most program to allow for those errors, as long as there are not too many.
The fundamental problem with planning a dive using either ratio deco or desktop software is what I described earlier--it is based upon the assumption that the humans who created the plan will be able to follow it as planned. Here is an example of a DCS case that hit a buddy team of friends of mine. They went to their planned depth for the planned time, ascended to their planned first deep stop, and then followed the planned ascent profile from there to the surface. They used bottom timers and a computer in gauge mode to guide them. They thought they had done everything perfectly, and they were surprised to get bent. Because they had used a computer in gauge mode, they had a computer log of the dive, and it showed that they had not done the dive they thought they had done. They had strayed below their planned maximum depth a number of times, something I see happening frequently on decompression dives. They had taken longer than planned to reach their first deep stop, and they had not realized that they were beginning their decompression profile from there several minutes later than they should have been. They had somehow miscounted their minutes on their final stop, leading them to surface a little early.
I am willing to bet a lot of people have made errors like that during their dives and were either lucky enough not to get bent or they did get bent but did not have a computer log to show them where they had messed up. There is enough wiggle room in most program to allow for those errors, as long as there are not too many.