VPM-B and the current deco algorithm

[Tomaz Canabrava]

On Wed, May 27, 2015 at 2:22 PM, Jan Darowski <jan.darowski at gmail.com>
wrote:

> Hi!
> If as Dirk said, you guys want to have a constant access to my work
> and relatively often merge it with master, I need to change my
> approach a little bit (I wanted to first implement the algorithm,
> independent from the rest of the source, then integrate it). Maybe
> it's a good idea to keep it integrated all the time.
> But it leads to some questions about how this new algorithm should
> work with the current deco implementation:
>
> The most important thing is if we want both algorithms to be
> calculated for the current dive and just one of them displayed or
> should we recalculate the plan depending on the chosen algorithm?
>
> Should I put the new algorithm into current deco. files or should I
> look for some way to split them? Right now, there is a lot of things
> in deco which I need in vpmb implementation.
>
> Right now, planner has an ugly plan() function which among others
> implements the main logic of the current deco algorithm. Can I add
> plan_buehlmann and plan_vpmb() which will be called from the current
> plan() function?
>

I'm not really a plan guy but I think you should create a dropbox on the
planner with the current deco algorithm that will be used.



>
> Thanks,
> Jan Darowski
> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20150527/d834dc02/attachment.html>