<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 06/21/2015 03:23 PM, Rick Walsh wrote:<br>
<blockquote
cite="mid:CAF+v9JveKfPLcpTu9xCwora237KFXZaxNw+G-2RVhdrKuggKrw@mail.gmail.com"
type="cite">
<p dir="ltr">On 22 Jun 2015 8:16 am, "Steve Butler" <<a
moz-do-not-send="true" href="mailto:kg7je@comcast.net">kg7je@comcast.net</a>>
wrote:<br>
><br>
> On 06/20/2015 06:25 PM, Rick Walsh wrote:On 21 Jun 2015
11:19 am, "Dirk Hohndel" <<a moz-do-not-send="true"
href="mailto:dirk@hohndel.org">dirk@hohndel.org</a>> wrote:<br>
>> >On Sat, Jun 20, 2015 at 11:17:28AM +1000, Rick
Walsh wrote:<br>
>> > > But what about me? I like SI units and whole
decimals. Don't worry, 2 s<br>
>> > > timesteps fit nicely when using 10 m/s ascent
rate (18 s between stops).<br>
</p>
</blockquote>
snip<br>
<blockquote
cite="mid:CAF+v9JveKfPLcpTu9xCwora237KFXZaxNw+G-2RVhdrKuggKrw@mail.gmail.com"
type="cite">
<p dir="ltr">> Also my DC records every 10s. One of the DCs
i'm looking at does 5s intervals. <br>
><br>
> How would this work comparing the pre-dive plan with the
post-dive profile?<br>
></p>
<p dir="ltr">The change has nothing to do with setting or limiting
an ascent rate. Currently the ascent to the next stop is done in
3 second increments. If you ascend at 30ft/min (Subsurface
default, which matches most DCs) it should take 20s to ascend
10ft. But in 3s increments it is bumped out to 21s. No huge
issue but it makes the calculated plan have some odd runtimes.<br>
</p>
<br>
</blockquote>
So that would be 10 calculations (one every 2s) between stops. If
you slid the other way and went every 4s then its 5 calculations up
to the next stop. Any concerns with snappiness (performance) on
slower machines?<br>
</body>
</html>