Subsurface merging 2 dives 3 min interval question

[Joel S.]

hello, and thanks for your time. say cenote dives, one 25 min, 3 min interval, then like 25 again.. if on the latest desktop windows version 6.0.5299 , i select both, by control and clicking on both, then right click i see merge selected dives... if I do that, my numbering is good, but in the visual information window, it displays the single dive graph... summery all selected shows the total for both, like 49 minutes before the merge, and like 26 minutes after.. ..
do I need to exit and restart subsurface after the merge, or is the information not going to be more accurate ?? (no AI , so just basic time, depth and temp)

after I merge, it shows 26 minutes, and not the combined 49 minutes.. seems it just removes the 2nd dive, and doesn't combine them...
not sure what I'm missing here...
data came from a shearwater peregrine..
I have included the export of the 2 logged selections I would like to merge.. (zip is original, copy is the ssrf with an extra .txt extension added at the end..

thanks again for your time..

 

[dmaziuk]

FWIW you can always edit the xml file with notepad++ or some other text editor... if you're game.

 

[scubadada]

Hi @Joel S.

Sorry I can't help with your merge in Subsurface. To avoid this in the future, you can set your end dive delay to as long as 10 min. The default is 1 min. Page 42 of the Peregrine owner's manual.

 

[Joel S.]

Seems to me that what you need to do is eliminate all the lines of text in between:

<sample time='26:50 min' depth='0.0 m' />

and

<sample time='0:30 min' depth='3.261 m' />

Then you need to change the time stamps on each line after 26.50 to start at 27.00 and increase in 10 second intervals. It's basically copying and pasting and overwriting the first and then the first and second digits as you get into the higher numbers, you'll have to do it about 100 times.

Make a copy of the original file first and make sure Subsurface isn't running while you're doing the editing.

The developer of Subsurface to be very helpful and he's even gone into my logbook and made edits for me before I figured out how to do it myself. He posts here on ScubaBoard and can be reached from the Subsurface website.

Also you may want to change your computer settings to less frequent polling than every 10 seconds. Mine is about 1x per minute and you get a decent enough graph. It might also be costing you in battery life. Here's a screenshot of one of my Subsurface logged dives showing 1 minute data polling.

thanks for the time and the information, much appreciated.. seems easy enough ....
as far as battery, it can go 20 dives and not be 50% if I recall... so good in that department, but I'll keep it in mind, thanks for the tip.

@scubadada thanks for that, I'll look into it...

 

[anubisg11]

I have the same issue, this looks like a bug to me.
What version of subsurface are you running?

 

[dmaziuk]

It's not a bug, it's a feature: 3 minutes is close enough to the half-time of the fastest tissue compartment (4 or 5 minutes in ZH-L16) that it may make a difference in the calculations. So resetting to a new dive is the "safer" option.

 

[Joel S.]

I have the same issue, this looks like a bug to me.
What version of subsurface are you running?

windows version 6.0.5299

 

[harvalen]

Looks like the later versions merges it into one dive with profiles from two different computers.

An older version I have laying around, v6.0.5231-CICD-release, merges them into one long 49 minute dive.

Feels like a bug.

 

[Joel S.]

Looks like the later versions merges it into one dive with profiles from two different computers.

An older version I have laying around, v6.0.5231-CICD-release, merges them into one long 49 minute dive.

Feels like a bug.

Thanks so much! I appreciate it..
If it use to work and now doesn't, I would say it seems like a bug, especially if it tries to do something..

 

[anubisg11]

It's not a bug, it's a feature: 3 minutes is close enough to the half-time of the fastest tissue compartment (4 or 5 minutes in ZH-L16) that it may make a difference in the calculations. So resetting to a new dive is the "safer" option.

It was a bug in subsurface. Easy to identify the release when it was introduced and when it was fixed.