<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/11/2014 15:15, Miika Turkia
wrote:<br>
</div>
<blockquote
cite="mid:CAEB307Pz2Cud+XBxywyRLMaFet6FeS+qvfW46HybqmHhgVBu7w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Nov 11, 2014 at 6:21 AM,
Anton Lundin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:glance@acc.umu.se" target="_blank">glance@acc.umu.se</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 10 November, 2014 - Dirk Hohndel wrote:<br>
<br>
> So we’re a bit behind schedule for that…<br>
><br>
> As far as I know I have all outstanding patches
applied. If you have something that you sent me and that
isn’t in master, please resend.<br>
> Translation strings have been updated and pushed,
latest translations have been pulled.<br>
> I’m still waiting to hear on the Cobalt tank
download issue (Jef is helping me to get this right).<br>
> I’m hoping that Tomaz will send some more
improvements for the Filter UI.<br>
> I’m not sure I know where we are with the CCR
support. The patches and revisions and comments and…
leave me a bit confused if I have applied everything
that should be applied.<br>
<br>
</span>If someone with a taste for csv (Miika? =) would
like, we could shape up<br>
the APD Log Viewer import to import the setpoint as the
setpoint concept<br>
we have nowadays, and the three different sensors as
different sensors.<br>
</blockquote>
<div><br>
</div>
<div>Isn't the current po2 import field already the same as
setpoint? At least setting the setpoint on Poseidon import
it is saved as po2 attribute in the XML. And the csv2xml
seems to be doing just that for the po2 value field.<br>
<br>
I think the sensor reading support falls short currently.
Even though I set the values on Poseidon import, they are
not stored on Subsurface XML when saving. I wonder if
these fields are actually used currently or not - is it
only the saving/loading that is missing.<br>
</div>
<br>
</div>
<div class="gmail_quote">miika<br>
</div>
</div>
</div>
</blockquote>
The confusing question of po2 and setpoint is being discussed at the
moment.<br>
<br>
With respect to the APD log viewer, the only way I am aware of to
export dive log data is to select a tab labelled "Data" which shows
a matrix/spreadsheet of all information. It has many columns. The
only way of export is then hitting a button a button that copies the
whole thing to the clipboard from which it could be pasted into
notepad or something more sensible. Is there another way that I am
not aware of?<br>
<br>
Miika, the APD matrix fits perfectly into the existing CSV import
structure. The only issue is that for the APD there are two
computers, each with its own (redundant) set of data, but based on
the same three oxygen sensors. I suggest that 1) the data for the
first computer is read in as definitive and interpreted in the
conventional way by the existing code. I suspect that very little,
if any, code configuration will be required for this import. This
couldpotentially make Subsurface V 4.3. Afterwards, what we can do
is to actually look at the two independent data sets in the original
CSV file and, at import time, find the maximal difference in value
reported by the two computers, a type of 1-line summary of the
degree to which the 2 computers differ. This could be reported in
the device-dependent info tab in Subsurface.<br>
Kind regards,<br>
willem<br>
<br>
<br>
Kind regards,<br>
willem<br>
<br>
<br>
</body>
</html>