<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Aug 2015, at 15:44, 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="">Which approach is more justified? Debatable. The method used by Subsurface should be 'better', but when the depth of the first stop/ceiling is given a special significance thanks to the Boyles law compensation process, I'm not so sure. The 'instantaneous' ceiling method is more conservative, and, without having modified the code and tested, I'm guessing would produce deco schedules more consistent with other VPM-B programs.</span><br 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;" class=""></div></blockquote></div><br class=""><div class="">I thought a bit about this. To me, it does not make much sense to ascent only if I can „see“ the ceiling is above the next stop and not to ascent as long as we don’t violate the ceiling.</div></div><div class=""><br class=""></div><div class="">On the other hand, one could argue this behaviour is part of the definition of the model and has been tested as such (or otherwise, some of the constants would have to be changed). </div><div class=""><br class=""></div><div class="">So maybe the best might be to let the user decide. So here is a patch that adds this as a preferences value (so far without UI, so to test it, you have to set it in the code).</div><div class=""><br class=""></div><div class="">On the other hand, we don’t want to confuse the user with too many options. </div><div class=""><br class=""></div><div class="">And what is a reasonable default? Set this to false for Buehlmann and to true for VPM-B or maybe even only make this an option for VPM-B?</div><div class=""><br class=""></div><div class="">Best</div><div class="">Robert</div><div class=""></div></body></html>