Unfortunatly I can't see how it works. Hopefully he will explane it though.
I have an example dive that i am preparing for.
Tx 10/60 SP 1,3
15min@30m, 10min@50m, 20min@80m, 10min@50m 15min@30m
Runtime is 205min
If i take the average depth
70min@50m
Runtime is 180 min
25 minutes skipped deco is to much for me.
I dont know if you calculate different than Lamont, but otherwise i think those 25 minutes are a pretty good reason.
Or is there a way to use RD for these kind of dives?
That's the kind of profile where depth averaging alone doesn't work very well. If you had this instead:
15min@40m, 10min@50m, 20min@60m, 10min@50m 15min@40m
It probably works much better since its smoother. Or if you had this which is just a quick spike somewhere:
15min@40m, 10min@50m, 5min@80m, 10min@50m, 15min@40m
Neither of those are dealing with "ratios" though, so those are just depth averaging. Your profile looks like an example of where depth averaging is fairly bad.
Assuming that the symmetry of your profile is because it's in a cave, then you can roll your own ratio deco by running profiles like this:
15min@30m, 10min@50m, 10min@80m, 10min@50m 15min@30m
15min@30m, 10min@50m, 20min@80m, 10min@50m 15min@30m
15min@30m, 10min@50m, 30min@80m, 10min@50m 15min@30m
Then pick a "setpoint" (unfortunate collision of terminology) around what your 'typical' profile is, and you determine a relationship between how many more minutes of deco you need based on the length of the bottom time. At 80m its going to be close to 2 minutes more deco for every minute of bottom you spend in the 80m segment. You'll probably award 1 minute of that to the 6m stop and 1 minute between 21m and 9m.
As your decos get longer you'll need to adjust the time moving from 30m to 21m and it'll eventually start to break down as you get too far away from your "setpoint".
What you're doing is very similar to approximating sin(x) = x which works to 2% accuracy in the range [-0.5,0.5]. But is obviously very bad near, say, 6.
That's really all there is to it, its just linear approximation, after noticing that there's a pattern in similar profiles.
There's also a practice that GUE divers tend to use which is "linearized deco" which means that instead of a profile full of random numbers to memorize you divide the deco up into phases where the stop times are the same. So for example (apologies for imperial measurements, but I don't have the time to convert this:
15 min @ 330' (10/70)
330 -> 240: 30 fpm (3 mins)
240 -> 190: 20 fpm (3 mins)
- switch to 21/35
190 -> 120: 1 minute stops (7 mins)
120 -> 70: 2 minute stops (10 mins)
- switch to 50%
70 -> 20: 5 minute stops (25 mins)
- switch to O2
20 -> surface: 30 minutes
6 mins slow ascent to surface
(don't ask me how to do the ratio deco on that, the diving there is a bit over my head, but that's a good example of linearized deco, and hopefully heads off misunderstandings suggesting that GUE teaches a straight linear profile all the way to the surface or something...). The basic idea here is that once you're driving a gradient as long as you don't overstay too long it doesn't make a whole lot of difference where you award the minutes for stops between 70 and 20 and so linear is easier to remember. Of course this is holding you "deeper than you should be" and you're using more gas, so when I've had issues on dives I've moved time from deeper stops shorter "on-the-fly" to get shallower and conserve gas when that was important.
There's weaknesses to all three of these principles: depth averaging, ratio deco, and linearized deco. But what is taught is that you apply them where they make sense, and GUE definitely teaches that deco planners should be considered more authoritative than any of these principles.
And like I said, I'm also running with a computer in "parachute mode" these days due to some of those weaknesses...