<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Rick,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Sep 2015, at 20:26, Rick Walsh <<a href="mailto:rickmwalsh@gmail.com" class="">rickmwalsh@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The model assumes that deco starts at the last input point. This is ok for a square profile dive. But for a multi-level dive, especially with a deep bouncing, it doesn't make much sense. I think a better assumption would be that the Boyle's ceiling be taken is the deepest ceiling at any point in the dive. This gives very nearly the same result for a square profile dive, but in a multilevel dive such as your example, the decompression time would increase with the deep bounce, as one might expect.</span></div></blockquote></div><br class=""></div><div class="">I thought you had already sent a patch for this. BTW, the thread that I got the idea from to look at this was about MultiDeco which (due to a bug apparently) gets the bounce dive really wrong.</div><div class=""><br class=""></div><div class="">Best</div><div class="">Robert</div></body></html>