Allow replanning of logged dives

[Anton Lundin]

On 12 October, 2015 - Davide DB wrote:

> On Mon, Oct 12, 2015 at 4:00 PM, Anton Lundin <glance at acc.umu.se> wrote:
> > On 12 October, 2015 - Anton Lundin wrote:
> >
> >>
> >
> > Fyi. I sketched out approximately that dive in the planner, 30min @ 70m
> > 16/60, and there is no problem calculating the TTS on this i7-4600U
> > @2.10Ghz. The calculation is instant and the TTS is at the "worst" point
> > is about 226min.
> >
> > Maybe the planner is nicer to the TTS algorithm for some reason i can't
> > figure out at the moment.
> >
> > Thats on OC btw, but you're dive is SCR? Maybe thats the culprit.
> 
> Anton, I'm missing something...
> I used three deco gas in my dive. The planner should calculate TTS as
> a normal tech DC would, hence considering I will follow the suggested
> plan with all gas switches.
>
> I think the TTS on the real profile should do the same because tissue
> saturation calcs are made taking in account my deco gasses.
> 

The TTS calculations isn't specific to the planner.  It's a general
subsurface feature.

Currently it doesn't do any gas-switches in its calculations, because
thats a quite big rabbit-hole to go down. IE, when should it switch gas?
At mod? 1.6, 1.5 or 1.4? Configurable?

So when i wrote that i just made it simple. No gas switches.

Thats why you see a jump in TTS at the gas-switches. When you switch to
a deco gas, the TTS drops.


There were quite a few older DC's who behaved that way. Its pretty
uncommon in newer DC's and some can still be configured that way.


So, thats why it doesn't do gas switches.


But still a upper limit of the TTS is anyhow a good idea.
I'll clobber up a patch for that unless someone else beats me to it.


//Anton


-- 
Anton Lundin	+46702-161604