Fwd: sample UDDF file

[Miika Turkia]

On Thu, Feb 28, 2013 at 4:56 PM, Jan Schubert <Jan.Schubert at gmx.li> wrote:
> On 28.02.2013 05:08, Miika Turkia wrote:
>>
>> I have not even tried to parse that, yet.
>>
>> So what should the setpo2 and measuredpo2 be translated to? And is
>> there anything else CC related that should be taken into account?
>
> Miika, I've no exact idea what the desired translation should be. I've
> no experience with the parser so far but in the following code in
> subsurface it will be used as po2 and ccpo2. Regarding the measuredpo2 -
> this is something we do not process in subsurface yet and Jef is also
> not feeding these data from libdivecomputer when handling my Shearwater
> Predator as of now. That said, I really like the sensor readings (and
> more data if available, battery voltage on Shearwater computers f.i.) to
> see in sometimes later releases of subsurface as I've some features in
> mind for them...

Dirk: can you shed a bit of light into the format Subsurface is
expecting for closed circuit? I did not spot any test dives that would
have revealed the expected format for po2.

> Is there an easy way for you to list all values you do not handle when
> translating the  data from the DR5?

I could not come up with anything that would have made any sense.
Basically getting the top level elements that are not handled is easy
enough, but I just could not figure out how to do the same for e.g.
the actual sample data.

Anyway, when looking at the
olibaumann_log_uddf__130203103820061119.uddf, the following samples
are ignored (under waypoint):
- otu
- setpo2
- measuredpo2 (for all sensors)

Other stuff that is not handled from that data file:
- generatore
- decomodel
- applicationdata
- surfaceinterval
- lowestoxygen
- greatestoxygen

miika