<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 21 Aug 2015, at 10:48, 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="">It appears that the error didn't occur with the 100 m profile, but with shallow profiles that were calculated after entering gasses, but before entering all the depth information. The red box with error messages wasn't visible while the planner was open, but is displayed after saving the plan. <span class="Apple-converted-space"> </span></span></div></blockquote></div><br class=""></div><div class="">thanks for catching this! It turned out, this could be triggered by opening the planner with VPM-B on an empty log and just changing the gas to OXYGEN (in fact any nitrox with >=78% oxygen).</div><div class=""><br class=""></div><div class="">This came about by a numerical instability when applying the Boyle law compensation when there is nothing to compensate for. </div><div class=""><br class=""></div><div class="">Here are two patches of which the first should fix the issue (at least it does for me). Please test carefully!</div><div class=""><br class=""></div><div class="">Best</div><div class="">Robert</div><div class=""><br class=""></div><div class="">PS: This happened to be quite hard to debug, took me >2h to fix.</div></body></html>