On 11/11/2014 15:15, Miika Turkia wrote:
On Tue, Nov 11, 2014 at 6:21 AM, Anton Lundin <[email protected]
<mailto:[email protected]>> wrote:
On 10 November, 2014 - Dirk Hohndel wrote:
> So we’re a bit behind schedule for that…
>
> 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.
> Translation strings have been updated and pushed, latest
translations have been pulled.
> I’m still waiting to hear on the Cobalt tank download issue (Jef
is helping me to get this right).
> I’m hoping that Tomaz will send some more improvements for the
Filter UI.
> 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.
If someone with a taste for csv (Miika? =) would like, we could
shape up
the APD Log Viewer import to import the setpoint as the setpoint
concept
we have nowadays, and the three different sensors as different
sensors.
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.
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.
miika
The confusing question of po2 and setpoint is being discussed at the moment.
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?
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.
Kind regards,
willem
Kind regards,
willem
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
