Hallo Robert, Am 18.09.2017 um 10:39 schrieb Robert Helling: > Stefan, > >> On 17. Sep 2017, at 22:47, Stefan Fuchs <[email protected] >> <mailto:[email protected]>> wrote: >> >> I see a somehow unexpected result: >> The situation that the plotted ceiling changes in respect to the >> spike being present or not when clicking at the dives in a different >> sequence is gone. So resetting additional things seems to be the >> correct approach because the result of the deco calculation really >> shouldn't depend on the sequence the dives are selected. >> >> But: The spike is now only gone for the one specific dive (#710 in my >> example) where I discovered this "unstable" results. Many of my other >> dives now still always show such a spike at the beginning of the deco >> ceiling exactly as before. >> I have the fear we see two different issues here. >> I now discovered s.th <http://s.th/>. else which could help solving >> the issue: If a plan a dive in the planner the deco ceiling displayed >> shows no spike. If I save the dive and the very same profile is >> displayed outside the planner in the "normal" main window view the >> spike is there. I will send you some pictures tomorrow and try to >> generate some debug output. >> >> One more important hint I maybe didn't mention up to now: The spikes >> in the profiles are only present if I enable " show ceiling in 3m steps". > > Ah, that’s an important clue: Turning on the steps let’s be see the > spike as well. Apparently, it comes from the 5min tissue which has a > ceiling of a few centimetres which gets rounded to 3m. > > Another observation: > > Start from an empty log. Plan a VPMB+2 dive to 30m for 20m. -> no spike > Save. In the logbook, this dive has a spike. > Edit dive in planner, spike gone. > Save again, spike still gone. > Save to xml, quit subsurface > Open Subsurface with this dive: spike reappeaered. > *Edit dive in planner: much less ceiling* Yep, this "much less ceiling" thing on replan until you delete the planner generated waypoints is something I recognized yesterday as well.
Good that you can reproduce all this now as well. I guess there is for the moment no more need to create some screenshots or further docu from my side? Or shall I at least update the issue on Github with the latest findings? Let's hope you or Rick can figure out where this comes from... Thanks! Best regards Stefan -- Stefan Fuchs E-Mail: [email protected] <mailto:[email protected]>
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
