<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 23, 2014, at 4:10 AM, Davide DB <<a href="mailto:dbdavide@gmail.com" class="">dbdavide@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I repeated the sequence and I was able to reproduce the bug.<br class=""><br class="">I exported the dive before/after the new DC import in subsurface format.<br class="">Comparing the two xml files I see that after importing the new DC<br class="">profile it added a wrong air gas and it modified just one sample with<br class="">a phantom "sensor '3'" attribute.<br class=""></div></blockquote><div><br class=""></div>As I said on trac - that’s one thing that puzzles me and it’s clearly broken and wrong.<br class=""><div><br class=""></div><blockquote type="cite" class=""><div class="">This is the inserted cylinder:<br class=""><br class=""><cylinder description='Air' start='218.25 bar' end='83.75 bar' /><br class=""></div></blockquote><div><br class=""></div><div>So it takes the pressure data from the first DC, first tank, and turns that into the </div><div>pressure data for the new air tank. Creative, but also wrong.</div><br class=""><blockquote type="cite" class=""><div class="">This is the modified sample:<br class=""><br class=""><sample time='0:12 min' depth='4.98 m' temp='18.4 C' pressure='218.25<br class="">bar' sensor='3' /><br class=""><br class="">BTW the new computer added also this:<br class=""><br class=""><notes>" "</notes><br class=""></div></blockquote><div><br class=""></div>That’s because the UDDF from the deep contains these insightful lines:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""><notes></span></div><div><font face="monospace" class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class=""><span class="Apple-tab-span" style="white-space:pre"> </span></span></font><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""><para>" "</para></span></div><div><font face="monospace" class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span></font><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""></notes></span></div><div><br class=""><blockquote type="cite" class=""><div class="">Before adding the new dc profile, the start/end pressure were<br class="">calculated (and correctly displayed) by galileo stored pressure<br class="">samples.<br class=""></div></blockquote><div><br class=""></div>Interestingly enough, even your ‘before’ XML already had very curious data</div><div>for the trimix cylinder that I couldn’t quite understand. Even though there</div><div>were samples with cylinder pressure it showed an (incorrect) end pressure</div><div>for that cylinder in the XML:</div><div><br class=""></div><div><span class="nt" style="color: rgb(0, 0, 128); font-family: monospace; font-size: 11px;"><cylinder</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">size=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'17.0 l'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">workpressure=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'232.0 bar'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">description=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'D8.5 232 bar'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">o2=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'15.0%'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">he=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'60.0%'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">start=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'220.0 bar'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="na" style="color: rgb(0, 128, 128); font-family: monospace; font-size: 11px;">end=</span><span class="s" style="color: rgb(187, 136, 68); font-family: monospace; font-size: 11px;">'200.0 bar'</span><span style="font-family: monospace; font-size: 11px; background-color: rgb(255, 255, 255);" class=""> </span><span class="nt" style="color: rgb(0, 0, 128); font-family: monospace; font-size: 11px;">/></span><br class=""><div><br class=""></div><div>And as usual - your top post makes it very hard for people to keep the chronology </div><div>of data in sight…</div><div><br class=""></div><div>/D</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><br class="">On Tue, Dec 23, 2014 at 12:28 PM, Davide DB <<a href="mailto:dbdavide@gmail.com" class="">dbdavide@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">Hummm,<br class=""><br class="">I think I got a nasty bug using two computers. I ask here before I file a bug.<br class=""></blockquote></div></blockquote><div><br class=""></div>I wouldn’t call this a nasty bug - it’s maybe a small inconsistency… :-)</div><div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""><br class="">I have a dive logged with a Galileo sol and a xdeep black Bottom timers.<br class=""><br class="">1) I downloaded Galileo data<br class="">2) I filled all the relevant info as gas used, tanks, pressures, gas<br class="">switches....<br class="">3) everything is fine.<br class="">4) I import xdeep data<br class="">5) I lost gas switches and gas used hence sac... One gas switch on<br class="">Galielo went to the xdeep.<br class=""></blockquote></div></blockquote><div><br class=""></div>I don’t see any indication of this. Can you explain where you think you see that?</div><div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class="">What should I see in this complicated situation?<br class=""><br class="">I was expecting to find one of the following:<br class=""><br class="">#1 the same gas switches and gas I add on a profile are copied on the other<br class=""></blockquote></div></blockquote><div><br class=""></div>As I said on trac. NOPE. That’s NOT what you should see.</div><div>The UDDF from the xdeep clearly claims that it uses air and has NO gas switch at all.</div><div>Since the first DC has no tank with air, Subsurface invents a third cylinder with air and</div><div>switches the xdeep DC explicitly to it at the beginning of the dive. And has no gas</div><div>switch at all in the xdeep DC afterwards.</div><div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class="">#2 The second profile is virgin so I have to insert again gas switches<br class=""></blockquote></div></blockquote><div><br class=""></div><div>I don’t understand. That’s what you get.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""><br class="">Actually option #2 would bring me in a dead end: different SAC so only<br class="">option #1 is correct<br class=""></blockquote></div></blockquote></div><br class=""><div class="">I don’t quite see how Subsurface could magically do the right thing with the data</div><div class="">it gets. Garbage in, garbage out.</div><div class=""><br class=""></div><div class="">What you COULD do to fix it is this:</div><div class=""><br class=""></div><div class="">Manually remove the gas switch event in the second DC structure (you can only do this</div><div class="">in the XML since we never show a forced gas switch at the start (since those are confusing</div><div class="">to the user)). And then simply add the gas switch to O2</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>