<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi All,</p>
<p>Joachim (R.) and I finished our first basic version of the
minimum gas calculation for the planner.<br>
We are now looking for testing and feedback :-)<br>
More details below...<br>
</p>
<p>Link to initial idea and discussion:<br>
<a class="moz-txt-link-freetext" href="https://github.com/Subsurface-divelog/subsurface/issues/188">https://github.com/Subsurface-divelog/subsurface/issues/188</a><br>
</p>
<p>Link to feature branch on Github:<br>
<a class="moz-txt-link-freetext" href="https://github.com/sfuchs79/subsurface/tree/feature_minimum_gas">https://github.com/sfuchs79/subsurface/tree/feature_minimum_gas</a></p>
<p><br>
</p>
<p>My feedback to comments from Robert and Joachim (B.):<br>
- Increased deco for longer bottom time due to problem solving
time: No, honestly this would have been much too complex for me at
the moment. Also this would not be according to how I would even
handle it during a real dive. But this may be a longer
discussion... ;-)<br>
- Real gases: Yes, hopefully implemented correctly.<br>
- No hard coded SAC*2: Yes, good idea, we didn't do this but for
the moment I limited SAC factor to min 2.0/max 10.0. 2.0 would be
two divers with unchanged SAC. SAC factor of e.g. 4.0 would be two
divers with doubled SAC. BTW: Setting problem solving time to 0min
comes close to "disabling" the feature.<br>
- Support rec dives: Yes, clearly, calculation is active for all
OC dives. I put some limitations for min depth (>18m) and min
tank size (12l). Calculating minimum gas for smaller cylinders is
from my point of view almost useless.<br>
- Calculating problem solving time as result: No, this would not
fit with my idea of doing and using it.<br>
</p>
<p>Open questions:<br>
- Most important: Any huge mistakes? Do we screw up s.th.? ;-)<br>
- What is missing? What else will we need to do? E.g.:<br>
o Everything ready for translations?<br>
o Which documentation would be mandatory?<br>
- Any dive setups where this should work but doesn't based on this
implementation? Remark: It is clear for me that this
implementation is currently only useful for limited types of dive
scenarios. <br>
</p>
<p>Possible enhancements I still have in my mind:<br>
- Print such a tiny little yellow warning flag in the profile when
minimum gas is exceeded before end of bottom time. Anyone could
guide me how to do this?<br>
- Tooltips for the new preferences. I can easily do this. One
question: What about line breaks in tooltips? Good/not good? How
do they work?<br>
</p>
<p><br>
</p>
<p>Best regards<br>
Stefan<br>
</p>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.3 (Win32)">
<meta name="CREATED" content="0;0">
<meta name="CHANGEDBY" content="Stefan Fuchs">
<meta name="CHANGED" content="20120503;23115492">
<style type="text/css">
<!--
P { color: #000000 }
-->
</style>
<p>Stefan Fuchs<br>
E-Mail: <a href="mailto:sfuchs@gmx.de">sfuchs@gmx.de</a></p>
</div>
</body>
</html>