Planner last stop 6m issue and som others.

[Joakim Bygdell]

On 05 Jun 2014, at 0:23, Robert C. Helling <helling at atdotde.de> wrote:

> 
> On 04 Jun 2014, at 20:10, Joakim Bygdell <j.bygdell at gmail.com> wrote:
> 
>> If we have a gas switch at 6m and choose last stop at 6m we get the gas switch event and the deco stop as two separate entries in the final plan.
>> 
>> Thera are some other issues related to gas switch events as well, look at the table below.
>> 
>> EAN50 switch depth 22m
>> depth
>> runtime
>> duration
>> gas
>> 50m
>> 2min
>> 2min
>> (21/35)
>> 50m
>> 30min
>> 28min
>>  
>> 22m
>> 34min
>> 4min
>> EAN50
>> 21m
>> 35min
>> 1min
>>  
>> 18m
>> 37min
>> 1min
>>  
>> 15m
>> 39min
>> 2min
>>  
>> 12m
>> 43min
>> 3min
>>  
>> 9m
>> 48min
>> 5min
>>  
>> 6m
>> 49min
>> 1min
>> EAN100
>> 6m
>> 60min
>> 11min
>>  
>> 0m
>> 66min
>> 6min
>>  
>> 
>> The above table tells us that we hav a gas switch a 22m with a total stop time of 4min.
>> 
>> If the gas switch is set to occur at 21m the 4min stop at 22m disappears and we only have a 1min stop at 21m.
>> 
>> For some reason the stop time reported at 22m are actually the calculated ascent time.
>> 
>> 
>> 
>> Looking at the output of the Verbatim dive plan we have transitions leading up to gas switch events and surfacing even if we choose not to show transitions.
>> 
>> Stay at 50 m for 27:00 min - runtime 30:00 on (21/35)
>> Transition to 22 m in 3:53 min - runtime 33:53 on (21/35) <— This transition disappears if the switch depth is set to 21m.
>> Switch gas to EAN50
>> Stay at 21 m for 1:00 min - runtime 35:03 on EAN50
>> Stay at 18.0 m for 1:00 min - runtime 36:33 on EAN50
>> Stay at 15.0 m for 2:00 min - runtime 39:03 on EAN50
>> Stay at 12.0 m for 3:00 min - runtime 42:33 on EAN50
>> Stay at 9.0 m for 4:00 min - runtime 47:03 on EAN50
>> Transition to 6.0 m in 0:30 min - runtime 47:33 on EAN50 <---
>> Switch gas to EAN100
>> Stay at 6.0 m for 11:01 min - runtime 58:34 on EAN100
>> Transition to 0.0 m in 6:15 min - runtime 64:49 on EAN100 <—
> 
> <0001-Planner-Change-lasttime-only-if-we-printed-something.patch>
> <0002-Planner-Avoid-bogus-segments-with-0-time-and-don-t-s.patch>
> These two patches address the issues you raise. 
> 

Patches work fine.


> The “segment duration” always includes the time of the previous transition (that’s why I didn’t call it stop time) and that makes these durations add up to the runtime (modulo rounding effects). Do people want that differently?
> 
> Best
> Robert
> 
> --                                                                              
> .oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oO 
> Robert C. Helling     Elite Master Course Theoretical and Mathematical Physics  
>                       Scientific Coordinator                                   
>                       Ludwig Maximilians Universitaet Muenchen, Dept. Physik    
> print "Just another   Phone: +49 89 2180-4523  Theresienstr. 39, rm. B339       
>     stupid .sig\n";   http://www.atdotde.de 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140605/fe27a48b/attachment.html>