On Thu, Apr 15, 2021 at 10:39 AM Tom Kuehnel <
t.kue...@gmail.com> wrote:
>
> Sure here are 3 examples from different vintages. not so sure about the "simple manually edit" part as the edit window does NOT show the extra points..
So I only looked at the first one, but the basic issue seems to be
that you have a perfectly fine dive:
<dive number='410' otu='115' cns='42%' divesiteid='1cecd01f'
date='2019-04-28' time='11:34:00' duration='102:10 min'>
and you have samples for it all:
<sample time='0:00 min' depth='1.7 m' temp='30.0 C' po2='0.77 bar' />
<sample time='0:10 min' depth='1.9 m' ndl='99:00 min' po2='0.54 bar' />
<sample time='0:20 min' depth='2.2 m' po2='0.7 bar' />
...
<sample time='101:50 min' depth='1.7 m' po2='0.71 bar' />
<sample time='102:00 min' depth='1.4 m' po2='0.68 bar' />
<sample time='102:10 min' depth='0.0 m' po2='0.64 bar' />
but then you have a couple of insane events:
<divecomputer model='Shearwater Petrel/Perdix' dctype='CCR'>
<event time='2000:00 min' type='11' value='21' name='gaschange'
cylinder='0' />
..
<divecomputer model='Shearwater import' dctype='CCR'>
<event time='833:20 min' type='11' value='21' name='gaschange' cylinder='0' />
and because you have those events at the 833 and 2000 minute marks,
subsurface will make that profile go out all the way to that. End
result: the actual dive (that is only 103 minutes long, not 2000
minutes) looks squished up at the beginning of the profile.
If you remove those crazy events- you can literally just edit that
file and remove those two lines - it all looks right to me (although I
obviously don't know the dive, so maybe there is something else odd
hiding too)
I don't know how you imported your old log-files, but the times for
those gas changes are clearly wrong. Some import script bug, but I
don't know where it comes from.
Linus