Hi Robert, On 23 November 2016 at 22:05, Robert Helling <hell...@atdotde.de> wrote:
> > Hi, > > here are two patches to improve the dive plan. The first simply shows the > total runtime on top of the plan. This is one of the most important data of > a plan and should be visible while adjusting parameters of the plan. So it > is very inconvenient if is scrolled out of the dive plan widget. > This is a great idea. I've lost count of the number of times I scroll down to the bottom of the notes, just to see the total runtime. One question: is there a reason why we can't access displayed_dive.dc.duration.seconds instead of creating a new function to iterate through all the data points to get the runtime? > > the second attempts to find an approximation of a VPM-B profile in terms > of Buehlmann+GF parameters: For each stop it computes an effective gradient > factor that would give a similar ceiling. Of all these computed gradient > factors it does a linear regression to fit a line to these factors (this is > what the Baker GF’s do). This line is then expressed as effective GFlow and > GFhigh in the dive plan. > This sounds very interesting; hopefully I'll have a chance to play with it in the next day or two. Cheers, Rick
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
