Fwd: sample UDDF file

[Dirk Hohndel]

Jan Schubert <Jan.Schubert at GMX.li> writes:

> On 01.03.2013 06:05, Miika Turkia wrote:
>>
>> Anyway, when looking at the
>> olibaumann_log_uddf__130203103820061119.uddf, the following samples
>> are ignored (under waypoint):
>
> Thx Miika, just forget to grab this.
>
>> - otu
>
> This is something subsurface is calculating also at the moment, I'd
> suggest to use the dive computer generated values in case we get it!?

Yes

>> - setpo2
>> - measuredpo2 (for all sensors)
>
> Nuff said...
>
>> Other stuff that is not handled from that data file:
>> - generatore
> I assume you refer to <generator>? In  detail it reads like this:
>
> <generator>
>   <name>DR5 278 with Firmware V 1.5</name>
>   <manufacturer>
>    <name>heinrichs weikamp, Germany</name>
>   </manufacturer>
>   <version>0.2</version>
>   <datetime>2013-02-03T10:38</datetime>
>  </generator>
>
> Look like additonal information describing the dive computer. Might be
> nice to have added to some meta data in subsurface!?

we could parse this into our divecomputer settings

>> - decomodel
> I'd like to see this processes sometimes in the future and be added as
> information to the dive profile.
> BTW: I can not see any specification for the gradient factors in the
> data, similar strange as the missing deco ceiling. I really would like
> to clarify this with HW...

Matthias mentioned to me that he is insanely busy with their new
products. But yes, that's something we should discuss with them.

Jan, let's you and I agree on a concise email in which we summarize the
feedback that we have BEFORE sending it to HW (I know Matthias may be
reading all this, but I really want to make this consistent and easy for
him)

>> - applicationdata
>
> Looks like some specific data used by HW? It reads in detail:
>     <applicationdata>
>      <heinrichsweikamp>
>       <dr5>
>       
> <drxplotdepth>03070b0c0e1013171c21232526282a2c2c2e2f30323333333436383c4149535d64696c707377797a7b7b7b7b7c7d7c7c7c7d7d7d7d7d7d7d7e7d7d7c7a78767373717172747372737374727171727171706d6b6a69696a6b6a68656564636463616261646263605f5d5e5d5f5c5b58595a5a59534f4c474442413f3a373531312c2c2b292b2b28262625262626252421201f1e1d1e1d201d1b1d1919171819181717191818181715151514131213111111121212121213100f1010100e0e0e0e0f0e0e0d0e0f100e0e0d0e0e0d0f0e0e0d0d0d0d0d0c0d0e0c0d0e0e0e0e0e0d0d0c0e0f0e0c0c0c0c0e0d100e0f0e0e0e0f0d0e0f0e0e0e0e0c0e0d0b0a0a070301010000010000000000000000000000000000000000000000000000000000000000000000000000000000</drxplotdepth>
>       
> <drxplottemp>656565666666666666666666666666666666666666666666666666666666666666666767676667676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676767676766666767666767676666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666666768686868686868686868686868686868686868686868686868686868686868686868</drxplottemp>
>       
> <drxplotoxy>282d3030302f2b25303130302c2f2f2e46494547454144444445464746403f484a4444444346454444464544444443414141434241403f424141413f413f3e404447454546444443464342414443434242413f3e3d3c3b3e3d403e444041414041403f3f40483f40404241424046433b404048433e443b403e3c40604944413f433d43404444404747454445434344403e404141484548464149444441464847464546464946444242424240444642424149474747464644434a575054504e4e5654535152545652525053535254535450515150514f51514f4f525452535251504f5254524f4f4e4e535157545552535455515254545354534f52524d494a413934333232333131313131313131313131313131313131313131313131313131313131313131313131313131</drxplotoxy>
>       </dr5>
>      </heinrichsweikamp>
>     </applicationdata>
>
> I do not see any use for this right now.

I'm curious what it actually is - I won't know if it's useful until I
understand it :-)

>> - surfaceinterval
> Same as OTU, generated by subsurface as well.
>> - lowestoxygen
>> - greatestoxygen
>
> As Dirk already said: Might be similar as maxdepth is different as
> maximum depth reportet in samples. Could/Should be handled similar to
> maxdepth....

Well - we don't do ANYTHING with low/high o2 - so I don't know what we
would do with these values, either

/D