<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 27/10/2014 18:38, Paul Sargent
wrote:<br>
</div>
<blockquote cite="mid:46b329e8-50ff-4cfd-9ff0-04609d791411@me.com"
type="cite"><br>
<div>
<div>
<blockquote type="cite">
<div class="msg-quote">
<div class="_stretch"><span style="white-space:pre-wrap;"
data-mce-style="white-space: pre-wrap;">> <br>
> I'm certainly happy to look over as much as I
can, but it's limited by<br>
> what I can exercise from my dive data. As far as
I can tell a number of<br>
> the patches recently deal with utilising ppO2
data from the sensors, and<br>
> the only unit we can import ppO2 data from is a
MkVI. I don't dive a<br>
> MkVI, so whilst I can test planning CCR dives, or
imported constant ppO2<br>
> CCR dives from an OSTC, I can't exercise
everything.<br>
<br>
And that's fine.<br>
<br>
> Let me know what you'd like me to attack ;-)<br>
<br>
Everything that you CAN use. So for the dives that you
import, do the<br>
things that we show make sense? Is there a way they
could (should?) make<br>
more sense? Does the planning seem right? Pieces
missing?<br>
<br>
I simply notice that almost every time I do something
that I usually don't<br>
play much with, I quickly find little bugs. And I
worry that that's the<br>
experience for a lot of our users as well. And
especially since tech<br>
divers appear to be a reasonably big part of our user
base, I want to make<br>
sure we get this right :-)<br>
<br>
/D<br>
</span></div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
subsurface mailing list
<a class="moz-txt-link-abbreviated" href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a>
<a class="moz-txt-link-freetext" href="http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface</a>
</pre>
</blockquote>
<br>
Sorry for some absence. Was on a business trip (managed a few dives
on the side). <br>
I suggest that we focus in getting the Poseidon data logging working
accurately and reliably. Once the Poseidon stuff is in an acceptable
state, we use this as a platform to widen the range of CCR equipment
that can be logged. We need to see that the underlying data
structures for the Poseidon is rockstable, that the import reads a
whole diversity of Poseidon dives and that the visual presentation
is efficient and accurate. Currently there is no explicit provision
for bailout diving, only uncomplicated CCR. I think it should not be
complex to implement because the underlying data structures are
already in place. That is the obvious next step in finalising the
Poseidon code. But, for me, the first step is to see that the
existing code works well, before any expansion. The Qt side is
obviously becoming important now but I do not know whether Tomaz haz
any spare time at the moment.<br>
<br>
Does this make sense at all?<br>
<br>
I will really try to get more persons diving with Poseidon to do
some testing. I should be able to get at least one CCR instructor
that uses Poseidon extensively.<br>
<br>
The way that I feel, the APD Inspiration is the next one to tackle
because in some ways it would probably only use a subset of the
Poseidon features (although there are complexities generated by the
fact that it uses two computers), and Shearwater is obviously also
often used, but I am hesitant to touch that before the Poseidon
import works well. <br>
Kind regards,<br>
willen<br>
<br>
<br>
</body>
</html>