mirror of
https://github.com/subsurface/subsurface.git
synced 2024-11-30 22:20:21 +00:00
4790 lines
221 KiB
Text
4790 lines
221 KiB
Text
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
|
||
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
|
||
<meta name="generator" content="AsciiDoc 8.6.8" />
|
||
<title></title>
|
||
<style type="text/css">
|
||
/*
|
||
* compact_subsurface.css, a special style sheet for Subsurface,
|
||
* modified by Willem Ferguson and derived from:
|
||
* compact.css, version 1.3 by Alex Efros <powerman@powerman.name>
|
||
* Licence: Public Domain
|
||
*
|
||
* Usage: asciidoc -a theme=compact_subsurface ...
|
||
*/
|
||
|
||
* { padding: 0; margin: 0; }
|
||
img { border: 0; }
|
||
|
||
/*** Layout ***/
|
||
|
||
body { margin: 10px 20px; }
|
||
#header br { display: none; }
|
||
#revnumber { display: block; }
|
||
#toc { margin: 1em 0; }
|
||
.toclevel2 { margin-left: 1em; }
|
||
.toclevel3 { margin-left: 2em; }
|
||
#footer { margin-top: 2em; }
|
||
|
||
#preamble .sectionbody,
|
||
h2,
|
||
h3,
|
||
h4,
|
||
h5 { margin: 1em 0 0 0; }
|
||
|
||
.admonitionblock,
|
||
.listingblock,
|
||
.sidebarblock,
|
||
.exampleblock,
|
||
.tableblock,
|
||
.literalblock { margin: 1em 0; }
|
||
.admonitionblock td.icon { padding-right: 0.5em; }
|
||
.admonitionblock td.content { padding-left: 0.5em; }
|
||
.listingblock .content { padding: 0.5em; }
|
||
.sidebarblock > .content { padding: 0.5em; }
|
||
.exampleblock > .content { padding: 0 0.5em; }
|
||
.tableblock caption { padding: 0 0 0.5em 0; }
|
||
.tableblock thead th,
|
||
.tableblock tbody td,
|
||
.tableblock tfoot td { padding: 0 0.5em; }
|
||
.quoteblock { padding: 0 2.0em; }
|
||
|
||
.paragraph { margin: 1em 0 0 0; }
|
||
.sidebarblock .paragraph:first-child,
|
||
.exampleblock .paragraph:first-child,
|
||
.admonitionblock .paragraph:first-child { margin: 0; }
|
||
|
||
.ulist, .olist, .dlist, .hdlist, .qlist { margin: 1em 0; }
|
||
li .ulist, li .olist, li .dlist, li .hdlist, li .qlist,
|
||
dd .ulist, dd .olist, dd .dlist, dd .hdlist, dd .qlist { margin: 0; }
|
||
ul { margin-left: 1.5em; }
|
||
ol { margin-left: 2em; }
|
||
dd { margin-left: 3em; }
|
||
td.hdlist1 { padding-right: 1em; }
|
||
|
||
/*** Fonts ***/
|
||
|
||
body { font-family: Verdana, sans-serif; }
|
||
#header { font-family: Arial, sans-serif; }
|
||
#header h1 { font-family: Arial, sans-serif; }
|
||
#footer { font-family: Georgia, serif; }
|
||
#email { font-size: 0.85em; }
|
||
#revnumber { font-size: 0.75em; }
|
||
#toc { font-size: 0.9em; }
|
||
#toctitle { font-weight: bold; }
|
||
#footer { font-size: 0.8em; }
|
||
|
||
h2, h3, h4, h5, .title { font-family: Arial, sans-serif; }
|
||
h2 { font-size: 1.5em; }
|
||
.sectionbody { font-size: 0.85em; }
|
||
.sectionbody .sectionbody { font-size: inherit; }
|
||
h3 { font-size: 159%; } /* 1.35em */
|
||
h4 { font-size: 141%; } /* 1.2em */
|
||
h5 { font-size: 118%; } /* 1em */
|
||
.title { font-size: 106%; /* 0.9em */
|
||
font-weight: bold;
|
||
}
|
||
|
||
tt, .monospaced { font-family: monospace; font-size: 106%; } /* 0.9em */
|
||
dt, td.hdlist1, .qlist em { font-family: Times New Roman, serif;
|
||
font-size: 118%; /* 1em */
|
||
font-style: italic;
|
||
}
|
||
.tableblock tfoot td { font-weight: bold; }
|
||
|
||
/*** Colors and Backgrounds ***/
|
||
|
||
h1 { color: #527bbd; border-bottom: 2px solid silver; }
|
||
#footer { border-top: 2px solid silver; }
|
||
|
||
h2 { color: #527bbd; border-bottom: 2px solid silver; }
|
||
h3 { color: #5D7EAE; border-bottom: 2px solid silver; }
|
||
h3 { display: inline-block; }
|
||
h4,h5 { color: #5D7EAE; }
|
||
|
||
.admonitionblock td.content { border-left: 2px solid silver; }
|
||
.listingblock .content { background: #f4f4f4; border: 1px solid silver; border-left: 5px solid #e0e0e0; }
|
||
.sidebarblock > .content { background: #ffffee; border: 1px solid silver; border-left: 5px solid #e0e0e0; }
|
||
.exampleblock > .content { border-left: 2px solid silver; }
|
||
.quoteblock { border-left: 5px solid #e0e0e0; }
|
||
.tableblock table {
|
||
border-collapse: collapse;
|
||
border-width: 3px;
|
||
border-color: #527bbd;
|
||
}
|
||
.tableblock table[frame=hsides] { border-style: solid none; }
|
||
.tableblock table[frame=border] { border-style: solid; }
|
||
.tableblock table[frame=void] { border-style: none; }
|
||
.tableblock table[frame=vsides] { border-style: none solid; }
|
||
.tableblock table[rules=all] tbody tr *,
|
||
.tableblock table[rules=rows] tbody tr * {
|
||
border-top: 1px solid #527bbd;
|
||
}
|
||
.tableblock table[rules=all] tr *,
|
||
.tableblock table[rules=cols] tr * {
|
||
border-left: 1px solid #527bbd;
|
||
}
|
||
.tableblock table tbody tr:first-child * {
|
||
border-top: 1px solid white; /* none don't work here... %-[] */
|
||
}
|
||
.tableblock table tr *:first-child {
|
||
border-left: none;
|
||
}
|
||
.tableblock table[frame] thead tr *,
|
||
.tableblock table[frame] thead tr * {
|
||
border-top: 1px solid white;
|
||
border-bottom: 2px solid #527bbd;
|
||
}
|
||
.tableblock table tr td p.table,
|
||
.tableblock table tr td p.table * {
|
||
border: 0px;
|
||
}
|
||
|
||
tt, .monospaced { color: navy; }
|
||
|
||
li { color: #a0a0a0; }
|
||
li > * { color: black; }
|
||
|
||
span.aqua { color: aqua; }
|
||
span.black { color: black; }
|
||
span.blue { color: blue; }
|
||
span.fuchsia { color: fuchsia; }
|
||
span.gray { color: gray; }
|
||
span.green { color: green; }
|
||
span.lime { color: lime; }
|
||
span.maroon { color: maroon; }
|
||
span.navy { color: navy; }
|
||
span.olive { color: olive; }
|
||
span.purple { color: purple; }
|
||
span.red { color: red; }
|
||
span.silver { color: silver; }
|
||
span.teal { color: teal; }
|
||
span.white { color: white; }
|
||
span.yellow { color: yellow; }
|
||
|
||
span.aqua-background { background: aqua; }
|
||
span.black-background { background: black; }
|
||
span.blue-background { background: blue; }
|
||
span.fuchsia-background { background: fuchsia; }
|
||
span.gray-background { background: gray; }
|
||
span.green-background { background: green; }
|
||
span.lime-background { background: lime; }
|
||
span.maroon-background { background: maroon; }
|
||
span.navy-background { background: navy; }
|
||
span.olive-background { background: olive; }
|
||
span.purple-background { background: purple; }
|
||
span.red-background { background: red; }
|
||
span.silver-background { background: silver; }
|
||
span.teal-background { background: teal; }
|
||
span.white-background { background: white; }
|
||
span.yellow-background { background: yellow; }
|
||
|
||
span.big { font-size: 2em; }
|
||
span.small { font-size: 0.6em; }
|
||
|
||
span.underline { text-decoration: underline; }
|
||
span.overline { text-decoration: overline; }
|
||
span.line-through { text-decoration: line-through; }
|
||
|
||
/*** Misc ***/
|
||
|
||
.admonitionblock td.icon { vertical-align: top; }
|
||
.attribution { text-align: right; }
|
||
|
||
ul { list-style-type: disc; }
|
||
ol.arabic { list-style-type: decimal; }
|
||
ol.loweralpha { list-style-type: lower-alpha; }
|
||
ol.upperalpha { list-style-type: upper-alpha; }
|
||
ol.lowerroman { list-style-type: lower-roman; }
|
||
ol.upperroman { list-style-type: upper-roman; }
|
||
.hdlist td { vertical-align: top; }
|
||
|
||
|
||
</style>
|
||
<script type="text/javascript">
|
||
/*<+'])');
|
||
// Function that scans the DOM tree for header elements (the DOM2
|
||
// nodeIterator API would be a better technique but not supported by all
|
||
// browsers).
|
||
var iterate = function (el) {
|
||
for (var i = el.firstChild; i != null; i = i.nextSibling) {
|
||
if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
|
||
var mo = re.exec(i.tagName);
|
||
if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
|
||
result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
|
||
}
|
||
iterate(i);
|
||
}
|
||
}
|
||
}
|
||
iterate(el);
|
||
return result;
|
||
}
|
||
|
||
var toc = document.getElementById("toc");
|
||
if (!toc) {
|
||
return;
|
||
}
|
||
|
||
// Delete existing TOC entries in case we're reloading the TOC.
|
||
var tocEntriesToRemove = [];
|
||
var i;
|
||
for (i = 0; i < toc.childNodes.length; i++) {
|
||
var entry = toc.childNodes[i];
|
||
if (entry.nodeName.toLowerCase() == 'div'
|
||
&& entry.getAttribute("class")
|
||
&& entry.getAttribute("class").match(/^toclevel/))
|
||
tocEntriesToRemove.push(entry);
|
||
}
|
||
for (i = 0; i < tocEntriesToRemove.length; i++) {
|
||
toc.removeChild(tocEntriesToRemove[i]);
|
||
}
|
||
|
||
// Rebuild TOC entries.
|
||
var entries = tocEntries(document.getElementById("content"), toclevels);
|
||
for (var i = 0; i < entries.length; ++i) {
|
||
var entry = entries[i];
|
||
if (entry.element.id == "")
|
||
entry.element.id = "_toc_" + i;
|
||
var a = document.createElement("a");
|
||
a.href = "#" + entry.element.id;
|
||
a.appendChild(document.createTextNode(entry.text));
|
||
var div = document.createElement("div");
|
||
div.appendChild(a);
|
||
div.className = "toclevel" + entry.toclevel;
|
||
toc.appendChild(div);
|
||
}
|
||
if (entries.length == 0)
|
||
toc.parentNode.removeChild(toc);
|
||
},
|
||
|
||
|
||
/////////////////////////////////////////////////////////////////////
|
||
// Footnotes generator
|
||
/////////////////////////////////////////////////////////////////////
|
||
|
||
/* Based on footnote generation code from:
|
||
* http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
|
||
*/
|
||
|
||
footnotes: function () {
|
||
// Delete existing footnote entries in case we're reloading the footnodes.
|
||
var i;
|
||
var noteholder = document.getElementById("footnotes");
|
||
if (!noteholder) {
|
||
return;
|
||
}
|
||
var entriesToRemove = [];
|
||
for (i = 0; i < noteholder.childNodes.length; i++) {
|
||
var entry = noteholder.childNodes[i];
|
||
if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
|
||
entriesToRemove.push(entry);
|
||
}
|
||
for (i = 0; i < entriesToRemove.length; i++) {
|
||
noteholder.removeChild(entriesToRemove[i]);
|
||
}
|
||
|
||
// Rebuild footnote entries.
|
||
var cont = document.getElementById("content");
|
||
var spans = cont.getElementsByTagName("span");
|
||
var refs = {};
|
||
var n = 0;
|
||
for (i=0; i<spans.length; i++) {
|
||
if (spans[i].className == "footnote") {
|
||
n++;
|
||
var note = spans[i].getAttribute("data-note");
|
||
if (!note) {
|
||
// Use [\s\S] in place of . so multi-line matches work.
|
||
// Because JavaScript has no s (dotall) regex flag.
|
||
note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
|
||
spans[i].innerHTML =
|
||
"[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
|
||
"' title='View footnote' class='footnote'>" + n + "</a>]";
|
||
spans[i].setAttribute("data-note", note);
|
||
}
|
||
noteholder.innerHTML +=
|
||
"<div class='footnote' id='_footnote_" + n + "'>" +
|
||
"<a href='#_footnoteref_" + n + "' title='Return to text'>" +
|
||
n + "</a>. " + note + "</div>";
|
||
var id =spans[i].getAttribute("id");
|
||
if (id != null) refs["#"+id] = n;
|
||
}
|
||
}
|
||
if (n == 0)
|
||
noteholder.parentNode.removeChild(noteholder);
|
||
else {
|
||
// Process footnoterefs.
|
||
for (i=0; i<spans.length; i++) {
|
||
if (spans[i].className == "footnoteref") {
|
||
var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
|
||
href = href.match(/#.*/)[0]; // Because IE return full URL.
|
||
n = refs[href];
|
||
spans[i].innerHTML =
|
||
"[<a href='#_footnote_" + n +
|
||
"' title='View footnote' class='footnote'>" + n + "</a>]";
|
||
}
|
||
}
|
||
}
|
||
},
|
||
|
||
install: function(toclevels) {
|
||
var timerId;
|
||
|
||
function reinstall() {
|
||
asciidoc.footnotes();
|
||
if (toclevels) {
|
||
asciidoc.toc(toclevels);
|
||
}
|
||
}
|
||
|
||
function reinstallAndRemoveTimer() {
|
||
clearInterval(timerId);
|
||
reinstall();
|
||
}
|
||
|
||
timerId = setInterval(reinstall, 500);
|
||
if (document.addEventListener)
|
||
document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
|
||
else
|
||
window.onload = reinstallAndRemoveTimer;
|
||
}
|
||
|
||
}
|
||
asciidoc.install(3);
|
||
/*]]>*/
|
||
</script>
|
||
</head>
|
||
<body class="article">
|
||
<div id="header">
|
||
</div>
|
||
<div id="content">
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Subsurface4Banner.png" alt="Banner" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><span class="big">USER MANUAL</span></p></div>
|
||
<div class="paragraph"><p><strong>Manual authors</strong>: Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,
|
||
Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat</p></div>
|
||
<div class="paragraph"><p><span class="blue"><em>Version 4.2, August 2014</em></span></p></div>
|
||
<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, an advanced dive logging program with
|
||
extensive infrastructure to describe, organise, interpret and print scuba
|
||
and free dives. <em>Subsurface</em> offers many advantages over other similar
|
||
software solutions:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Do you use two different dive computer brands, each with its own proprietary
|
||
software for downloading dive logs? Do you dive with rebreathers as well
|
||
as open circuit? Do you use a Reefnet Sensus time-depth recorder
|
||
in conjunction with a dive computer? <em>Subsurface</em> offers a standard
|
||
interface for downloading dive logs from all these different pieces of
|
||
equipment and to store and analyse the dive logs within a unified system.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do you use more than one operating system? <em>Subsurface</em> is fully compatible
|
||
with Mac, Linux and Windows, allowing you to access your dive log on each
|
||
of your operating systems with a single application.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do you use Linux or Mac and your dive computer has only Windows-based software
|
||
for downloading dive information (e.g. Mares)? <em>Subsurface</em> provides a way of
|
||
storing and analysing your dive logs on other operating systems.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> binaries are available for Windows PCs (Win XP or later), Intel
|
||
based Macs (OS/X) and many Linux distributions. <em>Subsurface</em> can be built for
|
||
many more hardware platforms and software environments where Qt and
|
||
libdivecomputer are available.</p></div>
|
||
<div class="paragraph"><p>The scope of this document is the use of the <em>Subsurface</em> program. To install
|
||
the software, consult the <em>Downloads</em> page on the
|
||
<a href="http://subsurface.hohndel.org/"><em>Subsurface</em> web site</a>.
|
||
Please discuss issues with this program by sending an email to
|
||
<a href="mailto:subsurface@hohndel.org">our mailing list</a> and report bugs at
|
||
<a href="http://trac.hohndel.org">our bugtracker</a>. For instructions on how to build the
|
||
software and (if needed) its dependencies please consult the INSTALL file
|
||
included with the source code.</p></div>
|
||
<div class="paragraph"><p><strong>Audience</strong>: Recreational Scuba Divers, Free Divers, Tec Divers, Professional
|
||
Divers</p></div>
|
||
<div id="toc">
|
||
<div id="toctitle">Table of Contents</div>
|
||
<noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_UserSurvey">1. The user survey</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>In order to develop <em>Subsurface</em> in a way that serves its users in the best possible way,
|
||
it is important to have some user information. Upon launching <em>Subsurface</em>
|
||
after using this software for a week or so, a one-box user survey pops up. It is entirely
|
||
optional and the user controls what, if any, data are sent to the <em>Subsurface</em> development
|
||
team. Any data that the user chooses to send is extremely useful, and will only be
|
||
used to steer future development and to customise the software to fit the needs of
|
||
the <em>Subsurface</em> users. If one completes the survey, or clicks the option not to
|
||
be asked again, that should be the last communication of this nature one receives.
|
||
However, if one’s diving and/or subsurface habits change and one wishes to provide
|
||
another survey, this can be done by launching <em>Subsurface</em> with the <em>--survey</em> option on the
|
||
command line.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_StartUsing">2. Start Using the Program</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>The <em>Subsurface</em> window is usually divided into four panels with a <strong>Main
|
||
Menu</strong> (File Import Log View Filter Help) at the top of the window (for Windows
|
||
and Linux) or the top of the screen (for Mac and Ubuntu Unity). The four panels are:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
The <strong>Dive List</strong> to the bottom left containing a list of all the dives in the
|
||
user’s
|
||
dive log. A dive can be selected and highlighted on the dive list by clicking on
|
||
it. In most situations the up/down keys can be used to switch
|
||
between dives. The <strong>Dive List</strong> is an important tool for manipulating a dive log.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The <strong>Dive Map</strong> to the bottom right, showing the user’s dive sites on a world
|
||
map
|
||
and centred on the site of the last dive selected in the <strong>Dive List</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The <strong>Dive Info</strong> to the top left, giving more detailed information on the
|
||
dive selected in the <strong>Dive List</strong>, including some statistics for the selected dive or for all
|
||
highlighted dive(s).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The <strong>Dive Profile</strong> to the top right, showing a graphical dive profile of the
|
||
selected dive in the <strong>Dive List</strong>.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>The dividers between panels can be dragged in order to change the size of any of
|
||
the panels. <em>Subsurface</em> remembers the position of the dividers, so the next
|
||
time <em>Subsurface</em> starts it uses the positions of the dividers from when the program
|
||
was last used.</p></div>
|
||
<div class="paragraph"><p>If a dive is selected in the <strong>Dive List</strong>, the dive location, detailed information
|
||
and profile of
|
||
the <em>selected dive</em> are shown in the respective panels. On the other hand, if
|
||
one highlights more than one dive the last highlighted dive is the <em>selected
|
||
dive</em>, but summary data of all <em>highlighted dives</em> are shown in the <strong>Stats</strong> tab
|
||
of the <strong>Dive Info</strong> panel (maximum, minimum and average depths, durations, water
|
||
temperatures and SAC; total time and number of dives selected).</p></div>
|
||
<div class="imageblock" id="S_ViewPanels" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/main_window.jpg" alt="The Main Window" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The user can determine which of the four panels are displayed by selecting the
|
||
<strong>View</strong> option on the main menu. This feature gives the user several choices of
|
||
display:</p></div>
|
||
<div class="paragraph"><p><strong>All</strong>: show all four of the panels as in the screenshot above.</p></div>
|
||
<div class="paragraph"><p><strong>Divelist</strong>: Show only the Dive List.</p></div>
|
||
<div class="paragraph"><p><strong>Profile</strong>: Show only the Dive Profile of the selected dive.</p></div>
|
||
<div class="paragraph"><p><strong>Info</strong>: Show only the Dive Notes about the last selected dive and statistics for
|
||
all highlighted dives.</p></div>
|
||
<div class="paragraph"><p><strong>Globe</strong>: Show only the world map, centred on the last selected dive.</p></div>
|
||
<div class="paragraph"><p>Like many other functions that can be accessed via the Main Menu, these options
|
||
can be triggered using keyboard shortcuts. The shortcuts for a particular system
|
||
are shown with an underline in the main menu entries. Since different Operating
|
||
Systems and the user chosen language may cause <em>Subsurface</em> to use different
|
||
shortcut keys they are not listed here in the user manual.</p></div>
|
||
<div class="paragraph"><p>When the program is started for the first time, it shows no information at all.
|
||
This is because the program doesn’t have any dive information available. In the
|
||
following sections, the procedures to create a new logbook will be described.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_NewLogbook">3. Creating a new logbook</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Select <em>File → New Logbook</em> from the main menu. All existing dive data are
|
||
cleared so that new information can be added. If there are unsaved data in an
|
||
open logbook, the user is asked whether the open logbook should be
|
||
saved before a new logbook is created.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_GetInformation">4. How to store dive information in the user’s logbook</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>There are several ways in which dive information can be added to a logbook:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Enter dive information by hand. This is typically useful if the diver did not
|
||
use a dive computer and dives were recorded in a written logbook.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Import dive information directly from a dive computer if it is supported by
|
||
<em>Subsurface</em>. The latest list of dive computers supported by <em>Subsurface</em> can
|
||
be found at:
|
||
<a href="http://subsurface.hohndel.org/documentation/supported-dive-computers/">
|
||
Supported dive computers</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Import dive information from another database or file format. If you
|
||
have kept your dive logs with other log software, these logs can often
|
||
be imported to subsurface. This is discussed in more detail below.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="sect2">
|
||
<h3 id="S_EnterData">4.1. Entering dive information by hand</h3>
|
||
<div class="paragraph"><p>This is usually the approach for dives without a dive computer. The basic record
|
||
of information within <em>Subsurface</em> is a dive. The most important information
|
||
in a simple dive logbook usually includes dive type, date, time, duration,
|
||
depth, the names of your dive buddy and of the dive master or dive guide, and
|
||
some remarks about the dive. <em>Subsurface</em> can store much more information
|
||
than this for each dive. In order to add a dive to a dive log, select <em>Log
|
||
→ Add Dive</em> from the Main Menu. The program then shows three panels to enter
|
||
information for a dive: two tabs in the <strong>Dive Info</strong> panel (<strong>Dive Notes</strong> and
|
||
<strong>Equipment</strong>), as well as the <strong>Dive Profile</strong> panel that displays a graphical profile
|
||
of each dive. These panels are respectively marked <span class="red">A</span>, <span class="red">B</span> and
|
||
<span class="red">C</span>
|
||
in the figure below. Each of these tabs will now be explained for data entry.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/AddDive1.jpg" alt="FIGURE: Add dive" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>When one edits a field in Dive notes or Equipment panels, <em>Subsurface</em> enters <strong>Editing Mode</strong>,
|
||
indicated by the message in the blue box at the top of the <em>Dive Notes</em> panel. This message is
|
||
displayed in all the panels under Dive notes and Equipment when in <strong>Editing Mode</strong>.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_dive_notes">4.1.1. Dive Notes</h4>
|
||
<div class="paragraph"><p>This panel contains the date, time and place information for a particular dive,
|
||
environmental conditions, co-divers and buddies, as well as some descriptive
|
||
information. If one clicks on the <strong>Dive Notes</strong> tab, the following
|
||
fields are visible:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/AddDive2.jpg" alt="FIGURE: The Dive Notes tab" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The <strong>Time</strong> field reflects the date and the time of the dive. By clicking
|
||
the date, a calendar is displayed from which
|
||
one can choose the correct date. Press ESC to escape from the calendar.
|
||
The time values (hour and minutes) can also be
|
||
edited directly by clicking on each of them in the text box and by overtyping the
|
||
information displayed. The default date is the present date and the default time is
|
||
an hour in advance of the present time.</p></div>
|
||
<div class="paragraph"><p><strong>Air and water temperatures</strong>: the air and water temperatures during the
|
||
dive can be typed directly on the fields to the right of the Start time.
|
||
Temperature units are not needed, as they will be automatically supplied by
|
||
<em>Subsurface</em>. Only the numerical value must be
|
||
typed by the user (the units selected in the <em>Preferences</em>
|
||
will determine whether metric or imperial units are used).</p></div>
|
||
<div class="paragraph"><p><strong>Location</strong>: Here the name of the dive site can be entered, e.g. "Tihany, Lake
|
||
Balaton,
|
||
Hungary". Auto completion of location names will make this easier if one
|
||
frequently dives at the same sites.</p></div>
|
||
<div class="paragraph"><p><strong>Coordinates</strong>: The geographic coordinates of the dive site should be entered
|
||
here. These can come from three sources:</p></div>
|
||
<div class="olist loweralpha"><ol class="loweralpha">
|
||
<li>
|
||
<p>
|
||
One can find the coordinates on the world map in the bottom right hand
|
||
part
|
||
of the Subsurface window. The map displays a green bar indicating "No location
|
||
data - Move the map and double-click to set the dive location". Upon a double-click
|
||
at the appropriate place, the green bar disappears and the coordinates are
|
||
stored.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The coordinates can be obtained from the <em>Subsurface</em> Companion app if the
|
||
user has an Android device with GPS and if the coordinates of the dive site
|
||
were stored using that device.
|
||
<a href="#S_Companion">Click here for more information</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The coordinates can be entered by hand if they are known, using one of
|
||
four formats with latitude followed by longitude:
|
||
</p>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
|
||
Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
|
||
Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
|
||
Decimal degrees, e.g. 30.22496 , 30.821798</code></pre>
|
||
</div></div>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Southern hemisphere latitudes are given with a <strong>S</strong>, e.g. S30°, or with a
|
||
negative value, e.g. -30.22496. Similarly western longitudes are given with a
|
||
<strong>W</strong>, e.g. W07°, or with a negative value, e.g. -7.34323.</p></div>
|
||
<div class="paragraph"><p>Please note that GPS coordinates of a dive site are linked to the Location
|
||
name - so adding coordinates to dives that do not have a location description
|
||
will cause unexpected behaviour (Subsurface will think that all of these
|
||
dives have the same location and try to keep their GPS coordinates the
|
||
same).</p></div>
|
||
<div class="paragraph"><p><strong>Divemaster</strong>: The name of the dive master or dive guide for this dive can be
|
||
entered here.
|
||
Again, this field offers auto completion based on the list of dive masters in
|
||
the current logbook.</p></div>
|
||
<div class="paragraph"><p><strong>Buddy</strong>: In this field one can enter the name(s) of the buddy / buddies
|
||
(separated by commas) who accompanied the user on the dive. Auto completion
|
||
is offered based on the list of buddies in the current logbook.</p></div>
|
||
<div class="paragraph"><p><strong>Suit</strong>: The type of diving suit used for the dive can be entered here.
|
||
As with the other items, auto completion of the suit description is available.
|
||
Some dry-suit users may choose to use this field to record what combination of
|
||
suit and thermal protection undersuit was used.</p></div>
|
||
<div class="paragraph"><p><strong>Rating</strong>: One can provide a subjective overall rating of the dive on a
|
||
5-point scale by clicking the appropriate star on the rating scale.</p></div>
|
||
<div class="paragraph"><p><strong>Visibility</strong>: Similarly, one can provide a rating of visibility during the
|
||
dive on a
|
||
5-point scale by clicking the appropriate star.</p></div>
|
||
<div class="paragraph"><p><strong>Tags</strong>: Tags that describe the type of dive performed may
|
||
be entered here (separated by commas). Examples of common tags are boat, drift,
|
||
training, cave etc. <em>Subsurface</em> has many built-in tags. Auto completion is once again offered.
|
||
For instance, if <code>cav</code> was typed, then the tags <strong>cave</strong> and <strong>cavern</strong> are
|
||
shown for the user to choose from.</p></div>
|
||
<div class="paragraph"><p><strong>Notes</strong>: Any additional information can be typed here.</p></div>
|
||
<div class="paragraph"><p>The <strong>Save</strong> and <strong>Cancel</strong> buttons are used to save all the information for tabs in
|
||
the info panel and in the dive profile panel, so there’s no need to use them
|
||
until ALL other information has been added. Here is an example of a completed
|
||
Dive Notes panel:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CompletedDiveInfo.jpg" alt="FIGURE: A completed Dive Notes tab" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_equipment">4.1.2. Equipment</h4>
|
||
<div class="paragraph"><p>The Equipment tab allows the user to enter information about the type of
|
||
cylinder and gas used, as well as the weights used for a dive. This is a highly interactive part of
|
||
<em>Subsurface</em> and the information on
|
||
cylinders and gases (entered here) affects the behaviour of the dive profile
|
||
(top right-hand panel).</p></div>
|
||
<div class="paragraph" id="S_CylinderData"><p><strong>Cylinders</strong>: The cylinder information is entered through a dialogue that looks
|
||
like this:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Gas_dialogue1.jpg" alt="FIGURE:Initial cylinder dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The + button at the top right allows the user to add more cylinders for this
|
||
dive.
|
||
The dark dustbin icon on the left allows one to delete information for a
|
||
particular cylinder. Note that it is not possible to delete a cylinder if it is used during the
|
||
dive. One cylinder is implicitly used in the dive, even without a gas change event. Thus the first
|
||
cylinder cannot be deleted until another cylinder is created.</p></div>
|
||
<div class="paragraph"><p>Start by selecting a cylinder type on the left-hand side of the
|
||
table. To select a cylinder, click in the <strong>Type</strong> box.
|
||
This brings up a button that can be used to display a dropdown list of
|
||
cylinders:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Gas_dialogue2.jpg" alt="FIGURE:The cylinder drop-down list button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The drop-down list can be used to select the cylinder type used
|
||
for the dive or the user may start typing in the box which shows the
|
||
available options for the entered characters. The
|
||
<strong>Size</strong> of the cylinder as well as its working pressure (<strong>WorkPress</strong>) will
|
||
automatically be shown in the dialogue. If a cylinder is not shown in the dropdown list,
|
||
type the name and description of that cylinder into the <strong>Type</strong> field.</p></div>
|
||
<div class="paragraph"><p>Next, indicate the starting pressure and the ending pressure of
|
||
the
|
||
gas used during the dive. The unit of pressure (metric/imperial) corresponds
|
||
to the setting in the <em>Preferences</em>.</p></div>
|
||
<div class="paragraph"><p>Finally, type in the gas mixture used in the <strong>O2%</strong> field. If air
|
||
was used, a value of 21% can be entered on this field, or it might be
|
||
left blank. If nitrox or trimix were used, their percentages of oxygen and/or
|
||
helium must be specified.
|
||
Any inappropriate fields should be left empty. After typing the information for
|
||
the cylinder, press <em>ENTER</em> on the keyboard or click
|
||
outside the cell that contains the cursor. Information for any additional
|
||
cylinders can be added by using the + button at the top right hand. Following
|
||
is an example of a complete description for a
|
||
dive made using two cylinders (air and EAN50):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CylinderDataEntry3.jpg" alt="FIGURE: a completed cylinder dive information table" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Weights</strong>: Information about the weight system used during a dive can be entered
|
||
using a dialogue very similar to that for the cylinder information. If the user
|
||
clicks the + button on the top right of the weights dialogue, the table looks
|
||
like this:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry1.jpg" alt="FIGURE: The Weights dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>If one then clicks on the <strong>Type</strong> field, a drop-down list becomes accessible
|
||
through a down-arrow:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry2.jpg" alt="FIGURE: Weights type drop-down list button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The drop-down list can then be used to select the type of weight system or the user may start
|
||
typing in the box which shows the available options for the entered characters. In
|
||
the <strong>Weight</strong>
|
||
field, the weight used during the dive must be typed. After typing the
|
||
information
|
||
for the weight system the user must either press <em>ENTER</em> on the keyboard or
|
||
click outside the
|
||
cell that contains the cursor. It is possible to enter
|
||
information for more than one weight system by adding an additional system using
|
||
the + button on the top right hand. Weight systems can be deleted using the
|
||
dustbin icon on the left hand. Here is an example of information for a dive
|
||
with two types of weights: integrated and a weight belt:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry3.jpg" alt="FIGURE: A completed weights information table" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>There’s NO need to click the <em>Save</em> button before the dive
|
||
profile has been completed.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_CreateProfile">4.1.3. Creating a Dive Profile</h4>
|
||
<div class="paragraph"><p>The <strong>Dive Profile</strong> (a graphical representation of the depth of the dive as a
|
||
function of time) is indicated in the panel on the top right hand of the
|
||
<em>Subsurface</em> window. When a dive is manually added to a logbook, <em>Subsurface</em>
|
||
presents a default dive profile that needs to be modified to best represent the
|
||
dive being described:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DiveProfile1.jpg" alt="FIGURE: Initial dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><em>Modifying the dive profile</em>: When the cursor is moved around the dive profile,
|
||
its position is indicated by two coloured lines (red and green) as shown below.
|
||
The depth and time
|
||
that the cursor represents are indicated at the top of the black information box
|
||
(@ and D). The units (metric/imperial) on the axes are determined by the
|
||
<strong>Preference</strong> settings. The dive profile itself comprises several
|
||
line segments demarcated by waypoints (white dots on the profile, as shown
|
||
above). The default dive depth is 15 m.
|
||
If the dive depth was 20 m then the user needs to drag the appropriate waypoints
|
||
downwards to represent 20 m. To add a waypoint, double-click on
|
||
any line segment. To move an additional waypoint, drag it.
|
||
To remove this waypoint, right-click on it and choose "Remove this point" from the
|
||
context menu. The user needs to drag the waypoints to represent an
|
||
accurate
|
||
time duration for the dive. Below is a dive profile that represents a dive
|
||
to 20 m for 30 min, followed by a 5 minute safety stop at 5 m.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DiveProfile2.jpg" alt="FIGURE: Edited dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><em>Specifying the gas composition:</em> The gas composition used is clearly indicated
|
||
along the line segments of the dive profile. This defaults to the first gas
|
||
mixture specified in the <strong>Equipment</strong> tab, which was air in the case of the
|
||
profile illustrated above. The gas mixtures of segments of the dive profile can
|
||
be edited. This is done by right-clicking on the particular
|
||
waypoint and selecting the appropriate gas from the context menu. Changing
|
||
the gas for a waypoint affects the gas shown in the segment <em>to the left</em> of
|
||
that
|
||
waypoint. Note that only the gases defined in the <strong>Equipment</strong> tab appear in the
|
||
context menu.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DiveProfile3.jpg" alt="FIGURE: Gas composition context menu" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Below is the profile of a dive to 20 m for 30 min and with a switch from air to
|
||
EAN50 at the end of the duration at 20m. In this case the first cylinder in the
|
||
<strong>Equipment</strong> tab contained air and the second cylinder contained EAN50.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DiveProfile4.jpg" alt="FIGURE: Completed dive profile" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_saving_the_hand_entered_dive_information">4.1.4. Saving the hand-entered dive information</h4>
|
||
<div class="paragraph"><p>The information entered in the <strong>Dive Notes</strong> tab, the <strong>Equipment</strong> tab as well as
|
||
the <strong>Dive Profile</strong> can now be saved in the user’s logbook by using the two
|
||
buttons
|
||
on the top right hand of the Dive Notes tab. If the <em>Save</em> button is clicked,
|
||
the dive data
|
||
are saved in the current logbook. If the <em>Cancel</em> button is clicked, the newly
|
||
entered
|
||
dive data are discarded. When exiting <em>Subsurface</em>, the user will be prompted
|
||
once more to save the logbook with the new dive(s).</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportDiveComputer">4.2. Importing new dive information from a Dive Computer</h3>
|
||
<div class="sect3">
|
||
<h4 id="_connecting_and_importing_data_from_a_dive_computer">4.2.1. Connecting and importing data from a dive computer.</h4>
|
||
<div class="paragraph"><p>The use of dive computers allows the collection of a large amount of
|
||
information about
|
||
each dive, e.g. a detailed record of depth, duration, rates of ascent/descent
|
||
and of gas partial pressures. <em>Subsurface</em> can capture this information and
|
||
present it as part of the dive information, using dive
|
||
information from a wide range of dive computers. The latest list of supported
|
||
dive computers can be found at:
|
||
<a href="http://subsurface.hohndel.org/documentation/supported-dive-computers/">
|
||
Supported dive computers</a>.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Several dive computers consume more power when they are in their
|
||
PC-Communication mode. <strong>This could drain the dive computer’s battery</strong>. We
|
||
therefore
|
||
recommend that the user checks if the dive computer is charged when
|
||
connected to the USB port of a PC. For example, several Suunto and Mares dive
|
||
computers do not recharge through the USB connection. Users should refer to
|
||
the dive computer’s manual
|
||
if they are unsure whether the dive computer recharges its batteries
|
||
while connected to the USB port.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>To import dive information from a dive computer to a computer with
|
||
<em>Subsurface</em>,
|
||
it is necessary that the two pieces of equipment communicate with one another.
|
||
This
|
||
involves setting up the communications port (or mount point) of the computer
|
||
with <em>Subsurface</em> that communicates with the dive computer. In order to set up
|
||
this communication, one needs to find the appropriate information to
|
||
instruct
|
||
<em>Subsurface</em> where and how to import the dive information.
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a>
|
||
provides the technical information to help the user achieving this for different
|
||
operating
|
||
systems and
|
||
<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a>
|
||
has dive computer specific information.</p></div>
|
||
<div class="paragraph"><p>After this, the dive computer can be hooked up to the user’s PC, which can be
|
||
achieved by following these steps:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
The interface cable should be connected to a free USB port (or the Infra-red
|
||
or Bluetooth connection set up as described later in this manual)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The dive computer should be placed into PC Communication mode.
|
||
(Users should refer to the manual of their specific dive computer)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In <em>Subsurface</em>, from the Main Menu, the user must select <em>Import → Import
|
||
From Dive Computer</em>.
|
||
Dialogue <strong>A</strong> in the figure below appears:
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/ImportFromDC1.jpg" alt="FIGURE: Download dialogue 1" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Dive computers tend to keep a certain number of dives in their memory, even
|
||
though these dives have already been imported to <em>Subsurface</em>. For that reason
|
||
<em>Subsurface</em> only imports dives that have not been uploaded before. This makes
|
||
the download process faster on most dive computers and also saves battery power
|
||
of the dive computer (at least for those not charging while connected via USB).
|
||
If, for some reason, the user wishes to import ALL dives from the dive computer,
|
||
even though some may already be in the logbook, then check the check box labelled
|
||
<em>Force download of all dives</em>.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The dialogue has two drop-down lists, <strong>Vendor</strong> and <strong>Dive Computer</strong>. On the
|
||
<strong>vendor</strong> drop-down list select the make of the computer, e.g.
|
||
Suunto, Oceanic,
|
||
Uwatec, Mares. On the <strong>Dive Computer</strong> drop-down list, the model name of
|
||
the dive computer must be selected, e.g. D4 (Suunto), Veo200 (Oceanic), or Puck
|
||
(Mares).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The <strong>Device or Mount Point</strong> drop-down list contains the USB or Bluetooth port
|
||
name that <em>Subsurface</em> needs in order to communicate with the dive computer.
|
||
The appropriate port name must be selected. Consult
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a>
|
||
and
|
||
<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a>
|
||
for technical details on how to find the appropriate port information for a
|
||
particular dive
|
||
computer and, in some cases, how to do the correct settings to the operating
|
||
system of the computer on which <em>Subsurface</em> is running.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If all the dives on the dive computer need to be downloaded, check the
|
||
checkbox <em>Force download of all dives</em>. Normally, <em>Subsurface</em> only downloads
|
||
dives after the date-time of the last dive in the <strong>Dive List</strong> panel. If one
|
||
or more of your dives in <em>Subsurface</em> have been accidentally deleted or if there
|
||
are older dives that still need to be downloaded from the dive computer, this
|
||
checkbox needs to be activated. Some dive computers (e.g. Mares Puck) do not provide
|
||
a contents list to <em>Subsurface</em> before the download in order to select only new dives.
|
||
Consequently, for these dive computers, all dives are downloaded
|
||
irrespective of the status of this check box.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If the checkbox <em>Always prefer downloaded dives</em>
|
||
has been checked and, during download, dives with identical date-times exist on
|
||
the dive computer and on the <em>Subsurface</em>
|
||
<strong>Dive List</strong> panel, the record in the <em>Subsurface</em> divelog will be overwritten
|
||
by the record from the dive computer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do <strong>not</strong> check the checkboxes labelled <em>Save libdivecomputer logfile</em> and
|
||
<em>Save libdivecomputer dumpfile</em>. These are only used as diagnostic tools
|
||
when problems with downloads are experienced (see below).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The <em>OK</em> button must then be clicked. Dialogue <strong>B</strong> in the figure above
|
||
appears.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
With communication established, one can see how the data are
|
||
retrieved from the dive computer.
|
||
Depending on the make of the dive computer and/or number of recorded dives, this
|
||
could take some time. The user should be patient. The <em>Download</em> dialogue
|
||
shows a
|
||
progress bar at the bottom of the dialogue (for some dive computers the
|
||
progress information could be inaccurate as we cannot determine how much
|
||
downloadable data there is until all data have been downloaded). When the
|
||
download of the dive information is complete, all the imported dives appear
|
||
in the <strong>Dive List</strong>, sorted by date and time. Disconnect and
|
||
switch off the dive
|
||
computer to conserve its battery power.
|
||
If a particular dive is selected, the <strong>Dive Profile</strong> panel shows an informative
|
||
graph of dive depth against time for that particular dive.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If there is a problem in communicating with the dive computer, an error
|
||
message will be shown, similar to this text: "Unable to open /dev/ttyUSB0 Mares
|
||
(Puck Pro)". Refer to the text in the box below.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sidebarblock">
|
||
<div class="content">
|
||
<div class="paragraph"><p><strong>PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?</strong></p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Check the following:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Is the dive computer still in PC-communication or
|
||
Upload mode?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Is the battery of the dive computer fully charged? If not then the battery
|
||
must be charged or replaced.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Is the connecting cable faulty? Does the cable work perfectly using other
|
||
software? Has it worked before, or is this the first time the cable is being used? Are the contacts
|
||
on the dive computer and the cable clean?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Consult
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a>
|
||
and make sure that the correct Mount Point
|
||
was specified (see above).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
On Unix-like operating systems, does the user have write permission to the
|
||
USB port? If not, consult
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If the <em>Subsurface</em> computer does not recognise the USB adaptor by
|
||
showing an appropriate device name next to the Mount Point, then there is a
|
||
possibility that the cable or USB adaptor is faulty. A faulty cable is the most
|
||
common cause of communication failure between dive computer and <em>Subsurface</em>
|
||
computer. It is also possible that the <em>Subsurface</em> computer cannot interpret
|
||
the data. Perform a download for diagnostic purposes with the following
|
||
two check boxes checked in the download dialogue discussed above:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Save libdivecomputer logfile
|
||
Save libdivecomputer dumpfile</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p><strong>Important</strong>: These check boxes are only used when problems are encountered
|
||
during the download process: under normal circumstances they should not be checked.
|
||
When checking these boxes, the user is prompted to select a folder to
|
||
save the information to. The default folder is the one in which the <em>Subsurface</em>
|
||
dive log is kept.</p></div>
|
||
<div class="paragraph"><p><strong>Important:</strong> <em>After downloading with the above checkboxes
|
||
checked, no dives are added to the
|
||
<strong>Dive List</strong> but two files are created in the folder selected above</em>:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>subsurface.log
|
||
subsurface.bin</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>These files should be send to the <em>Subsurface</em> mail list:
|
||
<em>subsurface@hohndel.org</em> with a
|
||
request for the files to be analysed. Provide the dive computer
|
||
make and model
|
||
as well as contextual information about the dives recorded on the dive computer.</p></div>
|
||
</div></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_DeviceNames">4.2.2. Changing the name of a dive computer</h4>
|
||
<div class="paragraph"><p>It may be necessary to distinguish between different dive computers used to
|
||
upload dive logs to <em>Subsurface</em>. For instance if one’s partner’s dive computer is the
|
||
same make and model as one’s own and dive logs are uploaded from both dive computers
|
||
to the same <em>Subsurface</em> computer, then
|
||
one would perhaps like to call one dc "Alice’s Suunto D4" and the other one
|
||
"Bob’s Suunto D4". Alternatively, perhaps a technical diver dives with two or more
|
||
dive computers of the same model, the logs of both (or all) being uploaded.
|
||
In this case it might be prudent to call one of them
|
||
"Suunto D4 (1)" and another one "Suunto D4 (2)". This is easily done in <em>Subsurface</em>.
|
||
On the <strong>Main Menu</strong>, select <em>Log → Edit device names</em>. A dialog opens, indicating the
|
||
current Model, ID and Nickname of the dive computers used for upload. Edit the Nickname
|
||
field for the appropriate dive computer. After saving the Nickname, the dive logs
|
||
show the nickname for that particular device instead of the model name,
|
||
allowing easy identification of devices.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_EditDiveInfo">4.2.3. Updating the dive information imported from the dive computer.</h4>
|
||
<div class="paragraph"><p>The information from the dive computer is not complete and more
|
||
details must be added in order to have a fuller record of the dives. To
|
||
do this,
|
||
the <strong>Dive Notes</strong> and the <strong>Equipment</strong> tabs on the top left hand of the
|
||
<em>Subsurface</em> window should be used.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_dive_notes_2">4.2.4. Dive Notes</h4>
|
||
<div class="paragraph"><p>The date and time of the dive, gas mixture and (often) water temperature is
|
||
shown as obtained from the dive computer, but the user needs to add some
|
||
additional information by hand in order to have a more complete dive record.
|
||
If the contents of this tab is changed or edited in any way, the message in a blue box at
|
||
the top of the panel indicates that the dive is being edited. If one
|
||
clicks on the <strong>Dive Notes</strong> tab, the following fields are
|
||
visible:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/AddDive3.jpg" alt="FIGURE: The Dive Notes tab" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The <strong>Time</strong> field reflects the date and time of the dive. By clicking
|
||
the date, a calendar is displayed from which
|
||
one can choose the correct date. Press ESC to close the calendar.
|
||
The time values (hour and minutes) can also be
|
||
edited directly by clicking on each of them in the text box and by overtyping the
|
||
information displayed.</p></div>
|
||
<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown
|
||
in these fields to the right of the Start time. Many dive computers supply water
|
||
temperature information and this field may therefore contain information obtained from the dive computer.
|
||
If air temperature is not provided by the dive computer, the first temperature reading
|
||
might be used for the air temperature. Generally this is close enough to the real air temperature as
|
||
the change in the temperature sensor reading is quite slow to follow the changes in the environment.
|
||
If editing is required, only a value is required, the units of temperature will be
|
||
automatically supplied by
|
||
<em>Subsurface</em> (according to the <em>Preferences</em>, metric or imperial units will
|
||
be used).</p></div>
|
||
<div class="paragraph"><p><strong>Location</strong>: In this field one should type in text that describes the site
|
||
where the dive was performed, e.g. "Tihany, Lake Balaton, Hungary".
|
||
Auto completion of location names will
|
||
make this easier if one frequently dives at the same sites.</p></div>
|
||
<div class="paragraph"><p><strong>Coordinates</strong>: The geographic coordinates of the dive site should be entered
|
||
here. These can come from three sources:</p></div>
|
||
<div class="olist loweralpha"><ol class="loweralpha">
|
||
<li>
|
||
<p>
|
||
The user can find the coordinates on the world map in the bottom right hand
|
||
part
|
||
of the Subsurface window. The map displays a green bar indicating "Move the map
|
||
and double-click to set the dive location". Double-click
|
||
at the appropriate place, the green bar disappears and the coordinates are
|
||
stored.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The user can obtain the coordinates from the <em>Subsurface</em> Companion app if
|
||
an Android device with GPS was used and if the coordinates of the dive site
|
||
were stored using that device.
|
||
<a href="#S_Companion">Click here for more information</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The coordinates can be entered by hand if they are known, using one of
|
||
four formats with latitude followed by longitude:
|
||
</p>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
|
||
Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
|
||
Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
|
||
Decimal degrees, e.g. 30.22496 , 30.821798</code></pre>
|
||
</div></div>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Southern hemisphere latitudes are given with a <strong>S</strong>, e.g. S30°, or with a
|
||
negative value, e.g. -30.22496. Similarly, western longitudes are given with a
|
||
<strong>W</strong>, e.g. W07°, or with a negative value, e.g. -7.34323.</p></div>
|
||
<div class="paragraph"><p>Please note that GPS coordinates of a dive site are linked to the Location
|
||
name - so adding coordinates to dives that do not have a location description
|
||
will cause unexpected behaviour (Subsurface will think that all of these
|
||
dives have the same location and try to keep their GPS coordinates the
|
||
same).</p></div>
|
||
<div class="paragraph"><p><strong>Divemaster</strong>: The name of the dive master or dive guide for this dive should be
|
||
entered in this field
|
||
which offers auto completion based on the list of dive masters in
|
||
the current logbook.</p></div>
|
||
<div class="paragraph"><p><strong>Buddy</strong>: In this field, one enters the name(s) of the buddy / buddies
|
||
(separated with commas) who accompanied him/her on the
|
||
dive. Auto completion based on the list of buddies in the current logbook is
|
||
offered.</p></div>
|
||
<div class="paragraph"><p><strong>Suit</strong>: Here the type of diving suit used for the dive can be entered.
|
||
Auto completion of the suit description is available.
|
||
Some dry-suit users may choose to use this field to record what combination of
|
||
suit and thermal protection undersuit was used.</p></div>
|
||
<div class="paragraph"><p><strong>Rating</strong>: One can provide a subjective overall rating of the dive on a
|
||
5-point scale by clicking the appropriate star on the rating scale.</p></div>
|
||
<div class="paragraph"><p><strong>Visibility</strong>: Similarly, one can provide a rating of visibility during the
|
||
dive on a
|
||
5-point scale by clicking the appropriate star.</p></div>
|
||
<div class="paragraph"><p><strong>Tags</strong>: Tags that describe the type of dive performed can be entered
|
||
here (separated by commas). Examples of common tags are boat, drift, training,
|
||
cave, etc.
|
||
<em>Subsurface</em> has many built-in tags. If the user starts typing a tag, the
|
||
program
|
||
will list the tags that correspond to the typing. For instance, if the user
|
||
typed
|
||
<code>cav</code>, then the tags <strong>cave</strong> and <strong>cavern</strong> are shown for the user to choose from.</p></div>
|
||
<div class="paragraph"><p><strong>Notes</strong>: Any additional information for the dive can be entered here.</p></div>
|
||
<div class="paragraph"><p>The <strong>Save</strong> and <strong>Cancel</strong> buttons are used to save all the information for tabs
|
||
in the info panel and in the dive profile panel, so there’s no need to use them
|
||
until ALL other information has been added. Here is an example of a completed
|
||
Dive Notes panel:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CompletedDiveInfo.jpg" alt="FIGURE: A completed Dive Notes tab" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_equipment_2">4.2.5. Equipment</h4>
|
||
<div class="paragraph"><p>The Equipment tab allows one to enter information about the type of
|
||
cylinder and gas used as well as the weights used for the dive. The
|
||
message in a blue box at the top of the panel:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/BlueEditBar.jpg" alt="FIGURE: Blue edit bar" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>indicates that the dive is being edited. This is a highly interactive part of
|
||
<em>Subsurface</em> and the information on
|
||
cylinders and gases (entered here) determines the behaviour of the dive profile
|
||
(top right-hand panel).</p></div>
|
||
<div class="paragraph"><p><strong>Cylinders</strong>: The cylinder information is entered through a dialogue that looks
|
||
like this:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DC_gas_dialogue1.jpg" alt="FIGURE: Initial cylinder dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>In most cases <em>Subsurface</em> obtains the gas used from the dive computer and
|
||
automatically inserts the gas composition(% oxygen) in the table. The + button
|
||
at the top right allows the user to add more cylinders for this dive. The dark
|
||
dustbin icon on the left allows the deletion of information for a cylinder.
|
||
Note that it is not possible to delete a cylinder if it is used during the
|
||
dive. A cylinder might be implicitly used in the dive, even without a gas change event.</p></div>
|
||
<div class="paragraph"><p>The user should start by selecting a cylinder type on the left-hand side of the
|
||
table. To select a cylinder, the <strong>cylinder type</strong> box should be clicked. This
|
||
brings up a list button that can be used to display a dropdown list of
|
||
cylinders:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DC_gas_dialogue2.jpg" alt="FIGURE: The cylinder drop-down list button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The drop-down list can then be used to select the cylinder type that was used
|
||
for this dive or the user may start typing in the box which shows the available
|
||
options for the entered characters. The
|
||
<strong>Size</strong> of the cylinder as well as its working pressure (<strong>WorkPress</strong>) will
|
||
automatically be shown in the dialogue.</p></div>
|
||
<div class="paragraph"><p>Next one must indicate the starting pressure and the ending pressure of the
|
||
specified gas during the dive. The unit of pressure (metric/imperial)
|
||
corresponds to the settings chosen in the <em>Preferences</em>.</p></div>
|
||
<div class="paragraph"><p>Finally, provide the gas mixture used. If air was used, the
|
||
value of 21% can be entered or this field can be left blank. If nitrox or
|
||
trimix were used, their percentages of oxygen and/or helium should be entered.
|
||
Any inappropriate fields should be left empty. After typing the
|
||
information for the cylinder,
|
||
either press <em>ENTER</em> on the keyboard or click outside the cell
|
||
that contains
|
||
the cursor. Information for any additional cylinders can be added by using the<br />
|
||
button at the top right hand. Following is an example of a complete description
|
||
for a dive using two cylinders (air and EAN50):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CylinderDataEntry3.jpg" alt="FIGURE: a completed cylinder dive information table" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Weights</strong>: Information about the weight system used can be entered
|
||
using a dialogue very similar to that of the cylinder information. If one
|
||
clicks
|
||
the + button on the top right of the weights dialogue, the table looks like
|
||
this:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry1.jpg" alt="FIGURE:The Weights dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>By clicking on the <strong>Type</strong> field, a drop-down list becomes accessible through a
|
||
down-arrow:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry2.jpg" alt="FIGURE:Weights type drop-down list button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The drop-down list can then be used to select the type of weight system
|
||
used during the dive or the user may start typing in the box
|
||
which shows the available options for the entered characters.
|
||
In the <strong>Weight</strong>
|
||
field, type in the amount of weight used during the dive. After
|
||
specifying the weight
|
||
system, the user can either press <em>ENTER</em> on the keyboard or click outside the
|
||
cell with the cursor.
|
||
It is possible to enter information for more than one weight system by adding
|
||
an additional system
|
||
using the + button on the top right hand. Weight systems can be deleted using
|
||
the dustbin icon on the left hand. Here is an example of information for a dive
|
||
with two types of weights: integrated as well as a weight belt:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/WeightsDataEntry3.jpg" alt="FIGURE: A completed weights information table" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_editing_several_selected_dives_simultaneously">4.2.6. Editing several selected dives simultaneously</h4>
|
||
<div class="paragraph"><p><em>METHOD 1</em>: After uploading dives from
|
||
a dive computer, the dive profiles of the uploaded dives are shown in the <strong>Dive profile</strong> tab, as well
|
||
as a few items of information
|
||
in the <strong>Dive Notes</strong> tab (e.g. water temperature) and in the <strong>Equipment</strong> tab (e.g. gas pressures
|
||
and gas composition). However the other fields remain empty.
|
||
It may be useful to simultaneously edit some of the
|
||
fields in the <strong>Dive Notes</strong> and <strong>Equipment</strong> tabs. For instance, it is possible
|
||
that a diver performed several dives during a single day, using identical equipment while diving at the same
|
||
dive site or with the same dive master and/or buddy or tags. Instead of completing the information for each
|
||
of these dives separately, one can select all the dives for that day in the <strong>Dive List</strong> and
|
||
insert the same information in the <strong>Dive Notes</strong> and <strong>Equipment</strong> fields that need
|
||
identical information. This is achieved by editing the dive notes or the equipment for any one
|
||
of the selected dives.</p></div>
|
||
<div class="paragraph"><p>The simultaneous editing only works with fields that do not already contain information.
|
||
This means that, if some fields have been edited for a particular dive among the selected dives,
|
||
these are not changed while
|
||
editing the dives simultaneously. Technically, the rule for editing several dives simultaneously is:
|
||
if the data field being edited contains <em>exactly the same information</em> for all the dives that have been
|
||
selected, the new, edited information is substituted for all the selected dives, otherwise only the
|
||
edited dive is
|
||
changed, even though several dives have been selected in the <strong>Dive List</strong>. This greatly speeds
|
||
up the completion of the dive log after several similar dives.</p></div>
|
||
<div class="paragraph" id="S_CopyComponents"><p><em>METHOD 2</em>:There is a different way of achieving the same goal. Select a dive with all the appropriate information
|
||
typed into the <strong>Dive Notes</strong> and <strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log → Copy dive components</em>.
|
||
A box is presented with a selection of check boxes for most of the fields in the <strong>Dive Notes</strong> and <strong>Equipment</strong> tabs.
|
||
Select the fields to be copied from the currently selected dive, then select <em>OK</em>. Now, in the <strong>Dive List</strong>,
|
||
select the dives
|
||
into which this information is to be pasted. Then, from the main menu, select <em>Log → Paste dive components</em>. All the selected dives now contain the data initially selected in the original source dive log.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_adding_bookmarks_to_a_dive">4.2.7. Adding Bookmarks to a dive</h4>
|
||
<div class="paragraph"><p>Many divers wish to annotate their dives with text that indicate particular events
|
||
during the dive, e.g. "Saw dolphins", or "Released surface bouy". This is easily
|
||
done:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Right-click at the appropriate point on the dive profile.
|
||
This brings up the dive profile context menu. Select <em>Add bookmark</em>. A red flag is
|
||
placed on the dive profile at the point that was initially selected (see <strong>A</strong> below).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Right-click on the red flag. This brings up the context menu (see <strong>B</strong> below). Select <em>Edit name</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
A text box is shown. Type the explanatory text for the bookmark (see <strong>C</strong> below). Select <em>OK</em>.
|
||
This saves the text associated with the bookmark.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If one hovers using the mouse over the red bookmark, the appropriate text is shown at
|
||
the bottom of the information box (see <strong>D</strong> below).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Bookmarks.jpg" alt="FIGURE: Bookmark dialog" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_saving_the_updated_dive_information">4.2.8. Saving the updated dive information</h4>
|
||
<div class="paragraph"><p>The information entered in the <strong>Dive Notes</strong> tab and the <strong>Equipment</strong> tab can be
|
||
saved by
|
||
using the
|
||
two buttons on the top right hand of the <strong>Dive Notes</strong> tab. If the <em>Save</em> button
|
||
is clicked,
|
||
the dive data are saved. If the <em>Cancel</em> button is clicked, then the newly
|
||
entered dive data are
|
||
deleted, although the dive profile obtained from the dive computer will be
|
||
retained. When the user exits <em>Subsurface</em> there is a final prompt to confirm
|
||
that the new data should be saved.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importing_dive_information_from_other_digital_data_sources_or_other_data_formats">4.3. Importing dive information from other digital data sources or other data formats</h3>
|
||
<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>If a user has been diving for some time, it is possible that several dives were
|
||
logged using other dive log software. This information does not need retyping
|
||
because these dive logs can probably be
|
||
imported into <em>Subsurface</em>. <em>Subsurface</em> will import dive logs from a range of
|
||
other
|
||
dive log software. While some software is supported natively, for others the
|
||
user has to
|
||
export the logbook(s) to an intermediate format so that they can then be imported
|
||
by <em>Subsurface</em>.
|
||
Currently, <em>Subsurface</em> supports importing CSV log files from several sources.
|
||
APD LogViewer, XP5, Sensus and Seabear files are
|
||
preconfigured, but because the import is flexible, users can configure their own
|
||
imports.
|
||
Manually kept log files (e.g. in spreadsheet) can also be imported by
|
||
configuring the CSV import.
|
||
<em>Subsurface</em> can also import UDDF and UDCF files used by some divelog
|
||
software and some dive computers, like the Heinrichs & Weikamp DR5. Finally,
|
||
for some divelog software like Mares Dive Organiser it is currently suggested to
|
||
import the logbooks first into a webservice like <em>divelogs.de</em> and then import
|
||
them from there with
|
||
<em>Subsurface</em>, as divelogs.de supports a few additional logbook formats that
|
||
<em>Subsurface</em> currently cannot parse.</p></div>
|
||
<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, it should be sufficient to select
|
||
either <em>Import→Import log files</em> or <em>File→Open log file</em>. <em>Subsurface</em> supports the data formats
|
||
of many dive computers, including Suunto and Shearwater. When importing dives, <em>Subsurface</em>
|
||
tries to detect multiple records for
|
||
the same dive and merges the information as best as it can. If
|
||
there are no time zone issues (or other reasons that would cause the
|
||
beginning time of the dives to be significantly different) <em>Subsurface</em>
|
||
will not create duplicate entries.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_using_the_universal_import_dialogue">4.3.1. Using the universal import dialogue</h4>
|
||
<div class="paragraph" id="Unified_import"><p>Importing dives from other software is performed through a universal interface
|
||
that is activated by selecting <em>Import</em> from the Main Menu, then clicking on
|
||
<em>Import Log Files</em>. This brings up the dialogue <strong>A</strong> below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Import1.jpg" alt="FIGURE: Import dialogue: step 1" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Towards the bottom right is a dropdown selector with a default label
|
||
of <em>Dive Log Files</em> which gives access to the different types of direct imports
|
||
available, as in dialogue <strong>B</strong>, above. Currently these are:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
XML-formatted dive logs (Divinglog 5.0, MacDive and several other dive log systems)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
UDDF-formatted dive logs (e.g. Kenozoooid)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
UDCF-formatted dive logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Poseidon CCR logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
JDiveLog
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Suunto Dive Manager (DM3 and DM4)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Selecting the appropriate file in the file list of the dialogue opens
|
||
the imported dive log in the <em>Subsurface</em> <strong>Dive List</strong>. Some other formats, not
|
||
accessible through the Import dialogue are also supported, as explained below.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_importing_dive_logs_from_closed_circuit_rebreather_ccr_systems">4.3.2. Importing dive logs from closed circuit rebreather (CCR) systems</h4>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/APD.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Closed system rebreathers use avanced technology to recirculate
|
||
gas that has been breathed while doing two things to maintain a
|
||
breathable oxygen concentration:
|
||
a) remove carbon dioxide from the gas that has been exhaled
|
||
b) regulate the oxygen concentration to remain within safe diving limits.
|
||
Currently, within <em>Subsurface</em>, the Poseidon MkVI Discovery is the best
|
||
supported CCR dive computer. The CCR interface of <em>Subsurface</em> is currently experimental
|
||
and under active development. In contrast to a conventional open circuit
|
||
dive computer, a CCR system computer does not allow the download of a log
|
||
containg multiple dives. Rather, each dive is stored independently. This
|
||
means that <em>Subsurface</em> cannot download a dive log directly from a CCR
|
||
dive computer, but that it imports CCR dive logs in the same way that it
|
||
imports dive log data from other databases.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_import_a_ccr_dive">Import a CCR dive</h5>
|
||
<div class="paragraph"><p>See the section dealing with <a href="#S_ImportingAlienDiveLogs">Importing dive information from other
|
||
digital sources</a>. From the main menu of <em>Subsurface</em>, select <em>Import→Import
|
||
log files</em> to bring up the <a href="#Unified_import">universal import dialogue</a>. As
|
||
explained in the previous section, the bottom right
|
||
hand of the import dialogue contains a dropdown list of appropriate devices
|
||
that currently includes an option for MkVI files. Having selected the appropriate CCR format and
|
||
the directory where the original dive logs have been stored from the CCR dive
|
||
computer, one can select a particular dive log file (in the case of the MkVI
|
||
it is a file with a .txt extension). After selecting the appropriate dive log,
|
||
activate the <em>Open</em> button at the bottom right hand of the universal import dialogue.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_displayed_information_for_a_dive">Displayed information for a dive</h5>
|
||
<div class="paragraph"><p><em>Partial pressures of gases</em>: The graph of oxygen partial pressure shows the
|
||
information from the oxygen sensors of the CCR equipment. In the case of the
|
||
Poseidon MKVI, the mean value of the two oxygen sensors are shown. In the case
|
||
of the APD equipment, the mean of the three oxygen sensors are shown. If one
|
||
sensor shows a very different oxygen PO2 reading compared to the others, the
|
||
divergent sensor is ingnored. For CCR dives the graph for oxygen partial pressure
|
||
should be fairly flat, reflecting the setpoint settings during the dive.
|
||
Partial pressures for nitrogen (and helium,
|
||
if applicable) are shown in the usual way as for other dives.</p></div>
|
||
<div class="paragraph"><p><em>Cylinder pressures</em>: CCR dive computers like the Poseidon MkVI record the
|
||
pressures of the oxygen and diluent cylinders. The pressure of the oxygen cylinder
|
||
is shown on the dive profile. In addition, start and end pressures for both oxygen
|
||
and diluent cylinders are shown in the <em>Equipment Tab</em>.</p></div>
|
||
<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by
|
||
<em>Subsurface</em> is shown in the <em>Extra data</em> tab. This may include setup information
|
||
or metadata about the dive.</p></div>
|
||
<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs can be found in <a href="#S_PoseidonMkVI">Appendix B</a>.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_importing_from_mares_dive_organiser_v2_1">4.3.3. Importing from Mares Dive Organiser V2.1</h4>
|
||
<div class="paragraph"><p>Since Mares utilise proprietary Windows software not compatible with
|
||
multi-platform applications, these dive logs cannot be
|
||
directly imported into
|
||
<em>Subsurface</em>. Mares dive logs need to be imported using a three-step process,
|
||
using <em>www.divelogs.de</em> as a mechanism to extract the dive log information.</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
The dive log data from Mares Dive Organiser need to be exported to the user’s
|
||
desktop, using
|
||
a <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a> for more
|
||
information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Data should then be imported into <em>www.divelogs.de</em>. One needs to create a user
|
||
account in
|
||
<em>www.divelogs.de</em>, log into that web site, then
|
||
select <em>Import Logbook → Dive Organiser</em> from the menu on the left hand side.
|
||
The instructions must be carefully followed to transfer the dive information
|
||
(in <em>.sdf</em> format) from the Dive Organiser database to <em>www.divelogs.de</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Finally, import the dives
|
||
from <em>divelogs.de</em> to <em>Subsurface</em>, using the instructions below.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_ImportingDivelogsDe">4.3.4. Importing dives from <strong>divelogs.de</strong></h4>
|
||
<div class="paragraph"><p>The import of dive information from <em>divelogs.de</em> is simple, using a single
|
||
dialogue box. The <em>Import→Import form Divelogs.de</em> option should be selected
|
||
from the Main Menu. This
|
||
brings up a dialogue box (see figure on left [<strong>A</strong>] below). Enter a
|
||
user-ID and password for <em>divelogs.de</em> into the appropriate fields and then
|
||
select
|
||
the <em>Download</em> button. Download from <em>divelogs.de</em> starts immediately,
|
||
displaying a progress bar in the dialogue box. At the end of the download, the
|
||
success status is indicated (see figure on the right [<strong>B</strong>], below). The
|
||
<em>Apply</em> button should then be selected, after which the imported dives appear in the
|
||
<em>Subsurface</em> <strong>Dive List</strong> panel.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Divelogs1.jpg" alt="FIGURE:Download from Divelogs.de" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_ImportingCSV">4.3.5. Importing dives in CSV format</h4>
|
||
<div class="paragraph"><p>Sometimes dive computers export dive information as files with
|
||
<em>comma-separated values</em> (.CSV). For example, the APD Inspiration and Evolution
|
||
closed circuit rebreather (CCR) systems export dive information in a CSV
|
||
formatted file that normally contains information for a single dive only. These
|
||
files can easily be imported into <em>Subsurface</em>.
|
||
CSV files are normally organised into
|
||
a single line that provides the headers of the data columns, followed by the
|
||
data, one record per line. CSV files can be opened with a normal text editor.
|
||
Following is a highly simplified and shortened example of a CSV file from an
|
||
APD rebreather:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code> Dive Time (s) Depth (m) pO₂ - Setpoint (Bar) pO₂ - C1 Cell
|
||
1 (Bar) Ambient temp. (Celsius)
|
||
0 0.0 0.70 0.81 13.1
|
||
0 1.2 0.70 0.71 13.1
|
||
0 0.0 0.70 0.71 13.1
|
||
0 1.2 0.70 0.71 13.2
|
||
0 1.2 0.70 0.71 13.1
|
||
10 1.6 0.70 0.72 12.7
|
||
20 1.6 0.70 0.71 12.6
|
||
30 1.7 0.70 0.71 12.6
|
||
40 1.8 0.70 0.68 12.5
|
||
50 1.6 0.70 0.68 12.5
|
||
60 2.4 0.70 0.69 12.5
|
||
70 3.5 0.70 0.69 12.4
|
||
80 4.2 0.70 0.72 12.5
|
||
90 4.0 0.70 0.71 12.4</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Note that each title may comprise more than one word; for instance
|
||
<em>Dive Time (s)</em> in the above data example. Before being able to import the data
|
||
to <em>Subsurface</em> one first needs to know:</p></div>
|
||
<div class="olist loweralpha"><ol class="loweralpha">
|
||
<li>
|
||
<p>
|
||
Which character separates the different columns within a single line of
|
||
data? This field separator should be either a comma (,) or a TAB character.
|
||
This can be determined by opening the file with a text editor. If it is
|
||
comma-delimited, then the comma
|
||
characters between the values are clearly visible. If no commas are evident and
|
||
the numbers are aligned in columns,
|
||
the file is probably TAB-delimited (i.e. it uses a TAB as a field separator, as
|
||
in the above example).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Which data columns need to be imported into <em>Subsurface</em>? The Dive Time and
|
||
Depth columns are always required. Open the file using a text editor and note
|
||
the titles of the columns to be imported and their column positions. For
|
||
instance for the above example:
|
||
</p>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Time: column 1
|
||
Depth: column 2
|
||
Temperature: column 5
|
||
pO₂: column 4</code></pre>
|
||
</div></div>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Armed with this information, importing the data into <em>Subsurface</em> is
|
||
straightforward. Select
|
||
<em>Import→Import Log Files</em> from the main menu. In the resulting file
|
||
selection menu, select <em>CSV files</em>, after which a common configuration dialog
|
||
appears for all the
|
||
files with a CSV extension:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Import_CSV1.jpg" alt="FIGURE: CSV download dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>There are pre-configured definitions for some dive computers, e.g. the APD
|
||
rebreathers. If the user’s dive computer is on this list, it should be selected
|
||
using the dropdown
|
||
box labeled <em>Pre-configured imports</em>. Select the button at the bottom right
|
||
to indicate whether the dive data are in metric of imperial units.
|
||
Finally <em>OK</em> should be clicked and
|
||
the dive will be imported and listed in the <strong>Dive List</strong> tab of <em>Subsurface</em>.</p></div>
|
||
<div class="paragraph"><p>If the dive computer is not on the pre-configured list, the user must
|
||
select the <em>Field
|
||
Separator</em> (TAB or comma) for the particular CSV file, using the appropriate
|
||
dropdown list. and indicate which columns in the CSV file
|
||
contain which data
|
||
variables. For each data column used for import, the user must check the
|
||
appropriate check box
|
||
and indicate in which column these data are found. For instance, the image above
|
||
corresponds to the dialogue that would apply to the CSV data set described above
|
||
the image. After completing the column specification, select the <em>OK</em> button
|
||
and the dive will be imported and listed in the <strong>Dive List</strong> tab of <em>Subsurface</em>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_ImportingManualCSV">4.3.6. Importing dives from manually kept CSV file</h4>
|
||
<div class="paragraph"><p>If one keeps dive logs in a spreadsheet, there is an option to import
|
||
those dives as well. Spreadsheet data, exported as a CSV file, can
|
||
be imported to <em>Subsurface</em>. When importing manually
|
||
kept log files, the information needed is quite different as we are
|
||
importing only metadata, not profile samples.</p></div>
|
||
<div class="paragraph"><p>Similarly to importing dives in CSV format (see above), one needs to
|
||
know the internal format
|
||
of the CSV data to import.</p></div>
|
||
<div class="olist loweralpha"><ol class="loweralpha">
|
||
<li>
|
||
<p>
|
||
Which character separates the different columns within a single line of
|
||
data? This
|
||
should be either a comma (,), semicolon (;) or a TAB
|
||
character, and could be determined by opening the file with a text
|
||
editor. If it is comma-delimited, then the comma
|
||
characters between the values are clearly visible. If no commas are evident and
|
||
the data
|
||
are in clear columns, the file
|
||
is probably TAB-delimited (i.e. it uses a TAB as a field separator, as in the
|
||
above example).
|
||
A recommended field separator for the export is tab, as commas might be part of
|
||
the
|
||
field values themselves. Therefore the use of an appropriate field separator
|
||
in very important.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Which columns need to be imported into <em>Subsurface</em>? We do not
|
||
currently have any mandatory input fields, but some, e.g. dive duration
|
||
are crucial for the log file to make any sense. Possible options
|
||
can be seen in the image below and one should include all the
|
||
fields available in both your log file and in the <em>Subsurface</em>
|
||
import.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Units used for depth, weight and temperature. We consider depth to be
|
||
either feet or meters, weight kilograms or pounds and temperature either
|
||
Celsius or Fahrenheit. However, the users can select <em>Metric</em> or
|
||
<em>Imperial</em> in the <em>Preferences</em> tab of <em>Subsurface</em>. No mixture of unit
|
||
systems is allowed for the different fields.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Importing manually kept CSV log files is quite straight forward, but
|
||
there might be many fields and counting the field numbers is error
|
||
prone. Therefore validation of the data to be imported is critical.</p></div>
|
||
<div class="paragraph"><p>To import the dives, select <em>Import→Import Log Files</em> from the menu
|
||
bar. If the CSV option in the dropdown list is selected and the file list
|
||
includes file names ending with .CSV, one can select the
|
||
<em>Manual dives</em> tab that will bring up the following configuration dialog:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Import_CSV2.jpg" alt="FIGURE: Download dialog for Manual CSV logs" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The input fields can be configured as appropriate, and when everything is done
|
||
the <em>OK</em> button should be selected to perform the import. New dives should
|
||
appear in the <strong>Dive List</strong> area of <em>Subsurface</em>.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Companion">4.4. Importing GPS coordinates with the <em>Subsurface Companion App</em> for mobile phones</h3>
|
||
<div class="paragraph"><p>Using the <strong>Subsurface Companion App</strong> on an Android device with a GPS, the coordinates
|
||
for the diving
|
||
location can be automatically passed to the <em>Subsurface</em>
|
||
dive log. The Companion App stores the dive locations on
|
||
a dedicated Internet-based file server. <em>Subsurface</em>, in turn, can collect
|
||
the localities from the file server.</p></div>
|
||
<div class="paragraph"><p>To do this:</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_create_a_companion_app_account">4.4.1. Create a Companion App account</h4>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Register on the <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a>.
|
||
A confirmation email with instructions and a personal <strong>DIVERID</strong> will be sent,
|
||
a long number that gives access to the file server and Companion App capabilities.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Download the app from
|
||
<a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play Store</a>
|
||
or from
|
||
<a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_using_the_subsurface_companion_app_on_a_smartphone">4.4.2. Using the Subsurface companion app on a smartphone</h4>
|
||
<div class="paragraph"><p>On first use the app has three options:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Create a new account.</em> Equivalent to registering in <em>Subsurface</em> companion
|
||
page using an Internet browser. One can request a <strong>DIVERID</strong> using this option,
|
||
but this is supplied via email and followed up by interaction with the
|
||
<a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> in order to
|
||
activate the account.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Retrieve an account.</em> If users forgot their <strong>DIVERID</strong> they will receive an email
|
||
to recover the number.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Use an existing account.</em> Users are prompted for their <strong>DIVERID</strong>. The app saves
|
||
this <strong>DIVERID</strong> and does not ask for it again unless one uses the <em>Disconnect</em> menu
|
||
option (see below).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">In the <em>Subsurface</em> main program, the <strong>DIVERID</strong> should also be entered on the
|
||
Default Preferences
|
||
panel, obtained by selecting <em>File→Preferences→Defaults</em> from the main menu
|
||
in <em>Subsurface</em> itself.
|
||
This facilitates synchronisation between <em>Subsurface</em> and the Companion App.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_creating_new_dive_locations">Creating new dive locations</h5>
|
||
<div class="paragraph"><p>Now one is ready to get a dive position and
|
||
send it to the server. The Android
|
||
display will look like the left hand image (<strong>A</strong>) below, but without any dives.</p></div>
|
||
<div class="paragraph"><p>Touch the "+" icon on the top right to add a new dive site, a menu will be
|
||
showed with 3 options:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Current: A prompt for a place name (or a request to activate the GPS if it is turned
|
||
off) will be displayed, after which the current location is saved.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Use Map: This option allows the user to fix a position by searching a world map. A
|
||
world map is shown (see <strong>B</strong> below) on which one should indicate the desired position
|
||
with a <em>long press</em> on the touch
|
||
sensitive screen (if the marked location is erroneous, simply indicate a new location)
|
||
and select the check symbol in the upper right. A dialog is shown allowing to enter the
|
||
name of the dive location and the date-time of the dive (see <strong>C</strong> below). In order to import this
|
||
dive location in <em>Subsurface</em> it’s advisable to set the time to agree with the time of
|
||
that dive on the dive computer.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Companion_5.jpg" alt="FIGURE: Companion App, add location using map" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Import local GPX file: The android device searches for .gpx files and located
|
||
archives will be shown. The selected .gpx file is opened and the stored
|
||
locations shown. Now one needs to select the appropriate locations, then select the
|
||
tab in the upper right, after which the locations will be sent to the web service
|
||
and added to the list on the Android device.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_dive_lists_of_dive_locations">Dive lists of dive locations</h5>
|
||
<div class="paragraph"><p>The main screen shows a list of dive locations, each with a name, date and
|
||
time (see <strong>A</strong> below). Some locations may have an arrow-up icon over the selection box to the left
|
||
indicating that they require upload to the server. One
|
||
can select individual dive locations from the list. A selected location has a
|
||
check mark in the selection box on the left. Group operations (such as <em>Delete</em> or <em>Send</em>)
|
||
are performed on several locations that are selected.</p></div>
|
||
<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations or a
|
||
map indicating the dive locations. The display mode (List or Map) is changed by
|
||
selecting <em>Dives</em> at the top left of the screen (see <strong>A</strong> below) and then selecting
|
||
the display mode. The display mode can be changed either from the list
|
||
of locations or from the map (see <strong>B</strong> below). If one selects a location (on the list
|
||
or on the map), an editing
|
||
panel opens (see <strong>C</strong> below) where the dive description or other details may be changed.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Companion_4.jpg" alt="FIGURE: Companion App, add location using map" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>When one clicks on a dive (<strong>not</strong> selecting the check box), the
|
||
name given to it, date/time and GPS coordinates will be shown, with two options at the top
|
||
of the screen:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Edit (pencil): Change the text name or other characteristics of the dive location.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Maps: Display a map showing the dive location.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>After editing and saving a dive location (see <strong>C</strong> above), one needs to upload it to the web
|
||
service, as explained below.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_uploading_dive_locations">Uploading dive locations</h5>
|
||
<div class="paragraph"><p>There are several ways to send locations to the server.
|
||
The easiest is by simply
|
||
selecting the locations (See <strong>A</strong> below) and then touching the right arrow at the
|
||
top right of the screen.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Users must be careful, as the trash icon on the right means exactly what it should;
|
||
it deletes the selected dive location(s).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Companion_1.jpg" alt="FIGURE: Screen shots (A-B) of companion app" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>After a dive trip using the Companion App, all dive locations are ready to be
|
||
downloaded to a <em>Subsurface</em> dive log (see below).</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_settings_on_the_companion_app">Settings on the Companion app</h5>
|
||
<div class="paragraph"><p>Selecting the <em>Settings</em> menu option results in the right hand image above (<strong>B</strong>).</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_server_and_account">Server and account</h5>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Web-service URL.</em> This is predefined (<a href="http://api.hohndel.org/">http://api.hohndel.org/</a>)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>User ID.</em> The DIVERID obtained by registering as described above. The easiest way to
|
||
obtain it is simply to copy and paste from the confirmation email but, of
|
||
course, users can also type this information.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_synchronisation">Synchronisation</h5>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Synchronize on startup.</em> If selected, dive locations in the Android device and those
|
||
on the web service synchronise each time the app is started.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Upload new dives.</em> If selected, each time the user adds a dive location it is
|
||
automatically sent to the server.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_background_service">Background service</h5>
|
||
<div class="paragraph"><p>Instead of entering a unique dive location, users can leave the service running
|
||
in the background of their Android device, allowing the continuous collection of GPS locations.</p></div>
|
||
<div class="paragraph"><p>The settings below define the behaviour of the service:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Min duration.</em> In minutes. The app will try to get a location every X minutes
|
||
until stopped by the user.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Min distance.</em> In meters. Minimum distance between two locations.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Name template.</em> The name the app will use when saving the locations.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/info.jpg" alt="Tip" />
|
||
</td>
|
||
<td class="content"><em>How does the background service work?</em> Assuming the user sets 5 minutes and 50
|
||
meters in the settings above, the app will start by recording a location at the current
|
||
location, followed by another one at every 5 minutes <strong>or</strong> every time one moves 50m
|
||
from previous location.
|
||
If subsequent locations are within a radius of 50 meters from the previous one,
|
||
a new location is not saved. If the user is not moving, only one location is saved,
|
||
but if the user is moving, a trace of the route is obtained by saving a
|
||
location every 50 meters.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_other">Other</h5>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Mailing List.</em> The mail box for <em>Subsurface</em>. Users can send an email to the
|
||
Subsurface mailing list.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface website.</em> A link to the URL of Subsurface web
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Version.</em> Displays the current version of the Companion App.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_search">Search</h5>
|
||
<div class="paragraph"><p>Search the saved dive locations by name or by date and time.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_start_service">Start service</h5>
|
||
<div class="paragraph"><p>Initiates the <em>background service</em> following the previously defined settings.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_disconnect">Disconnect</h5>
|
||
<div class="paragraph"><p>This is a badly named option that disconnects the app from the server by
|
||
resetting the user ID in the app, showing the first screen where an account
|
||
can be created, retrieve the ID for an existing account or use the users own
|
||
ID. The disconnect option
|
||
is useful if a user’s Android device was used to download the dive locations
|
||
of another registered diver.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_send_all_locations">Send all locations</h5>
|
||
<div class="paragraph"><p>This option sends all locations stored in the Android device to the server.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">4.4.3. Downloading dive locations to the <em>Subsurface</em> divelog</h4>
|
||
<div class="paragraph"><p>Download dive(s) from a dive computer or enter them manually into
|
||
<em>Subsurface</em> before obtaining the GPS coordinates from the server. The download
|
||
dialog can be reached via <em>Ctrl+G</em> or from the <em>Subsurface</em> Main Menu <em>Import
|
||
→ Import GPS data from Subsurface Service</em>, resulting in the image on the
|
||
left (<strong>A</strong>), below. On first use the DIVERID text box is blank. Provide a
|
||
DIVERID, then select the <em>Download</em> button to initiate the download process, after
|
||
which the screen on the right (<strong>B</strong>) below appears:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DownloadGPS.jpg" alt="FIGURE: Downloading Companion app GPS data" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Note that the <em>Apply</em> button is now active. By clicking on it, users can update the locations
|
||
of the newly entered or uploaded dives in <em>Subsurface</em> which applies the
|
||
coordinates and names entered on the app for all the new dives that match the
|
||
date-times of the uploaded GPS localities. If one has entered the name of the dive
|
||
location in <em>Subsurface</em> before downloading the GPS coordinates, this name will take
|
||
precedence over downloaded one.</p></div>
|
||
<div class="paragraph"><p>Since <em>Subsurface</em> matches GPS locations from the Android device and dive information from the
|
||
dive computer based on date-time data, automatic assignment of GPS data to dives is dependent
|
||
on agreement of the date-time information between these two devices. Although <em>Subsurface</em> has
|
||
a wide range tolerance, it may be unable to identify the appropriate dive if there is
|
||
a large difference between the time in the dive computer and that of the Android device,
|
||
resulting in no updates.</p></div>
|
||
<div class="paragraph"><p>Similar date-times may not always be possible and there may be many reasons for this (e.g. time zones), or
|
||
<em>Subsurface</em> may be unable to decide which is the correct position for a dive (e.g. on repetitive
|
||
dives while running <em>background service</em> there may be several locations that would be
|
||
included in the time range that fit not only the first dive, but one or more subsequent dives as well).
|
||
A workaround for this situation to manually edit the date-time of a dive in the <em>Subsurface</em>
|
||
Dive List <strong>before</strong> downloading the GPS data and then to change the date-time back again <strong>after</strong>
|
||
downloading GPS data.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/info.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">TIPS:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Background service</em>, being a very powerful tool, may fill the location list with
|
||
many unnecessary locations not corresponding to the exact dive point but reflecting the boat’s route.
|
||
Currently these locations are difficult to delete from the server. In some situations it
|
||
is therefore prudent to clean up the list on the Android device before sending the dive points to the web
|
||
server by simply deleting the inappropriate locations. This might be necessary, for
|
||
instance, if one wants to keep the location list clear to see dives in the web service map display (see above).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
It may also make sense to give informative names to the locations sent to the web server, or at least
|
||
to use an informative name in the <em>Name Template</em> setting while running the <em>background service</em>,
|
||
especially on a dive trip with many dives and dive locations.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_LoadImage">4.5. Adding photographs to dives</h3>
|
||
<div class="paragraph"><p>Many (if not most) divers take a camera with them and take photographs
|
||
during a dive. One would like to associate each photograph with a specific
|
||
dive. <em>Subsurface</em> allows one to load photos into a dive. Photos are superimposed
|
||
on the dive profile, from where they can be viewed.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_loading_photos_and_getting_synchronisation_between_dive_computer_and_camera">4.5.1. Loading photos and getting synchronisation between dive computer and camera</h4>
|
||
<div class="paragraph"><p>Left-lick on a dive or on a group of dives on the dive list. Then right-click on this
|
||
dive or group of dives and choose the option <em>Load Images</em>:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage1.jpg" alt="FIGURE: Load images option" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The system file browser appears. Select the folder and photographs that need
|
||
to be loaded into <em>Subsurface</em> and click the <em>Open</em> button.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage2.jpg" alt="FIGURE: Load images option" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This brings one to the time synchronisation dialog, shown below. The
|
||
critical problem is that the time
|
||
synchronisation is not perfect between the dive computer used during a dive,
|
||
and the camera used during that same dive. These two devices
|
||
often differ by several minutes. If <em>Subsurface</em> can achieve synchronisation,
|
||
then the exact times of photographs can be used to position photographs on
|
||
the dive profile.</p></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> achieves this synchronisation in two ways:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Manually</strong>: If the user wrote down the exact camera time at the start of a dive, the
|
||
difference in time between the two devices can be determined. Actually, as long as the device
|
||
settings for time has not been changed in either device, one could write down the times of
|
||
both devices after the dive or even at the end of the day. One can then manually set the time
|
||
difference in the <em>Time shift</em> dialog. Towards the top of the dialog is a time setting tool
|
||
immediately under the heading <em>Shift times of image(s) by</em>, evident in figure <strong>A</strong> below.
|
||
If the camera time is 7 minutes later than that of the dive computer, set the time setting
|
||
tool to a value of 00:07. Select either the <em>earlier</em> or <em>later</em> radio button.
|
||
In the above example, the <em>earlier</em> option is appropriate, since the photos need to be shifted
|
||
7 minutes earlier (camera is 7 minutes ahead of dive computer). Ignore any "AM" or "PM" suffix
|
||
in that tool. Click the <em>OK</em> button and synchronisation is achieved.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage3b.jpg" alt="FIGURE: Synchronisation dialog" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>By photograph</strong>: There is a very slick way of achieving synchronisation. If one takes a
|
||
photograph of the face of the dive computer showing the time, then <em>Subsurface</em> can obtain
|
||
the exact time the photograph was taken, using the metadata that the camera stores within
|
||
each photo. In order to do this, use the bottom half of the Time shift_ dialog. If one uses
|
||
the bottom part, the top part of the dialog is ignored. Click on
|
||
the horizontal bar entitled "<em>Select image of divecomputer showing time</em>. This brings up
|
||
a file browser with which one can select the photograph of the dive computer. Select the
|
||
photograph using the file browser and click on <em>OK</em>. This photograph of the dive computer
|
||
appears in the bottom panel of the <em>Shift times</em> dialog. Now <em>Subsurface</em> knows exactly
|
||
when the photograph has been taken. Now set the date-time dialog to the left of the photo
|
||
so that this tool reflects the date and time of the dive computer in the photo. When the
|
||
date-time tool has been set, <em>Subsurface</em> knows exactly what the time difference between
|
||
camera and dive computer is, and synchronisation is achieved. There is a
|
||
photograph with the face of the dive computer and with the date-time tool set to the
|
||
date-time on image <strong>B</strong> above.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If the timestamp of a photograph is long before or after the dive, it is not placed on
|
||
the dive profile. If the timestamp of the photo is within 30 minutes of the dive, it is shown.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_viewing_the_photos">4.5.2. Viewing the photos</h4>
|
||
<div class="paragraph"><p>In order to view the photos added to a dive, activate the <em>show-photos</em> button in the tool bar
|
||
to the left of the dive profile:</p></div>
|
||
<div class="imageblock" style="text-align:left;">
|
||
<div class="content">
|
||
<img src="images/icons/ShowPhotos.png" alt="FIGURE:Show photos toolbar button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>After the images have been loaded, they appear in two places:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
the <em>Photos</em> tab of the <strong>Dive Notes</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
as tiny icons (stubs) on the dive profile at the appropriate positions reflecting the time
|
||
each photograph was taken. See below:
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage4.jpg" alt="FIGURE: Photos on dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>If one hovers with the mouse over any of the photo icons, then a thumbnail photo
|
||
is shown of the appropriate photo. See the image below:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage5.jpg" alt="FIGURE:Thumbnail photo on dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Clicking on the thumbnail brings up a full size
|
||
photo overlaid on the <em>Subsurface</em> window. This allows good viewing of
|
||
the photographs that have been added (see the image below). Note that the thumbnail
|
||
has a small dustbin icon in the bottom right hand corner (see image above). If one selects
|
||
the dustbin, the image is removed from the dive. Therefore some care
|
||
is required when clicking on a thumbnail. Images
|
||
can also be deleted using the <em>Photos</em> tab (see text below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage6.jpg" alt="FIGURE: Full-screen photo on dive profile" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_the_em_photos_em_tab">4.5.3. The <em>Photos</em> tab</h4>
|
||
<div class="paragraph"><p>Photographs associated with a dive are shown as thumbnails in the <em>Photos</em> tab of the <em>Dive Notes</em>
|
||
panel. Photos taken in rapid succession during a dive (therefore sometimes with large
|
||
overlap on the dive profile) can easily be accessed in the <em>Photos</em> tab. This tab serves as
|
||
a tool for individually accessing the photos of a dive, while the stubs on the dive profile
|
||
give an indication of when during a dive a photo was taken. By single-clicking on a thumbnail in
|
||
the <em>Photos</em> panel, a photo is selected. By double-clicking a thumbnail, the full-sized image is
|
||
shown, overlaying the <em>Subsurface</em> window. A photo can be deleted from the <em>Photos</em> panel by selecting
|
||
it (single-click) and then by pressing the <em>Del</em> key on the keyboard. This removes the photo both
|
||
from the <em>Photos</em> tab as well as the dive profile.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_photos_on_an_external_hard_disk">4.5.4. Photos on an external hard disk</h4>
|
||
<div class="paragraph"><p>Most underwater photographers store their photos on an external drive. If such a drive can be mapped
|
||
(almost always the case) the photos can be directly accessed by <em>Subsurface</em>. This facilitates the interaction
|
||
between <em>Subsurface</em> and an external repository of photos. When associating a dive profile with photos from an
|
||
external drive, the normal procedure of selection and synchronisation (see text above) is used.
|
||
However, after the external drive has been disconnected, <em>Subsurface</em> cannot access these photos any more.
|
||
If the display of photos is activated (using the toolbox to the left of the <em>Dive Profile</em>), the
|
||
program only shows a small white dot where each photo should be on the dive profile.
|
||
In addition the <em>Photos</em> tab only shows the file names of the photos. This is normal behaviour.
|
||
If, later, the external drive with the photos is connected again, the photos can be seen in the normal way.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">5. Obtaining more information about dives entered into the logbook</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_the_strong_dive_info_strong_tab_for_individual_dives">5.1. The <strong>Dive Info</strong> tab (for individual dives)</h3>
|
||
<div class="paragraph"><p>The Dive Info tab gives some summary information about a particular dive that
|
||
has been selected in the <strong>Dive List</strong>. Useful information here includes the
|
||
surface interval before the dive, the maximum and mean depths of the dive, the
|
||
gas volume consumed, the surface air consumption (SAC) and the number of oxygen
|
||
toxicity units (OTU) incurred.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/info.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Gas consumption and SAC calculations:
|
||
<em>Subsurface</em> calculates SAC and Gas consumption taking in account gas
|
||
incompressibility, particularly at tank pressures above 200 bar, making them more accurate.
|
||
Users should refer to <a href="#SAC_CALCULATION">Appendix D</a> for more information.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_the_strong_stats_strong_tab_for_groups_of_dives">5.2. The <strong>Stats</strong> tab (for groups of dives)</h3>
|
||
<div class="paragraph"><p>The Stats tab gives summary statistics for more than one dive, assuming that
|
||
more than one dive has been selected in the <strong>Dive List</strong> using the standard
|
||
Ctrl-click or Shift-click of the mouse. If only one
|
||
dive has been selected, figures pertaining to only that dive are given. This tab
|
||
shows the number of dives selected, the total amount of dive time in these
|
||
dives,
|
||
as well as the minimum, maximum and mean for the dive duration,
|
||
water temperature and surface air consumption (SAC). It also shows the depth of the
|
||
shallowest and deepest dives of those selected.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_DiveProfile">5.3. The <strong>Dive Profile</strong></h3>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Profile2.jpg" alt="Typical dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Of all the panels in <em>Subsurface</em>, the Dive Profile contains the most detailed
|
||
information about each dive. The Dive Profile has a <strong>button bar</strong> on the left hand side
|
||
that allows control over several display options. The functions of these
|
||
buttons are described below. The main item in the Dive
|
||
Profile is the graph of
|
||
dive depth as a function of time. In addition to the obvious information of
|
||
the depth it also shows the ascent and descent rates compared to the recommended
|
||
speed of going up or down in the water column. This information is given using
|
||
different colours:</p></div>
|
||
<div class="tableblock">
|
||
<table rules="all"
|
||
width="100%"
|
||
frame="border"
|
||
cellspacing="0" cellpadding="4">
|
||
<col width="33%" />
|
||
<col width="33%" />
|
||
<col width="33%" />
|
||
<tbody>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table"><strong>Colour</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Descent speed (m/min)</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Ascent speed (m/min)</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Red</p></td>
|
||
<td align="left" valign="top"><p class="table">> 30</p></td>
|
||
<td align="left" valign="top"><p class="table">> 18</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Orange</p></td>
|
||
<td align="left" valign="top"><p class="table">18 - 30</p></td>
|
||
<td align="left" valign="top"><p class="table">9 - 18</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Yellow</p></td>
|
||
<td align="left" valign="top"><p class="table">9 - 18</p></td>
|
||
<td align="left" valign="top"><p class="table">4 - 9</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Light green</p></td>
|
||
<td align="left" valign="top"><p class="table">1.5 - 9</p></td>
|
||
<td align="left" valign="top"><p class="table">1.5 - 4</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Dark green</p></td>
|
||
<td align="left" valign="top"><p class="table">< 1.5</p></td>
|
||
<td align="left" valign="top"><p class="table">< 1.5</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
<div class="paragraph"><p>The profile also includes depth readings for the peaks and troughs in the graph.
|
||
Thus, users should see the depth of the deepest point and other peaks. Mean depth
|
||
is marked with a horizontal red line.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/scale.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">In some cases the dive profile does not fill the whole area of the <strong>Dive Profile</strong>
|
||
panel. Clicking the <strong>Scale</strong> button in the toolbar on the left of the dive profile
|
||
frequently increases the size of the dive profile to fill the area of the panel efficiently.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Water temperature</strong> is displayed with its own blue line with temperature values
|
||
placed adjacent to significant changes.</p></div>
|
||
<div class="paragraph"><p>The dive profile can include graphs of the <strong>partial pressures</strong>
|
||
of O2, N2, and He during the dive (see figure above) as well as a calculated and dive computer
|
||
reported deco ceilings (only visible for deep, long, or repetitive dives). Partial pressures of oxygen are indicated in green, those of nitrogen in black, and those of helium in dark red. These
|
||
partial pressure graphs are shown below the profile data.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/O2.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button allows display of the partial pressure of <strong>oxygen</strong> during the
|
||
dive. This is depicted below the dive depth and water temperature graphs.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/N2.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button allows display of the partial pressure of <strong>nitrogen</strong> during the dive.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/He.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button allows display of the partial pressure of <strong>helium</strong> during the dive.
|
||
This is only of importance to divers using Trimix, Helitrox or similar breathing gasses.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>The <strong>air consumption</strong> graph displays the tank pressure and its change during the
|
||
dive. The air consumption takes depth into account so that even when manually
|
||
entering the start and end pressures the graph is not a straight line.
|
||
Similarly to the depth graph the slope of the tank pressure gives the user information
|
||
about the
|
||
momentary SAC rate (Surface Air Consumption) when using an air integrated dive computer.
|
||
Here the colour
|
||
coding is not relative to some absolute values but relative to the average
|
||
normalised air consumption during the dive. So areas that are red or orange
|
||
indicate
|
||
times of increased normalized air consumption while dark green reflects times
|
||
when the diver was using less gas than average.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/Heartbutton.png" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking on the heart rate button will allow the display of heart rate information
|
||
during the dive if the dive computer was attached to a heart rate sensor.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>It is possible to <strong>zoom</strong> into the profile graph. This is done either by using
|
||
the scroll wheel / scroll gesture of your mouse or trackpad. By default
|
||
<em>Subsurface</em> always shows a profile area large enough for at least 30 minutes
|
||
and 30m
|
||
(100ft) – this way short or shallow dives are intuitively recognizable;
|
||
something
|
||
that free divers clearly won’t care about.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/MeasuringBar.png" alt="FIGURE: Measuring Bar" />
|
||
</div>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ruler.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Measurements of <strong>depth or time differences</strong> can be achieved by using the
|
||
<strong>ruler button</strong> on the left of the dive profile panel.
|
||
The measurement is done by dragging the red dots to the two points
|
||
on the dive profile that the user wishes to measure. Information is then given
|
||
in the horizontal white area underneath the
|
||
two red dots.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ShowPhotos.png" alt="Note" />
|
||
</td>
|
||
<td class="content">Photographs that have been added to a dive can be shown on the profile
|
||
by selecting
|
||
the <strong>Show-photo</strong> button. The position of a photo on the profile
|
||
indicates the exact time when this photo was taken. If this button is not active,
|
||
the photos are hidden.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>The profile can also include the dive computer reported <strong>ceiling</strong> (more
|
||
precisely, the deepest deco stop that the dive computer calculated for each
|
||
particular moment in time) as a red overlay on the dive profile. Ascent ceilings
|
||
arise when a direct ascent to the surface increases
|
||
the risk of a diver suffering from decompression sickness (DCS) and it is necessary
|
||
to either ascend
|
||
slower or to perform decompression stop(s) before ascending to the surface. Not
|
||
all dive computers record this information and make it available for download;
|
||
for example all of the Suunto dive computers fail to make this very useful data
|
||
available to divelog software. <em>Subsurface</em> also calculates ceilings independently,
|
||
shown as a green overlay on the dive profile.
|
||
Because of the differences in algorithms used
|
||
and amount of data available (and other factors taken into consideration at the time
|
||
of the calculation) it is unlikely that ceilings from dive computers and from <em>Subsurface</em>
|
||
are the same, even if the same algorithm and <em>gradient factors</em> (see below) are used.
|
||
It is also quite common that <em>Subsurface</em> calculates a ceiling for
|
||
non-decompression dives when the dive computer stayed in non-deco mode during
|
||
the whole dive (represented by the <span class="green">dark green</span> section in the profile
|
||
at the beginning of this section). This is caused by the fact that
|
||
<em>Subsurface’s</em>
|
||
calculations describe the deco obligation at each moment during a dive,
|
||
while dive computers usually take the upcoming ascent into account. During the
|
||
ascent some excess nitrogen (and possibly helium) are already breathed off so
|
||
even
|
||
though the diver technically encountered a ceiling at depth, the dive still does
|
||
not require an explicit deco stop. This feature allows dive computers to offer
|
||
longer non-stop bottom times.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/cceiling.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">If the dive computer itself calculates a ceiling and makes it available to
|
||
<em>Subsurface</em> during upload of dives, this can be
|
||
shown as a red area by checking <strong>Dive computer reported ceiling</strong> button on the Profile Panel.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling1.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">If the <strong>Calculated ceiling</strong> button on the Profile Panel is clicked, then a ceiling,
|
||
calculated by <em>Subsurface</em>, is shown in green if it exists for
|
||
a particular dive (<strong>A</strong> in figure below). This setting can be modified in two ways:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling2.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">If, in addition, the <strong>show all tissues</strong> button on the Profile Panel is clicked, the ceiling is shown for the tissue
|
||
compartments following the Bühlmann model (<strong>B</strong> in figure below).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling3.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">If, in addition, the <strong>3m increments</strong> button on the Profile Panel is clicked, then the ceiling is indicated in 3 m increments
|
||
(<strong>C</strong> in figure below).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Ceilings2.jpg" alt="Figure: Ceiling with 3m resolution" />
|
||
</div>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/tissues.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Display inert gas tissue pressures relative to ambient inert gas pressure (horizontal grey line).
|
||
Tissue pressures are calculated using the Bühlmann ZH-L16 algorithm and are displayed as lines ranging from
|
||
green (faster tissues) to blue (slower tissues).
|
||
The black line, graphed above the ambient pressure, is the maximum allowable tissue supersaturation (pressure limit) derived
|
||
from the gradient factors specified in the <strong>Preferences</strong>. For
|
||
divers involved in planned decompression diving, efficient rates of offgasing are obtained with tissue pressures
|
||
between the ambient inert gas pressure (grey line) and the pressure limit (black line). This display is a representation
|
||
of the tissue pressures during the whole dive. In contast, the <a href="#S_gas_pressure_graph">Gas Pressure Graph</a> in the <strong>Information Box</strong> on the <strong>Dive Profile</strong>
|
||
is an instantaneous reflection of tissue pressures at the moment in time reflected by the position of the cursor on the dive profile.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/tissuesGraph.jpg" alt="Figure: Inert gas tissue pressure graph" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Gradient Factor settings strongly affect the calculated ceilings and their depths.
|
||
For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>. The
|
||
currently used gradient factors (e.g. GF 35/75) are shown above the depth profile if the appropriate toolbar buttons are activated.
|
||
<strong>N.B.:</strong> The indicated gradient factors are NOT the gradient factors in use by the dive computer,
|
||
but those used by <em>Subsurface</em> to calculate deco obligations
|
||
during the dive. For more information external to this manual see:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_the_dive_profile_context_menu">5.4. The Dive Profile context menu</h3>
|
||
<div class="paragraph"><p>The context menu for the Dive Profile is accessed by right-clicking while the
|
||
mouse cursor is over the Dive Profile panel. The menu allows the creation of
|
||
Bookmarks or Gas Change Event markers other than the ones that might have been
|
||
imported from a Dive Computer. Markers are placed against the depth profile line
|
||
and with the time of the event set by where the mouse cursor was when the right
|
||
mouse button was initially clicked to bring up the menu. Gas Change events
|
||
open a further selection of which gas is being switched to, the list based on
|
||
the available gases defined in the Equipment Tab. By right-clicking while over
|
||
an existing marker, the menu extends adding options to allow deletion of the
|
||
marker or to allow all markers of that type to be hidden. Hidden events can be
|
||
restored to view by selecting Unhide all events from the context menu.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_the_strong_information_box_strong">5.5. The <strong>Information Box</strong></h3>
|
||
<div class="paragraph"><p>The Information box displays a large range of information pertaining to the dive
|
||
profile. Normally the Information Box is located to the top left of the <strong>Dive
|
||
Profile</strong> panel. If the mouse points outside of the <strong>Dive Profile</strong> panel, then
|
||
only the top line of the Information Box is visible (see left-hand part of
|
||
figure (<strong>A</strong>) below). The Information Box can be moved around in the <strong>Dive Profile</strong>
|
||
panel by click-dragging it with the mouse so that it is not obstructing
|
||
important detail. The position of the Information Box is saved and used again
|
||
during subsequent dive analyses.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/InfoBox2.jpg" alt="Figure: Information Box" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The moment the mouse points inside the <strong>Dive Profile</strong> panel, the information box expands and
|
||
shows many data items. In this situation, the data reflect the time point along
|
||
the dive profile indicated by the mouse cursor (see right-hand part of figure (<strong>B</strong>) above
|
||
where the Information Box reflects the situation at the position of the cursor
|
||
[arrow] in that image). Therefore, moving the cursor in the horizontal
|
||
direction allows the Information Box to show information for any point along the
|
||
dive profile.
|
||
In this mode, the Information Box gives extensive statistics about depth, gas
|
||
and ceiling characteristics of the particular dive. These include: Time period
|
||
into the dive (indicated by a @), depth, cylinder pressure (P), temperature,
|
||
ascent/descent rate, surface air consumption (SAC), oxygen partial pressure,
|
||
maximum operating depth, equivalent air depth (EAD), equivalent narcotic depth
|
||
(END), equivalent air density depth (EADD), decompression requirements at that
|
||
instant in time (Deco), time to surface (TTS), the calculated ceiling, as well
|
||
as the calculated ceiling for several Bühlmann tissue compartments.</p></div>
|
||
<div class="paragraph"><p>The user has control over the display of several statistics, represented as four
|
||
buttons on the left of the profile panel. These are:</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/MOD.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button causes the Information Box to display the <strong>Maximum Operating Depth
|
||
(MOD)</strong> of the dive, given the
|
||
gas mixture used. MOD is dependent on the oxygen concentration in the breathing gas.
|
||
For air (21% oxygen) it is around 57 m. Below the MOD there is a markedly increased
|
||
risk of exposure to the dangers associated with oxygen toxicity.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/NDL.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button causes the Information Box to display the <strong>No-deco Limit (NDL)</strong> or the
|
||
<strong>Total Time to Surface (TTS)</strong>. NDL is the time duration that a diver can continue with a
|
||
dive, given the present depth, that does not require decompression (that is, before an
|
||
ascent ceiling appears). Once one has exceeded the NDL and decompression is required (that
|
||
is, there is an ascent ceiling above the diver, then TTS gives the number of minutes
|
||
required before the diver can surface. TTS includes ascent time as well as decompression
|
||
time.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/SAC.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button causes the Information Box to display the <strong>Surface Air Consumption (SAC)</strong>.
|
||
SAC is an indication of the surface-normalised respiration rate of a diver. The value of SAC
|
||
is less than the real
|
||
respiration rate because a diver at 10m uses breathing gas at a rate roughly double that of
|
||
the equivalent rate at the surface. SAC gives an indication of breathing gas consumption rate
|
||
independent of the depth of the dive so that the respiratory rates of different dives
|
||
can be compared. The units for SAC is litres/min or cub ft/min.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/EAD.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Clicking this button displays the <strong>Equivalent Air Depth (EAD)</strong> for
|
||
nitrox dives as well as the <strong>Equivalent
|
||
Narcotic Depth (END)</strong> for trimix dives. These are numbers of
|
||
importance to divers who use breathing gases other than air. Their
|
||
values are dependent on the composition of the breathing gas. The EAD
|
||
is the depth of a hypothetical air dive that has the same partial
|
||
pressure of nitrogen as the current depth of the nitrox dive at
|
||
hand. A nitrox dive leads to the same decompression obligation as an
|
||
air dive to the depth equalling the EAD. The END is the depth of a
|
||
hypothetical air dive that has the same sum of partial pressures of
|
||
the narcotic gases nitrogen and oxygen as the current trimix dive. A
|
||
trimix diver can expect the same narcotic effect as a diver breathing
|
||
air diving at a depth equalling the END.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>Figure (<strong>B</strong>) above shows an information box with a nearly complete set of data.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="S_gas_pressure_graph">5.5.1. The Gas Pressure Bar Graph</h4>
|
||
<div class="paragraph"><p>On the left of the <strong>Information Box</strong> is a vertical bar graph indicating the
|
||
pressures of the nitrogen (and other inert gases, e.g. helium, if applicable) that the diver
|
||
was inhaling <em>at a particular instant during the dive</em>, indicated by the position
|
||
of the cursor on the <strong>Dive Profile</strong>. The drawing on the left below indicates the
|
||
meaning of the different parts of the Gas Pressure Bar Graph.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/GasPressureBarGraph.jpg" alt="FIGURE:Gas Pressure bar Graph" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The light green area indicates the total gas, with the top margin of the light green
|
||
area indicating the total gas pressure inhaled by the diver and measured from the bottom
|
||
of the graph to the top of the light green area. This pressure has a <em>relative</em> value in the graph
|
||
and does not indicate absolute pressure.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The horizontal black line underneath the light green margin indicates the equilibrium pressure
|
||
of the inert gases inhaled by the diver, usually nitrogen. In
|
||
the case of trimix, it is the pressures of nitrogen and helium combined. In this example,
|
||
the user is diving with EAN32, so the inert gas pressure is 68% of the distance from the
|
||
bottom of the graph to the total gas pressure value.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The dark green area at the bottom of the graph represents the pressures of inert gas in each
|
||
of the 16 tissue compartments, following the Bühlmann algorithm, the fast tissues being on the
|
||
left hand side.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The top black horizontal line indicates the the gradient factor that applies to the depth of
|
||
the diver at the particular point on the <strong>Dive Profile</strong>. The appropriate gradient factor is an
|
||
interpolation between the FGLow and GFHigh values specified in the Graph tab of the <strong>Preferences
|
||
Panel</strong> of <strong>Subsurface</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The bottom margin of the red area in the graph indicates the Bühlman-derived M-value, that is the
|
||
pressure value of inert gases at which bubble formation is expected to be severe, resulting
|
||
in decompression sickness.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>These five values are indicated on the left in the graph above. The way the Gas Pressure Bar Graph changes
|
||
during a dive is indicated on the right hand side of the above figure for a diver using EAN32.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Graph <strong>A</strong> indicates the situation at the start of a dive with diver at the surface. The pressures in all
|
||
the tissue compartments are still at the quilibrium pressure because no diving has taken place.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Graph <strong>B</strong> indicates the situation after a descent to 30 meters. Few of the tissue compartments have had
|
||
time to respond to the descent, their gas pressures being far below the equilibrium gas pressure.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Graph <strong>C</strong> represents the pressures after 30 minutes at 30 m. The fast compartments have attained
|
||
equilibrium (i.e. they have reached the hight of the black line indicating the equilibrium pressure). The
|
||
slower compartments (towards the right) have not reached equilibrium and are in the process of slowly
|
||
increasing in pressure.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Graph <strong>D</strong> shows the pressures after ascent to a depth of 4.5 meters. Since, during ascent, the total
|
||
inhaled gas pressure has decreased strongly from 4 bar to 1.45 bar, the pressures in the different tissue
|
||
compartments now exceed that of the total gas pressure and approaches the gradient factor value (i.e.
|
||
the top black horizontal line). Further ascent will result in exceeding the gradient
|
||
factor value (GFHigh), endangering the diver.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Graph <strong>E</strong> indicates the situation after remaining at 4.5 meters for 10 minutes. The fast compartments
|
||
have decreased in pressure. As expected, the pressures in the slow compartments have not changed much.
|
||
The pressures in the fast compartments do not approach the GFHigh value any more and the diver is safer
|
||
than in the situation indicated in graph <strong>D</strong>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_organising_the_logbook_manipulating_groups_of_dives">6. Organising the logbook (Manipulating groups of dives)</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_the_dive_list_context_menu">6.1. The Dive List context menu</h3>
|
||
<div class="paragraph"><p>Many actions within <em>Subsurface</em> are dependent on a context menu used
|
||
mostly to manipulate groups of dives. The context menu is found by selecting
|
||
a dive or a group of dives and then right-clicking.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/ContextMenu.jpg" alt="Figure: Context Menu" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The context menu is used in many manipulations described below.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_customising_the_information_showed_in_the_strong_dive_list_strong_panel">6.1.1. Customising the information showed in the <strong>Dive List</strong> panel</h4>
|
||
<div class="imageblock" style="text-align:left;">
|
||
<div class="content">
|
||
<img src="images/DiveListOptions.jpg" alt="Example: Dive list info options" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The default information in the <strong>Dive List</strong> includes, for each dive, Dive_number, Date, Rating, Dive_depth,
|
||
Dive_duration and Dive_location. This information can be contolled and changed by right-clicking on the
|
||
header bar of the <strong>Dive List</strong>. For instance, a right-click on the <em>Date</em> header brings up a list of items
|
||
that can be shown in the dive list (see above). Select an item to be shown in the <strong>Dive List</strong> or to be
|
||
deleted from the dive list, and the list is immediately updated accordingly. Preferences for information
|
||
shown in the <strong>Dive List</strong> is saved and used when <em>Subsurface</em> is re-opened.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_selecting_dives_from_a_particular_dive_site">6.1.2. Selecting dives from a particular dive site</h4>
|
||
<div class="paragraph"><p>Many divers have long dive lists and it may be difficult to locate all the dives at a particular site.
|
||
By pressing <em>Ctl-F</em> on the keyboard, a text box is opened at the top left hand of the <strong>Dive List</strong>.
|
||
Type the name of a dive site in this text box and the <strong>Dive List</strong> is immediately filtered to
|
||
show only the dives for that site.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Renumber">6.2. Renumbering the dives</h3>
|
||
<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low sequence
|
||
numbers) to recent dives (having the highest sequence numbers). The numbering
|
||
of the dives is not always consistent. For instance, when non-recent dives are
|
||
added to the dive list the numbering does not automatically follow on because
|
||
of the dives that are more recent in date/time than the newly-added dive with
|
||
an older date/time. Therefore, one may sometimes need to renumber the dives.
|
||
This is performed by selecting (from the Main Menu) <em>Log → Renumber</em>. Users are
|
||
given a choice with respect to the lowest sequence number to be used.
|
||
Completing this operation results in new sequence numbers (based on date/time)
|
||
for the dives in the <strong>Dive List</strong> panel.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Group">6.3. Grouping dives into trips and manipulating trips</h3>
|
||
<div class="paragraph"><p>For regular divers, the dive list can rapidly become very long. <em>Subsurface</em>
|
||
can group dives into <em>trips</em>. It performs this by grouping dives that have
|
||
date/times that are not separated in time by more than two days, thus creating
|
||
a single heading for each diving trip represented in the dive log. Below is an
|
||
ungrouped dive list (<strong>A</strong>, on the left) as well as the corresponding grouped dive
|
||
list comprising five dive trips (<strong>B</strong>, on the right):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Group2.jpg" alt="Figure: Grouping dives" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Grouping into trips allows a rapid way of accessing individual dives without
|
||
having to scan a long lists of dives. In order to group the dives in a dive list,
|
||
(from the Main Menu) users must select <em>Log → Autogroup</em>. The <strong>Dive List</strong> panel
|
||
now shows only the titles for the trips.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_editing_the_title_and_associated_information_for_a_particular_trip">6.3.1. Editing the title and associated information for a particular trip</h4>
|
||
<div class="paragraph"><p>Normally, in the dive list, minimal information is included in the trip title.
|
||
More information about a trip can be added by selecting its trip title from
|
||
the <strong>Dive List</strong>. This shows a <strong>Trip Notes</strong> tab in the <strong>Dive Notes</strong> panel. Here
|
||
users can add or edit information about the date/time, the trip location and any
|
||
other general comments about the trip as a whole (e.g. the dive company that was
|
||
dived with, the general weather and surface conditions during the trip, etc.).
|
||
After entering this
|
||
information, users should select <strong>Save</strong> from the buttons at the top right
|
||
of the <strong>Trip Notes</strong>
|
||
tab. The trip title in the <strong>Dive List</strong> panel should now reflect some of the
|
||
edited information.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_viewing_the_dives_during_a_particular_trip">6.3.2. Viewing the dives during a particular trip</h4>
|
||
<div class="paragraph"><p>Once the dives have been grouped into trips, users can expand one or more
|
||
trips by clicking the arrow-head on the left of each trip title. This expands
|
||
the selected trip, revealing the individual dives performed during the trip.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_collapsing_or_expanding_dive_information_for_different_trips">6.3.3. Collapsing or expanding dive information for different trips</h4>
|
||
<div class="paragraph"><p>If a user right-clicks after selecting a particular trip in the dive list, the
|
||
resulting context menu allows several possibilities to expand or collapse dives
|
||
within trips. This includes expanding all trips, collapsing all trips and
|
||
collapsing all trips except the selected one.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">6.3.4. Merging dives from more than one trip into a single trip</h4>
|
||
<div class="paragraph"><p>By right-clicking on a selected trip title in the <strong>Dive List</strong> panel, a
|
||
context menu shows up that allows the merging of trips by either merging of the selected trip
|
||
with the trip below or with the trip above.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_splitting_a_single_trip_into_more_than_one_trip">6.3.5. Splitting a single trip into more than one trip</h4>
|
||
<div class="paragraph"><p>If a trip includes five dives, the user can split this trip into two trips (trip 1:
|
||
top 3 dives; trip 2: bottom 2 dives) by selecting and right-clicking the top
|
||
three dives. The resulting context menu allows the user to create a new trip by
|
||
choosing the option <strong>Create new trip above</strong>. The top three dives are then
|
||
grouped
|
||
into a separate trip. The figures below shows the selection and context menu
|
||
on the left (A) and
|
||
the completed action on the right (B):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/SplitDive3a.jpg" alt="FIGURE: Split a trip into 2 trips" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_manipulating_single_dives">6.4. Manipulating single dives</h3>
|
||
<div class="sect3">
|
||
<h4 id="_delete_a_dive_from_the_dive_log">6.4.1. Delete a dive from the dive log</h4>
|
||
<div class="paragraph"><p>Dives can be permanently deleted from the dive log by selecting and
|
||
right-clicking them to bring up the context menu, and then selecting <strong>Delete
|
||
dive(s)</strong>. Typically this would apply to a case where a user wishes to delete
|
||
workshop
|
||
calibration dives of the dive computer or dives of extremely short duration.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_unlink_a_dive_from_a_trip">6.4.2. Unlink a dive from a trip</h4>
|
||
<div class="paragraph"><p>Users can unlink dives from the trip to which they belong. In order to do this,
|
||
select and right-click
|
||
the relevant dives to bring up the context menu. Then select the option <strong>Remove dive(s)
|
||
from trip</strong>. The dive(s) now appear immediately above the trip to
|
||
which they belonged.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_add_a_dive_to_the_trip_immediately_above">6.4.3. Add a dive to the trip immediately above</h4>
|
||
<div class="paragraph"><p>Selected dives can be moved from the trip to which they belong and placed within
|
||
the trip immediately above the currently active trip. To do this, select
|
||
and right-click
|
||
the dive(s) to bring up the context menu, and then select <strong>Add dive(s) to trip
|
||
immediately above</strong>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_shift_the_start_time_of_dive_s">6.4.4. Shift the start time of dive(s)</h4>
|
||
<div class="paragraph"><p>Sometimes it is necessary to adjust the start time of a dive. This may apply to
|
||
situations where dives are performed in different time zones or when the dive
|
||
computer has an erroneous time. In order to do this, user must select and right-click
|
||
the dive(s) to be
|
||
adjusted. This action brings up the context menu on which the <strong>Shift times</strong>
|
||
option should be selected. User must then specify the
|
||
time
|
||
(in hours and minutes) by which the dives should be adjusted and click on the
|
||
option indicating whether the time adjustment should be forwards or backwards.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_merge_dives_into_a_single_dive">6.4.5. Merge dives into a single dive</h4>
|
||
<div class="paragraph"><p>Sometimes a dive is briefly interrupted, e.g. if a diver returns to the surface
|
||
for a few minutes, resulting in two or more dives being recorded by the dive
|
||
computer and appearing as different dives in the <strong>Dive List</strong> panel. Users can
|
||
merge these dives onto a single dive by selecting the appropriate dives,
|
||
right-clicking them to bring up the context menu and then selecting <strong>Merge selected
|
||
dives</strong>. It may be necessary to edit the dive information in the <strong>Dive Notes</strong>
|
||
panel to reflect events or conditions that apply to the merged dive. The figure
|
||
below shows the depth profile of two such dives that were merged:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/MergedDive.png" alt="Example: Merged dive" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_filtering_the_dive_list">6.5. Filtering the dive list</h3>
|
||
<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, that is, one can select only some
|
||
of the dives based on their attributes, e.g. dive tags, dive site, dive master, buddy or protective
|
||
clothing. For instance, filtering allows one to list the deep dives at a particular
|
||
dive site, or otherwise the cave dives with a particular buddy.</p></div>
|
||
<div class="paragraph"><p>To open the filter, select <em>Log → Filter divelist</em> from the main menu. This opens the
|
||
<em>Filter Panel</em> at the top of the <em>Subsurface</em> window. Three icons are located at the top
|
||
right hand of the filter panel. The <em>Filter Panel</em> can be reset
|
||
(i.e. all current filters cleared) by selecting the <strong>+</strong>. The <em>Filter Panel</em> may also be
|
||
minimised by selecting the middle icon. When minimised, only these three icons are shown.
|
||
The panel can be maximised by clicking the icon that minimised the panel. The filter may also be
|
||
reset and closed by selecting the button with the flag.
|
||
An example of the <em>Filter Panel</em> is shown in the figure below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Filterpanel.jpg" alt="Figure: Filter panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Four filter criteria may be used to filter the dive list: dive tags, person (buddy / dive master), dive site
|
||
and dive suit, each of which is represented by a check list with check boxes. Above
|
||
each check list is a second-level filter tool, allowing the listing of only some of
|
||
the attributes within that check list. For instance, typing "<em>ca</em>" in the filter
|
||
textbox above the tags check list results in the tags check list being reduced
|
||
to "<em>cave</em>" and "<em>cavern</em>". Filtering of the check list enables the rapid finding
|
||
of search terms for filtering the dive list.</p></div>
|
||
<div class="paragraph"><p>To activate filtering of the dive list, the check box of at least one item in one of
|
||
the four check lists needs to be checked. The dive list is then shortened to include
|
||
only the dives that pertain to the selection criteria specified in the check lists.
|
||
The four check lists work as a filter with <em>AND</em> operators, Subsurface
|
||
filters therfore for <em>cave</em> as a tag AND <em>Joe Smith</em> as a buddy; but the
|
||
filters within a category are inclusive - filtering for <em>cave</em> and <em>boat</em>
|
||
shows those dives that have either one or both of these tags.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_ExportLog">7. Exporting the dive log or parts of the dive log</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>The export function can be reached by selecting <em>File → Export</em>, which brings up
|
||
the Export dialog. This dialog always gives two options: save ALL dives, or save only
|
||
the dives selected in <strong>Dive List</strong> panel of <em>Subsurface</em>. Click the appropriate
|
||
radio button (see images below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Export.jpg" alt="Figure: Export dialog" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>A dive log or part of it can be saved in three formats:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface XML</em> format. This is the native format used by <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Universal Dive Data Format (<em>UDDF</em>). Refer to <em>http://uddf.org</em> for more information.
|
||
UDDF is a generic format that enables communication among many dive computers
|
||
and computer programs.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Divelogs.de</em>, an Internet-based dive log repository. In order to upload to <em>Divelogs.de</em>,
|
||
one needs a user-ID as well as a password for <em>Divelogs.de</em>. Log into <em>http://en.divelogs.de</em>
|
||
and subscribe to this service in order to upload dive log data from <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CSV</em> format, that includes the most critical information of the dive
|
||
profile. Included information of a dive is: dive number, date, time,
|
||
duration, depth, temperature and pressure.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Worldmap</em> format, an HTML file with a world map upon which each dive and
|
||
some information about it are indicated. This map is not editable.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>HTML</em> format, in which the dive(s) are stored in HTML files, readable
|
||
with an Internet browser. Most modern web browsers are supported, but Javascript
|
||
must be enabled. This generated HTML file is not intended to be edited
|
||
by the users.
|
||
The HTML dive log contains most of the information and also contains a search
|
||
option to search the dive log. HTML export is specified on the second tab of the
|
||
Export dialog (image <strong>B</strong> above).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>General Settings</em>, under the HTML tab, provides the following options:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Subsurface Numbers: if this option is checked, the dive(s) are exported with the
|
||
numbers associated with them in Subsurface, Otherwise the dive(s) will be numbered
|
||
starting from 1.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Export Yearly Statistics: if this option is checked, a yearly statistics table will
|
||
be attached with the HTML exports.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Export List only: a list of dives will only be exported and the detailed dive
|
||
information will not be available.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Under <em>Style Options</em> some style-related options are available like font
|
||
size and theme.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Export to other formats can be achieved through third party facilities, for
|
||
instance <em>www.divelogs.de</em>.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_Cloud_access">8. Keeping a <em>Subsurface</em> dive log in the Cloud</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>For each diver, dive log information is highly important. Not only is it a record
|
||
of diving activities for one’s own pleasure, but it is important information required
|
||
for admission to further training courses or (sometimes) even diving sites. The
|
||
security of the dive log is therefore critical. In order to have a dive log that is
|
||
resistant to failure of a home computer hard drive, loss or theft of equipment, the
|
||
Cloud is an obvious solution. This also has the added benefit that one can access one’s dive
|
||
log from anywhere in the world without having to carry it with oneself. For this
|
||
reason, facilities such as <em>divelogs.de</em> and <em>Diving Log</em> offer facilities to store
|
||
dive log information on the Internet. Although <em>Subsurface</em> does not offer integrated
|
||
Cloud storage of dive logs, it is simple to achieve this using several of the
|
||
existing facilities on the Internet.</p></div>
|
||
<div class="paragraph"><p>For instance
|
||
<a href="http://www.dropbox.com/"><em>Dropbox</em></a>
|
||
offers a free application that allows
|
||
files on the Dropbox servers to be seen as a local folder on one’s desktop computer.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Cloud.jpg" alt="FIGURE: Dropbox folder" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The <em>Dropbox</em> program creates a copy of the <em>Dropbox</em> Internet Cloud content on one’s
|
||
desktop computer. When the computer is connected to the Internet, the Internet
|
||
content is automatically updated. Therefore both the <em>Open</em> and <em>Save</em> of dive logs are done
|
||
using the local copy of the dive log in the local <em>Dropbox</em> folder, so there’s no need
|
||
for a direct internet connection. If the local copy is modified, e.g. by adding a dive,
|
||
the remote copy in the <em>Dropbox</em> server in the Cloud will be automatically updated whenever
|
||
Internet access is available.</p></div>
|
||
<div class="paragraph"><p>In this way a dive log in
|
||
one’s <em>Dropbox</em> folder can be accessed seamlessly from the Internet and can
|
||
be accessed from any place with Internet access. Currently there are no costs
|
||
involved for this service. Dropbox (Windows, Mac
|
||
and Linux) can be installed by accessing the
|
||
<a href="http://www.dropbox.com/install"><em>Install Page on the Dropbox website</em></a>
|
||
. Alternatively one can use <em>Dropbox</em> as a mechanism to backup one’s dive log. To
|
||
Store a dive log in the Cloud, select <em>File→Save as</em> from the <em>Subsurface</em> main menu,
|
||
navigate to the <em>Dropbox</em> folder and select the <em>Save</em> button. To access the dive log
|
||
in the Cloud, select <em>File→Open Logbook</em> from the <em>Subsurface</em>
|
||
main menu and navigate to the dive log file in the <em>Dropbox</em> folder and select the
|
||
<em>Open</em> button.</p></div>
|
||
<div class="paragraph"><p>Several paid services exist on the Internet (e.g. Google, Amazon) where the same
|
||
process could be used for the Cloud-based storage of dive logs.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_PrintDivelog">9. Printing a dive log</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> provides a simple interface to print a whole dive log or only a
|
||
few selected dives, including dive profiles and other contextual information.</p></div>
|
||
<div class="paragraph"><p>Before printing, two decisions are required:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Should the whole dive log be printed or only part of it? If only part of the
|
||
dive log is required, then the user must select the required dives from the <strong>Dive List</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
What gas partial pressure information is required on the dive profile? Users should select
|
||
the appropriate toggle-buttons on the button bar to the left of the Dive Profile panel.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Now the print options should be selected to match the user’s needs. To do this, user should select <em>File→Print</em> from
|
||
the Main menu. The following dialogue appears (see the image on the left [A],
|
||
below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/PrintDiveLog.jpg" alt="FIGURE: Print dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Under <em>Print type</em> users need to select one of three options:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Print the complete Dive List: to do this, <em>Table Print</em> should be selected.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Print the selected dives (dive profiles and all other information) at 6
|
||
dives per printed page: to do this, users should select <em>6 dives per page</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Print the selected dives (dive profiles and all other information) at 2
|
||
dives per printed page: to do this, users should select <em>2 dives per page</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Print the selected dives (dive profiles and all other information) at 1
|
||
dive per printed page: to do this, users should select <em>1 dive per page</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Under <em>Print options</em> users need to select:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Printing only the dives that have been selected from the dive list prior to
|
||
activating the print dialogue, achieved by checking the box <em>Print only
|
||
selected dives</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Printing in colour, achieved by checking the box with <em>Print in colour</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The <em>Ordering</em> affects the layout of the page (or part of it) for each dive.
|
||
The dive profile could be printed at the top of each dive, with the textual
|
||
information underneath, or it could be printed with the textual information at
|
||
the top with the dive profile underneath. Users should select the appropriate option in the
|
||
print dialogue. See the image below which has a layout with
|
||
text below the dive profile.</p></div>
|
||
<div class="paragraph"><p>Users can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on the
|
||
dialogue. After preview, changes to the options in the print dialogue can be
|
||
made, resulting in a layout that fits personal taste.</p></div>
|
||
<div class="paragraph"><p>Next, select the <em>Print</em> button in the dialogue. This activates the regular print
|
||
dialogue used by the user operating system (image [<strong>B</strong>] in the middle, above),
|
||
allowing them to choose a printer and to set its properties (image [<strong>C</strong>] on the right,
|
||
above).
|
||
It is important to set the print resolution of the printer to an appropriate value by
|
||
changing
|
||
the printer properties. Finally, one can print the dives. Below is a (rather small)
|
||
example of
|
||
the output for one particular page.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Printpreview.jpg" alt="FIGURE: Print preview page" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_Preferences">10. Setting user <em>Preferences</em> for <em>Subsurface</em></h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>There are several settings within <em>Subsurface</em> that the user can specify. These
|
||
are found when selecting <em>File→Preferences</em>. The settings are performed in
|
||
five groups: <strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>. All five sections
|
||
operate on the same principles: the user must specify the settings that are to be changed, then
|
||
these changes are saved using the <strong>Apply</strong> button. After applying all the new settings users can then
|
||
leave the settings panel by selecting <strong>OK</strong>.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_defaults">10.1. Defaults</h3>
|
||
<div class="paragraph"><p>There are several settings in the <strong>Defaults</strong> panel:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref1.jpg" alt="FIGURE: Preferences defaults page" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Lists and tables</strong>: Here one can specify the font type and font size of the
|
||
<strong>Dive Table</strong> panel. By decreasing the font size of the <strong>Dive Table</strong>, users can see more dives on a screen.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Dives</strong>: For the <em>Default Dive File</em> one need to specify the directory and
|
||
file name of one’s
|
||
electronic dive log book. This is a file with filename extension .xml. When
|
||
launched, <em>Subsurface</em> will automatically load the specified dive log book.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide
|
||
dives that he/she don’t consider valid dives, e.g. pool dives, but still want to
|
||
keep them in the dive log). This controls whether those dives are displayed in
|
||
the dive list.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Default cylinder</strong>: Here users can specify the default cylinder listed in
|
||
the <strong>Equipment</strong> tab of the <strong>Dive Notes</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Animations</strong>: Some actions in showing the dive profile are performed using
|
||
animations. For instance, the axis values for depth and time change from dive to
|
||
dive. When viewing a different dive, these changes in axis characteristics do not
|
||
happen instantaneously, but are animated. The <em>Speed</em> of animations can be controlled
|
||
by setting this slider
|
||
with faster animation speed to the left, with a 0 value representing no animation
|
||
at all.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Subsurface web service</strong>: When one subscribes to the <a href="#S_Companion">Subsurface web service</a>, a very
|
||
long and hard-to-remember userID is issued. This is the place to save that userID. By
|
||
checking the option <em>Save User ID locally?</em>, one ensures that a local copy of that userID
|
||
is saved.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Clear all settings</strong>: As indicated in the button below this heading, all settings are
|
||
cleared and set to default values.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_units">10.2. Units</h3>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref2.jpg" alt="FIGURE: Preferences Units page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Here user can choose between metric and imperial units of depth, pressure,
|
||
volume, temperature and mass. By selecting the Metric or Imperial radio button
|
||
at the top, users can specify that all units are in the chosen measurement system.
|
||
Alternatively, if one selects the <strong>Personalise</strong> radio button, units can be selected
|
||
independently, with some units in the metric system and others in imperial.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_graph">10.3. Graph</h3>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref3.jpg" alt="FIGURE: Preferences Graph page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph" id="S_GradientFactors"><p>This panel allows two type of selections:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Show</strong>: Here users can specify the amount of information shown as part of
|
||
the dive profile:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Thresholds: <em>Subsurface</em> can display the nitrogen, oxygen and the helium partial pressures during
|
||
the dive. These are enabled using the toolbar on the left hand side of the <strong>Dive Profile</strong>
|
||
panel. For each of these graphs users can specify a threshold value on the right-hand side of the
|
||
Preferences panel. If any of the graphs go above this threshold level, the graph is
|
||
highlighted in red, indicating that the threshold has been exceeded.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Draw dive computer reported ceiling red</em>: This checkbox allows exactly what it says.
|
||
Not all dive computers report ceiling values. If the dive computer does report it, it may differ
|
||
from the ceilings calculated by <em>Subsurface</em>. This is because of the different algorithms and gradient factors available for calculating ceilings, as well as the dynamic way that a
|
||
dive computer can calculate ceilings during a dive.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Show unused cylinders in Equipment Tab</em>: This checkbox allows display of information about unused cylinders when viewing the <strong>Equipment Tab</strong>. Conversely, if this box is not checked, and any cylinders entered using the <strong>Equipment Tab</strong> are not used (e.g. there was no gas switch to such a cylinder), then these cylinders are omitted from that list.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Show average depth</em>: Activating this checkbox causes <em>Subsurface</em> to draw a red line across
|
||
the dive profile, indicating the mean depth of the dive.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Misc</strong>:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Gradient Factors:* Here users can set the <em>gradient factors</em> used while diving. GF_Low is
|
||
the gradient factor at depth and GF_High is used just below the surface.
|
||
At intermediate depths gradient factors between GF_Low and GF_High are used.
|
||
Gradient factors add conservatism to the nitrogen exposure during a dive, in a
|
||
similar way that many dive computers have a conservatism setting. The lower
|
||
the value of a gradient factor, the more conservative the calculations are with
|
||
respect to nitrogen loading and the deeper the ascent ceilings are. Gradient
|
||
factors of 20/60 are considered conservative and values of 60/90 are considered
|
||
harsh. Checking <strong>GFLow at max depth</strong> box causes GF_Low to be used at the
|
||
deepest depth of a dive. If this box is not checked, GF_Low is applied at
|
||
all depths deeper than the first deco stop. For more information see:
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_language">10.4. Language</h3>
|
||
<div class="paragraph"><p>Choose a language that <em>Subsurface</em> will use.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref4.jpg" alt="FIGURE: Preferences Language page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>A checkbox allows one to use the <em>System Default</em> language which in most cases
|
||
will be the correct setting; with this <em>Subsurface</em> simply runs in the same
|
||
language / country settings as the underlying OS. If this is for some reason
|
||
undesirable users can uncheck this checkbox and pick a language / country
|
||
combination from the list of included localizations. The <em>Filter</em> text box allows
|
||
one to list similar languages. For instance there are several system variants of English
|
||
or French. This particular preference requires a restart of <em>Subsurface</em> to take
|
||
effect.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_network">10.5. Network</h3>
|
||
<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources on the Internet.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref5.jpg" alt="FIGURE: Preferences Network page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This is important, for instance, when <em>Subsurface</em> needs to communicate with Internet
|
||
services such as the <a href="#S_Companion"><em>Subsurface Companion app</em></a> or data export/import
|
||
from <em>Divelogs.de</em>. These Internet requirements are determined by one’s type of
|
||
connection to the Internet and by the Internet Service Provider (ISP) used.
|
||
One’s ISP should provide the appropriate information.
|
||
If a proxy server is used for Internet access, the appropriate information needs
|
||
to be provided here. The type of proxy needs to be selected from the dropdown list.
|
||
after which the IP address of the host and the appropriate port number should
|
||
be provided. If the proxy server uses authentication, the appropriate userID and
|
||
password also needs to be provided so that <em>Subsurface</em> can automatically pass
|
||
through the proxy server to access the Internet.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_DivePlanner">11. The <em>Subsurface</em> dive planner</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessible by selecting <em>Log → Plan Dive</em> from the main menu. It allows calculation of
|
||
nitrogen load during a dive by using the Bühlmann ZH-L16 algorithm with the addition of gradient factors as
|
||
implemented by Erik Baker.</p></div>
|
||
<div class="sidebarblock">
|
||
<div class="content">
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">The <em>Subsurface</em> dive planner IS CURRENTLY EXPERIMENTAL
|
||
and assumes the user is already familiar with the <em>Subsurface</em>
|
||
user interface. It is explicitly used under the following conditions:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The user is conversant with dive planning and has the necessary training to perform
|
||
dive planning.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The user plans dives within his/her certification limits.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Dive planning makes large assumptions about the characteristics of the <em>average person</em>
|
||
and cannot compensate for individual physiology or health or personal history or
|
||
life style characteristics.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The safety of a dive plan depends heavily on the way in which the planner is used.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The user is familiar with the user interface of <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
A user who is not absolutely sure about any of the above requirements should not use
|
||
this feature.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div></div>
|
||
<div class="sect2">
|
||
<h3 id="_the_em_subsurface_em_dive_planner_screen">11.1. The <em>Subsurface</em> dive planner screen</h3>
|
||
<div class="paragraph"><p>Like the <em>Subsurface</em> dive log, the planner screen is divided into several sections (see image below). The <strong>setup</strong>
|
||
parameters for a dive are entered into the several sections on the left hand side of the screen.
|
||
The setup is divided into several sections: Available Gases, Rates, Planning, Gas Options and Dive Notes.</p></div>
|
||
<div class="paragraph"><p>At the top right hand is a green <strong>design panel</strong> upon which the profile of the dive can be
|
||
manipulated directly by dragging and clicking as explained below. This feature makes the
|
||
<em>Subsurface</em> dive planner unique in ease of use.</p></div>
|
||
<div class="paragraph"><p>At the bottom right is a text panel with a heading of <em>Dive Plan Details</em>. This is where the details of
|
||
the dive plan are provided in a way that can easily be copied to other software. This is also where
|
||
any warning messages about the dive plan are printed.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/PlannerWindow1.jpg" alt="FIGURE: Dive planner startup window" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_initiating_dive_planning">11.2. Initiating dive planning</h3>
|
||
<div class="paragraph"><p>The dive planner comprises two parts: <strong>constructing a dive plan</strong> and <strong>evaluating</strong>
|
||
that dive plan. To perform dive planning, perform these steps:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Clear the existing dive log by creating a new planning log. This is achieved by selecting
|
||
<em>File → New logbook</em> from the main menu. This way, dive plans are kept separate
|
||
from the existing dive log of completed dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the top left-hand area of the screen, ensure that the constant dive parameters are
|
||
appropriate. These are: Start date and time of the dive, Atmospheric Pressure and Altitude
|
||
above sea level of the dive site. The atmospheric pressure can also be entered as an altitude
|
||
in metres, assuming an atmospheric pressure of 1.013 bar.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the table labelled <em>Available Gases</em>, add the information of the cylinders to be used
|
||
as well as the gas composition within that cylinder. This is done in a similar way as for
|
||
<a href="#S_CylinderData">providing cylinder data for dive logs</a>. Choose the cylinder type by
|
||
double clicking the cylinder type and using the dropdown list, then specify the work
|
||
pressure of this cylinder. By leaving the oxygen concentration (O2%) filed empty,
|
||
the dive gas is assumed to be air. Otherwise enter the oxygen and/or helium
|
||
concentration in the boxes provided in this dialogue. Add additional cylinders by using the
|
||
"+" icon to the top righthand of the dialogue.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The dialogue indicating <em>Dive Planner Points</em> is usually not used at this stage of the dive
|
||
planning.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_managing_nitrogen_oxygen_and_gas_consumption">11.3. Managing nitrogen, oxygen and gas consumption</h3>
|
||
<div class="paragraph"><p>The planning is performed in three stages:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>a) Nitrogen management</strong>: This is performed by specifying the rates for descent and ascent,
|
||
as well as the gradient factors (GFLow and GFHigh) under the headings <em>Rates</em> and <em>Planning</em>
|
||
to the bottom left of the planning screen. Initially, the GFHigh and GFLow values in the <em>Preferences</em>
|
||
panel of <em>Subsurface</em> is used. If these are changed within the planner (see <em>Gas Options</em> within
|
||
the planner), the new values are
|
||
used without changing the original specifications in the <em>Preferences</em>. Gradient Factor settings strongly affect the calculated ceilings and their depths.
|
||
A very low GFLow value brings about decompression stops early on during the dive.
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.
|
||
For more information external to this manual see:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.amazon.com/Deco-Divers-Decompression-Theory-Physiology/dp/1905492073/ref=sr_1_1?s=books&ie=UTF8&qid=1403932320&sr=1-1&keywords=deco+for+divers"><em>Deco for Divers</em>, by Mark Powell (2008). Aquapress</a> Southend-on-Sea, UK. ISBN 10: 1-905492-07-3.
|
||
An excellent non-technical review.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified
|
||
for several depth ranges, utilising the average (or mean) depth as a yardstick. The mean depth
|
||
of the dive plan is indicated on the dive profile in the green panel of the dive planner. Ascent rates
|
||
at deeper levels are often in the range of 8-12 m/min, while ascent rates near the surface are
|
||
often in the range of 4-9 m/min. The descent rate is also specified. If the option <em>Drop to first depth</em>
|
||
is activated, then the descent phase of the planned dive will be at the maximal descent rate specified
|
||
in the <em>Rates</em> section of the dive setup.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>b) Oxygen management</strong>: In the <strong>Gas Options</strong> part of the dive specification, the maximum partial
|
||
pressure for oxygen needs to be specified for the
|
||
bottom part of the dive (<em>bottom po2</em>) as well as for the decompression part of the dive (<em>deco po2</em>).
|
||
The most commonly
|
||
used values are 1.4 bar for the bottom part of the dive and 1.6 bar for any decompression
|
||
stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 settings and the depth at which switching to a gas takes place can also be edited in the
|
||
<em>Available Gases</em> dialog. Normally the planner decides on switching to a new gas when, during
|
||
ascent, the partial pressure of the new gas has decreased to 1.6 bar.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>c) Gas management</strong>: One needs keep within the limits of the amount of gas contained in the dive
|
||
cylinder(s), allowing for an appropriate margin for safe return to the surface, possibly
|
||
sharing with a buddy. Under the <em>Gas Options</em> heading, specify the best (but conservative) estimate
|
||
of your surface-equivalent air consumption (SAC, also termed RMV) in
|
||
litres/min (for the time being, only SI units are supported). Specify the SAC during the
|
||
bottom part of the dive (<em>bottom SAC</em>) as well as during the decompression or safety stops of the
|
||
dive (<em>deco SAC</em>). Values of 20-30 l/min are common. For good gas management, a thumbsuck guess
|
||
is not sufficient and one needs to
|
||
monitor one’s gas consumption on a regular basis, dependent on different dive conditions and/or equipment.
|
||
The planner will calculate the total volume of gas used during the dive and will issue a warning
|
||
if one exceeds the total amount of gas available. Good practice demands that one does not dive to
|
||
the limit of the gas supply but that an appropriate reserve is kept for unforeseen circumstances.
|
||
For technical diving, this reserve can be up to 66% of the total available gas.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Now (at last) one can start the detailed time-depth planning of the dive. <em>Subsurface</em> offers a unique
|
||
graphical interface for performing this part of the planning. The mechanics of doing this is
|
||
similar to hand-entering a dive profile in the dive log part of <em>Subsurface</em>. Upon activating the
|
||
planner, a default dive of depth 15 m for 40 min is offered in the green design surface to the top
|
||
right hand of the screen. The white dots (waypoints) on the
|
||
profile can be dragged with a mouse. Create more waypoints by double-clicking on the profile
|
||
line and ensuring that the profile reflects the intended dive. Drag the waypoints to represent
|
||
the depth and duration of the dive.
|
||
If any of the management limits (for nitrogen, oxygen or gas) is exceeded, the surface
|
||
above the dive profile changes from BLUE to RED.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Each waypoint on the dive profile creates a <em>Dive Planner Point</em> in the table on the
|
||
left of the dive planner panel. Ensure that the <em>Used Gas</em> value in each row
|
||
of that table corresponds to one of the gas mixtures specified in the table with
|
||
<em>Available Gases</em> immediately above the Dive Planner Points. Add new waypoints
|
||
until the main features of the dive have been completed, e.g. the
|
||
bottom time segment and deep stops (if these are implemented). Leave the remaining
|
||
waypoints on the ascent to <em>Subsurface</em>. In most cases <em>Subsurface</em>
|
||
computes additional way points in order to fulfil decompression requirements for that
|
||
dive.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
A waypoint can be moved by selecting that waypoint and by using the arrow keys.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The waypoints listed in the <em>Dive Planner Points</em> dialogue can be edited by hand in
|
||
order to obtain a precise presentation of the dive plan. In fact, one can create the
|
||
whole dive profile by editing the <em>Dive Planner Points</em> dialog.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Indicate any changes in gas cylinder used by indicating gas changes as explained
|
||
in the section <a href="#S_CreateProfile">hand-creating a dive profile</a>. These changes should
|
||
reflect the cylinders and gas compositions defined in the table with <em>Available Gases</em>.
|
||
If two or more gases are used, automatic gas switches will be suggested during the ascent to
|
||
the surface. However, these changes can be deleted by right-clicking the gas change and by
|
||
manually creating a gas change by right-clicking on the appropriate waypoint.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Below is an example of a dive plan to 45m using EAN26, followed by an ascent using EAN50
|
||
and using the settings as described above.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DivePlanner2.jpg" alt="FIGURE: Planning a dive: setup" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Once the above has been completed, one can save it by clicking the <em>Save</em> button
|
||
towards the bottom left of the green design panel. The saved dive plan will appear
|
||
in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_the_dive_plan_details">11.4. The dive plan details</h3>
|
||
<div class="paragraph"><p>On the bottom right of the dive planner, under <em>Dive Plan Details</em>, the exact details
|
||
of the dive plan are provided. These details may be modified by checking any of the
|
||
options under the <em>Dive Notes</em> section of the dive planner, immediately to the left
|
||
of the <em>Dive Plan Details</em>. If a <em>Verbatim diveplan</em>
|
||
is requested, a detailed sentence-level explanation of the dive plan is given. If any
|
||
of the management specifications have been exceeded during the planning, a warning
|
||
message is printed underneath the dive plan information.</p></div>
|
||
<div class="paragraph"><p>If the option <em>Display segment duration</em> is checked, then the duration of each depth
|
||
level is indicated in the <em>Dive Plan Details</em>. This duration INCLUDES the transition
|
||
time to get to that level. However, if the <em>Display transition in deco</em> option is checked,
|
||
the transitions are shown separately from the segment durations at a particular level.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Replan">11.5. Modifying an existing dive plan</h3>
|
||
<div class="paragraph"><p>Normally, when a dive plan has been saved, it is accessible from the <strong>Dive List</strong>, like any
|
||
other dive log. Within the <strong>Dive List</strong> there is not a way to change a saved dive plan.
|
||
To perform changes to a dive plan, select it on the <strong>Dive List</strong>. Then, in the main menu,
|
||
select <em>Log → Re-plan dive</em>. This will open the selected dive plan within the dive planner,
|
||
allowing changes to be made and saved as usual.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_planning_for_repetitive_dives">11.6. Planning for repetitive dives</h3>
|
||
<div class="paragraph"><p>Repetitive dives can easily be planned if the dates and start times of the
|
||
repetitive dive set
|
||
is specified appropriately in the top left-hand <em>Start Time</em> field. <em>Subsurface</em>
|
||
calculates the gas loading figures correctly and the effect of the first dive is
|
||
evaluated on later dives.</p></div>
|
||
<div class="paragraph"><p>If one has just completed a long/deep dive and is planning
|
||
another dive, then highlight, in the <strong>Dive List</strong>, the dive that has just been completed
|
||
and then activate the planner. Depending on the start time of the planned dive,
|
||
the planner takes into account the gas loading incurred during the completed dive
|
||
and allows planning within these limitations.</p></div>
|
||
<div class="paragraph"><p>If only a few standard configurations are used (e.g. in GUE), then a template dive can
|
||
be created conforming to one of the configurations. If one now wishes to plan a dive using
|
||
this configuration, just highlight the template dive in the <strong>Dive List</strong> and activate the
|
||
planner: the planner takes into account the configuration in the highlighted dive.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_printing_the_dive_plan">11.7. Printing the dive plan</h3>
|
||
<div class="paragraph"><p>Selecting the <em>Print</em> button in the planner allows printing of the <em>Dive Plan Details</em>
|
||
for wet notes. Alternatively one can cut and paste the <em>Dive Plan Details</em> for
|
||
inclusion in a text file or word processing document.</p></div>
|
||
<div class="paragraph"><p>Dive plans have many characteristics in common with dive logs (dive profile, dive notes, etc).
|
||
After a dive plan has been saved, the dive details and gas calculations are saved in
|
||
the <strong>Dive Notes</strong> tab. While a dive plan is being designed, it can be printed using
|
||
the <em>Print</em> button in the dive planner. This prints the dive details and gas calculations
|
||
in the <em>Dive Plan Details</em> panel of the dive planner. However, after the plan has been saved, it is
|
||
represented in a way very similar to a dive log and the gas calculations cannot be
|
||
accessed in the same way as during the planning process. The only way to print the
|
||
dive plan is to use the <em>File→Print</em> facility on the main menu in the same way as for dive logs.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_description_of_the_subsurface_main_menu_items">12. Description of the Subsurface Main Menu items</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>This section describes the functions and operation of the items in the Main Menu
|
||
of Subsurface. Several of the items below are links to sections of this manual
|
||
dealing with the appropriate operations.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_file">12.1. File</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_NewLogbook"><em>New Logbook</em></a> - Close the currently open dive logbook and
|
||
clear all dive information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Open logbook</em> - This opens the file manager in order to select a dive
|
||
logbook to open.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Save</em> - Save the dive logbook that is currently open.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Save as</em> - Save the current logbook under a different file name.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Close</em> - Close the dive logbook that is currently open.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ExportLog"><em>Export</em></a> - Export the currently open dive logbook (or
|
||
the selected dives in the logbook) to one of several formats.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_PrintDivelog"><em>Print</em></a> - Print the currently open logbook.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Preferences"><em>Preferences</em></a> - Set the <em>Subsurface</em> preferences.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Quit</em> - Quit <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Configure dive computer</em> - This option is currently experimental and under development.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_import">12.2. Import</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ImportDiveComputer"><em>Import from dive computer</em></a> - Import dive information
|
||
from a dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#Unified_import"><em>Import Log Files</em></a> - Import dive information from a file in
|
||
in a <em>Subsurface</em>-compatible format.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Companion"><em>Import GPS data from Subsurface Service</em></a> - Load GPS
|
||
coordinates from the <em>Subsurface</em> mobile phone app.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ImportingDivelogsDe"><em>Import from Divelogs.de</em></a> - Import dive information
|
||
from <em>www.Divelogs.de</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_log">12.3. Log</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_EnterData"><em>Add Dive</em></a> - Manually add a new dive to the <strong>Dive List</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_DivePlanner"><em>Plan Dive</em></a> - This feature allows the planning of dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Replan"><em>Re-plan dive</em></a> - Edit a dive plan that has been saved into the <strong>Dive List</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_CopyComponents"><em>Copy dive components</em></a> - By selecting this option, one can copy information
|
||
from several fields of a dive log onto the clipboard.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Paste dive components</em> - Paste, into the selected dives in the <strong>Dive List</strong>,
|
||
the information copied using the <em>Copy dive components</em> option.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Renumber"><em>Renumber</em></a> - Renumber the dives listed in the <strong>Dive List</strong>
|
||
panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Group"><em>Auto Group</em></a> - Group the dives in the <strong>Dive List</strong> panel into dive
|
||
trips.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_DeviceNames"><em>Edit Device Names</em></a> - Edit the names of dive computers to facilitate your logs.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_view">12.4. View</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>All</em></a> - View the four main <em>Subsurface</em> panels
|
||
simmultaneously.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Dive List</em></a> - View only the <strong>Dive List</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Profile</em></a> - View only the <strong>Dive Profile</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Info</em></a> - View only the <strong>Dive Notes</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Globe</em></a> - View only the <strong>World Map</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Yearly Statistics</em> - Display summary statistics about dives during this and past
|
||
years.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Prev DC</em> - Switch to next dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Next DC</em> - Switch to previous dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Full Screen</em> - Toggles Full Screen mode.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_filter">12.5. Filter</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Select Events</em> - This option is not implemented yet.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_help">12.6. Help</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>About Subsurface</em> - Show a panel with the version number of <em>Subsurface</em> as
|
||
well as licensing information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Check for updates</em> - Find out whether a newer version of Subsurface is available
|
||
on the <a href="http://subsurface.hohndel.org/"><em>Subsurface</em> web site</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>User Manual</em> - Open a window showing this user manual.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">13. APPENDIX A: Operating system specific information for importing dive information from a dive computer.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_make_sure_that_the_os_has_the_required_drivers_installed">13.1. Make sure that the OS has the required drivers installed</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/drivers.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">The operating system of the desktop computer needs the appropriate drivers in
|
||
order to communicate with the dive computer in whichever way the dive
|
||
computer prefers (e.g. bluetooth, USB, infra-red).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
On Linux users need to have the correct kernel
|
||
module loaded. Most distributions will do this automatically, so the
|
||
user does not need to load kernel modules. However, some communication
|
||
protocols require an additional driver, especially for rarely used
|
||
technology such as infra-red.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
On Windows, the OS should offer to download the correct
|
||
driver once the user connects the dive computer to the USB port and
|
||
operating system sees the equipment for the first time.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
On a Mac users sometimes have to manually hunt for the correct
|
||
driver. For example the correct driver for the Mares Puck
|
||
devices or any other dive computer using a USB-to-serial interface
|
||
based on the Silicon Labs CP2101 or similar chip can be found as
|
||
<em>Mac_OSX_VCP_Driver.zip</em> at the
|
||
<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">Silicon Labs document and software repository</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_HowFindDeviceName">13.2. How to Find the Device Name for USB devices and set its write permission</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/usb.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">When a user connects the dive computer by using a USB connector, usually
|
||
<em>Subsurface</em> will either propose a drop down list that contains the
|
||
correct device name (or mount point for the Uemis Zurich), or it will
|
||
disable the device select drop down if no device name is needed at
|
||
all. In the rare cases where this doesn’t work, here are some
|
||
suggestions of ways to find out what the device name is:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><div class="title">On Windows:</div><p>Simply try COM1, COM2, etc. The drop down list should contain all connected COM
|
||
devices.</p></div>
|
||
<div class="paragraph"><div class="title">On MacOS:</div><p>The drop down box should find all connected dive computers.</p></div>
|
||
<div class="paragraph"><div class="title">On Linux:</div><p>There is a definitive way to find the port:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Disconnect the USB cable from the dive computer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Open a terminal
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Type the command: <em>dmesg</em> and press enter
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Plug in the USB cable of the dive computer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Type the command: <em>dmesg</em> and press enter
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>A message similar to this one should appear:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>usb 2-1.1: new full speed USB device number 14 using ehci_hcd
|
||
usbcore: registered new interface driver usbserial
|
||
USB Serial support registered for generic
|
||
usbcore: registered new interface driver usbserial_generic
|
||
usbserial: USB Serial Driver core
|
||
USB Serial support registered for FTDI USB Serial Device
|
||
ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected
|
||
usb 2-1.1: Detected FT232BM
|
||
usb 2-1.1: Number of endpoints 2
|
||
usb 2-1.1: Endpoint 1 MaxPacketSize 64
|
||
usb 2-1.1: Endpoint 2 MaxPacketSize 64
|
||
usb 2-1.1: Setting MaxPacketSize 64
|
||
usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3
|
||
usbcore: registered new interface driver ftdi_sio
|
||
ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>The third line from the bottom shows that the FTDI USB adapter is
|
||
detected and connected to <code>ttyUSB3</code>. This information can now be used in
|
||
the import settings as <code>/dev/ttyUSB3</code> which directs Subsurface to the correct
|
||
USB port.</p></div>
|
||
<div class="paragraph"><p>Ensuring that the user has write permission to the USB serial port:</p></div>
|
||
<div class="paragraph"><p>On Unix-like operating systems the USB ports can only be accessed by users who
|
||
are members
|
||
of the <code>dialout</code> group. If one is not root, one may not be a member of
|
||
that group and
|
||
will not be able to use the USB port. Let us assume one’s username is <em>johnB</em>.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
As root, type: <code>usermod -a -G dialout johnB</code> (Ubuntu users: <code>sudo usermod
|
||
-a -G dialout johnB</code>)
|
||
This makes johnB a member of the <code>dialout</code> group.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Type: <code>id johnB</code> This lists all the groups that johnB belongs to and
|
||
verifies that
|
||
the appropriate group membership has been created. The <code>dialout</code> group should
|
||
be listed
|
||
among the different IDs.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>With the appropriate device name (e.g. <code>dev/ttyUSB3</code>) and with write permission
|
||
to the USB
|
||
port, the dive computer interface can connect and one should be able to import
|
||
dives.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_HowFindBluetoothDeviceName">13.3. Setting up bluetooth enabled devices</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/bluetooth.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">For dive computers communicating through bluetooth like the Heinrichs
|
||
Weikamp Frog or the Shearwater Predator and Petrel there is a
|
||
different procedure to get the devices name to communicate with
|
||
<em>Subsurface</em>. Follow these steps:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.</strong>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>For Bluetooth pairing of the dive computer, refer to the
|
||
manufacturer’s user guide. When using a Shearwater Predator/Petrel, select
|
||
<em>Dive Log → Upload Log</em> and wait for the <em>Wait PC</em> message.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Pair the <em>Subsurface</em> computer with the dive computer.</strong>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><div class="title">On Windows:</div><p>Bluetooth is most likely already enabled. For pairing with the dive computer choose
|
||
<em>Control Panel→Bluetooth Devices→Add Wireless Device</em>.
|
||
This should bring up a dialog showing your dive computer (in Bluetooth mode) and
|
||
allowing pairing. Right click on it and choose <em>Properties→COM
|
||
Ports</em> to identify the port used for your dive computer. If there are several
|
||
ports listed, use the one saying "Outgoing" instead of "Incoming".</p></div>
|
||
<div class="paragraph"><p>For downloading to <em>Subsurface</em>, the <em>Subsurface</em> drop-down list should contain
|
||
this COM port already. If not, enter it manually.</p></div>
|
||
<div class="paragraph"><p>Note: If there are issues afterwards when downloading from the dive computer using
|
||
other software, remove the existing pairing with the dive computer.</p></div>
|
||
<div class="paragraph"><div class="title">On MacOS:</div><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up
|
||
Bluetooth Device…</em>. The dive computer should then show up in the list of devices. Select it and go
|
||
through the pairing process. This step should only be needed once for
|
||
initial setup.</p></div>
|
||
<div class="paragraph"><p>Once the pairing is completed the correct device is shown in the
|
||
<em>Device or Mount Point</em> drop-down in the <em>Subsurface</em> <strong>Import</strong> dialog.</p></div>
|
||
<div class="paragraph"><div class="title">On Linux</div><p>Ensure Bluetooth is enabled on the <em>Subsurface</em> computer.
|
||
On most common distributions this should be true out of the box and
|
||
pairing should be straight forward. For instance, Gnome3 shows a
|
||
Bluetooth icon in the upper right corner of the desktop where one selects <em>Set
|
||
up New Device</em>. This should show a dialog where one can select the
|
||
dive computer (which already should be in Bluetooth mode) and pair it.
|
||
If a PIN is required, try manually setting <em>0000</em>.</p></div>
|
||
<div class="paragraph"><p>In the rare cases where the above is not true, then
|
||
depending on your system, try <code>initd</code> or <code>systemd</code>. This might be different
|
||
and also involve loading modules specific to your hardware. In case your system
|
||
is running <code>systemd</code>, manually run <code>systemctl start bluetooth.service</code> to
|
||
enable it, in case of <code>initd</code>, run something like <code>rc.config start bluetoothd</code> or
|
||
<code>/etc/init.d/bluetooth start</code>.</p></div>
|
||
<div class="paragraph"><p>One may also use a manual approach by using such commands:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<code>hciconfig</code> shows the Bluetooth devices available on your
|
||
computer (not dive computer), most likely one will see a hci0, if not
|
||
try <code>hcitool -a</code> to see inactive devices and run <code>sudo
|
||
hciconfig hci0 up</code> to bring them up.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<code>hcitool scanning</code> gets a list of bluetooth enabled
|
||
client devices, look for the dive computer and remember the MAC
|
||
address are shown there
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<code>bluez-simple-agent hci0 10:00:E8:C4:BE:C4</code> pairs
|
||
the dive computer with the bluetooth stack of the <em>Subsurface</em> computer, copy/paste
|
||
the MAC address from the output of <em>hcitool scanning</em>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Unfortunately on Linux binding to a communication device has to be done
|
||
manually by running:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<code>rfcomm bind /dev/rfcomm0 10:00:E8:C4:BE:C4</code> binds the dive
|
||
computer to a communication device in the desktop computer, in case rfcomm is
|
||
already taken use rfcomm1 or up. IMPORTANT: Copy/paste the MAC address
|
||
from the output of <code>hcitool scanning</code>, the MAC address shown above will not
|
||
work.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>For downloading dives in <em>Subsurface</em> specify the device name connected to the MAC
|
||
address in the last step above, e.g. <em>/dev/rfcomm0</em>.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">14. APPENDIX B: Dive Computer specific information for importing dive information.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_ImportUemis">14.1. Import from a Uemis Zurich</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/iumis.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content"><em>Subsurface</em> downloads the information
|
||
stored on the SDA (the built-in file system of the Uemis) including
|
||
information about dive spots and
|
||
equipment. Buddy information is not yet downloadable.
|
||
Things are very similar to a normal USB-connected dive computer
|
||
(the Uemis is one of those that recharge when connected to the USB port).
|
||
The main difference is that one does not enter a
|
||
device name, but instead the location where the UEMISSDA file system is
|
||
mounted once connected to the dive computer. On Windows this is a drive letter (
|
||
often <em>E:</em> or <em>F:</em>), on a Mac this is
|
||
<em>/Volumes/UEMISSDA</em> and on Linux systems this differs depending on the
|
||
distribution. On Fedora it usually is
|
||
<em>/var/run/media/<your_username>/UEMISSDA</em>. In all cases <em>Subsurface</em>
|
||
should suggest the correct location in the drop down list.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>After selecting the above device name, download the
|
||
dives from the Uemis Zurich. One technical issue with the Uemis Zurich
|
||
download implementation (this is a Uemis firmware limitation, not a
|
||
<em>Subsurface</em> issue) is that one cannot download more than about 40-50
|
||
dives without running out of memory on the SDA. This will usually only
|
||
happen the very first time one downloads dives from the Uemis Zurich.
|
||
Normally when downloading at the end of a day or even after a dive
|
||
trip, the capacity is sufficient. If <em>Subsurface</em> displays an error
|
||
that the dive computer ran out of space the solution is straight
|
||
forward. Disconnect the SDA, turn it off and on again, and reconnect
|
||
it. You can now retry (or start a new download session) and the
|
||
download will continue where it stopped previously. One
|
||
may have to do this more than once, depending on how many dives are
|
||
stored on the dive computer.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportingGalileo">14.2. Importing dives from the Uwatec Galileo</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/Galileo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">The Uwatec Galileo dive computers use infra red (IrDA) communication
|
||
between the dive computer and Subsurface. The Uwatec hardware uses
|
||
a USB dongle based on the serial infra-red (SIR) protocol and the
|
||
MSC7780 IrDA controller manufactured by MosChip
|
||
and marketed by Scubapro and some electronics companies.
|
||
Under Linux, the kernel
|
||
already provides for communication using the IrDA protocol. However,
|
||
the user additionally needs to load a driver for the IrDA interface
|
||
with the dive computer. The easiest way is to load the <strong>irda-tools</strong>
|
||
package from the <a href="http://irda.sourceforge.net/docs/startirda.html">Linux IrDA Project</a>.
|
||
After the installation of the irda-tools, the <strong>root user</strong> can specify a device name
|
||
from the console as follows:
|
||
<code>irattach irda0</code></td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>After executing this command, Subsurface will recognise the Galileo
|
||
dive computer and download dive information.</p></div>
|
||
<div class="paragraph"><p>Under Windows, a similar situation exists. Drivers for the MCS7780 are
|
||
available from some Internet web sites e.g.
|
||
<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>.</p></div>
|
||
<div class="paragraph"><p>For the Apple Mac, IrDA communication via the MCS7780 link is not
|
||
available for OSX 10.6 or higher.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportingDR5">14.3. Importing dives from Heinrichs Weikamp DR5</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/HW_DR5.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">When mounted as a USB drive the Heinrichs Weikamp DR5 saves a single UDDF file
|
||
for every dive.
|
||
Mark all the dives you’d like to import or open.
|
||
Note: The DR5 does not seem to store gradient factors nor deco information, so
|
||
for <em>Subsurface</em> it is not possible to display them. Adjust the gradient
|
||
factors in the <em>Graph Settings</em> in <em>Subsurface</em> to generate a deco overlay in the
|
||
<em>Subsurface</em> <strong>Dive Profile</strong> panel but please note that the deco calculated by
|
||
<em>Subsurface</em> will most likely differ from the one displayed on the DR5.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_import_from_shearwater_predator_using_bluetooth">14.4. Import from Shearwater Predator using Bluetooth</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/predator.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Using a Shearwater Predator one may be able to pair Bluetooth but then encounter
|
||
issues when downloading, showing errors like <em>Slip RX: unexp. SLIP END</em> on the
|
||
Predator.
|
||
This might also arise when using other dive log software and operating
|
||
systems other than Linux. We have no detailed idea about the source and how to fix
|
||
this, but it is reported to be solved sometimes by one of these steps:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
use the Bluetooth dongle which came with the Shearwater Predator instead of
|
||
the built-in one of the <em>Subsurface</em> computer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
switch to different Bluetooth drivers for the same hardware
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
switch off WiFi while using Bluetooth
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_PoseidonMkVI">14.5. Importing dive logs from the Poseidon MkVI Discovery</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/MkVI.jpeg" alt="Note" />
|
||
</td>
|
||
<td class="content">Download of dive logs from the MkVI is performed using a custom communications
|
||
adapter and the <em>Poseidon PC Configuration Software</em>, obtained when purchasing
|
||
the MKVI equipment. The latter is a Windows application allowing configuration
|
||
of equipment and storage of dive logs. Communication between dive computer and
|
||
desktop computer utilises the IrDA infra-red protocol. Only data for one dive
|
||
can be downloaded at a time, comprising three files:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Setup configuration for the dive and key dive parameters (file with a .txt
|
||
extension)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Dive log details (file with a .csv extension)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Redbook format dive log (file with .cvsr extension). This is a compressed
|
||
version of the dive log using a propriatary format.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> accesses the .txt and the .csv files to obtain dive log information.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importing_dive_logs_from_the_apd_inspiration_ccr">14.6. Importing dive logs from the APD Inspiration CCR</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/APDComputer.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">The dive logs of an APD Inspiration or similar CCR dive computer are downloaded using
|
||
a communications adapter and <em>AP Communicator</em>, obtained when
|
||
purchasing the equipment. The dive logs can be viewed using the <em>AP Log Viewer</em>,
|
||
within Windows or Mac/OS. However, APD logs can be viewed and managed from within
|
||
<em>Subsurface</em> (together with dives using many other types of dive computer). The
|
||
APD inspiration dive logs are imported into <em>Subsurface</em> as follows:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Open a dive within the <em>AP Log Viewer</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select the tab at the top of the screen, entitled "<em>Data</em>".
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If the raw dive log data show on the screen, click on "<em>Copy to Clipboard</em>".
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Open a text editor, e.g. Notepad (Windows), TextWrangler (Mac).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Copy the contents of the clipboard into the text editor and save the text file
|
||
with a filename extension of .CSV
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Within <em>Subsurface</em>, select <em>Import→Import log files</em> to open the <a href="#Unified_import">universal import dialogue</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the dropdown list towards the bottom right of the dialogue, select "<em>CSV files</em>".
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
On the list of file names select the .CSV file that has been created above. An import
|
||
dialogue opens.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the dropdown list on the middle right labeled '<em>Pre-configured imports</em>",
|
||
select <em>APD Log Viewer</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ensure the other settings for the ADP dive log are appropriate, then select <em>OK</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">15. APPENDIX C: Exporting Dive log information from external dive log software.</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>The import of dive log data from external dive log software is mostly performed
|
||
using
|
||
the dialogue found by selecting <em>Import</em> from the Main Menu, then clicking on
|
||
<em>Import Log Files</em>. This is a single-step process, more information about which
|
||
can be found
|
||
<a href="#Unified_import">here.</a>
|
||
However, in some cases, a two-step process may be required:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Export the foreign dive log data to format that is accessible from
|
||
<em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Import the accessible dive log data into <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>This appendix provides some information about approaches to export dive log
|
||
data from foreign
|
||
dive log software. The procedures below mostly apply to Linux and/or Windows.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportingDivesSuunto">15.1. Exporting dives from <strong>Suunto Divemanager (DM3 and DM4)</strong></h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/suuntologo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Divemanager 3 (DM3) is an older version of the Suunto software. More recent
|
||
Suunto dive computers use Divemanager 4 (DM4). The
|
||
two versions of Divemanager use different methods and different file naming
|
||
conventions to export dive log data.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Start <em>Suunto Divemanager 3</em> and log in with the name containing the logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do not start the import wizard to import dives from the dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the navigation tree on the left side of the program-window, select the appropriate
|
||
dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Within the list of dives, select the dives you would like to import later:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
To select certain dives: hold <em>ctrl</em> and click the dive
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
To select all dives: Select the first dive, hold down shift and
|
||
select the
|
||
last dive
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
With the dives marked, use the program menu <em>File → Export</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The export pop-up will show. Within this pop-up, there is one field called <em>Export Path</em>.
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Click the browse button next to the field Export Path
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
A file-manager like window pops up
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Navigate to the directory for storing the
|
||
Divelog.SDE file
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Optionally change the name of the file for saving
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Save</em>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Back in the Export pop-up, press the button <em>Export</em>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The dives are now exported to the file Divelog.SDE.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p><strong>Divemanager 4 (DM4):</strong></p></div>
|
||
<div class="paragraph"><p>To export divelog from <em>Suunto DM4</em>, one needs to locate the DM4 database
|
||
where the dives are stored. the user can either look for the original
|
||
database or make a backup of the dives. Both methods are described here.</p></div>
|
||
<div class="paragraph"><p>Locating the Suunto DM4 database:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Start Suunto DM4
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select <em>Help → About</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Copy</em> after text <em>Copy log folder path to clipboard</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Now open Windows Explorer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Paste the address to the path box at the top of the File Explorer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The database is called DM4.db
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Backing up Suunto DM4:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Start Suunto DM4
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select <em>File - Create backup</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
From the file menu select the location and name for the backup, we’ll
|
||
use DM4 in here with the default extension .bak
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Save</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The dives are now exported to the file DM4.bak
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_exporting_from_mares_dive_organiser_v2_1">15.2. Exporting from Mares Dive Organiser V2.1</h3>
|
||
<div class="admonitionblock" id="Mares_Export">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/mareslogo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Mares Dive Organiser is a Windows application. The dive log is kept as a
|
||
Microsoft SQL Compact Edition database with a <em>.sdf</em> filename extension. The
|
||
database includes all Dive Organiser-registered divers on the particular
|
||
computer and all Mares dive computers used. The safest way to obtain a copy
|
||
of the dive database is to export the information to another compatible format
|
||
which can be imported into <em>Subsurface</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Within Dive Organiser, select
|
||
<em>Database → Backup</em> from the main menu and back up the database to the desk
|
||
top.
|
||
This creates a zipped file DiveOrganiserxxxxx.dbf.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Rename the file to
|
||
DiveOrganiserxxxxx.zip. Inside the zipped directory is a file
|
||
<em>DiveOrganiser.sdf</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Extract the <em>.sdf</em> file from the zipped folder to your Desktop.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The password for accessing the .zip file is <em>mares</em>.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportingDivinglog">15.3. Exporting dives from <strong>DivingLog 5.0</strong></h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/divingloglogo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Unfortunately DivingLog XML files give us no
|
||
indication on the preferences set on one’s system. So in order for
|
||
<em>Subsurface</em> to be able to successfully import XML files from DivingLog
|
||
one first needs to ensure that DivingLog is configured
|
||
to use the Metric system (one can easily change this within Diving Log by
|
||
selecting <em>File → Preferences → Units and Language</em> by clicking the <em>Metric</em>
|
||
button). Then do the following:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
In Divinglog open the <em>File → Export → XML</em> menu
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select the dives to export
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click on the export button and select the filename
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_d_faqs">16. APPENDIX D: FAQs.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_subsurface_appears_to_miscalculate_gas_consumption_and_sac">16.1. Subsurface appears to miscalculate gas consumption and SAC</h3>
|
||
<div class="paragraph" id="SAC_CALCULATION"><p><em>Question</em>: I dived with a 12.2 l tank, starting with 220 bar and ending with 100 bar, and I calculate a different SAC compared what <em>Subsurface</em> calculates. Is <em>Subsurface</em>
|
||
miscalculating?</p></div>
|
||
<div class="paragraph"><p><em>Answer</em>: Not really. What happens is that <em>Subsurface</em> actually calculates gas
|
||
consumption differently - and better - than you expect.
|
||
In particular, it takes the incompressibility of the gas into account.
|
||
Traditionally, Gas consumption and SAC should be:
|
||
<code>consumption = tank size x (start pressure - end pressure)</code></p></div>
|
||
<div class="paragraph"><p>and that’s true for an ideal gas, and it’s what you get taught in dive theory.
|
||
But an "ideal gas" doesn’t actually exist, and real gases actually don’t compress
|
||
linearly with pressure. Also, you are missing the fact that one atmosphere of
|
||
pressure isn’t actually one bar.
|
||
So the <strong>real</strong> calculation is:</p></div>
|
||
<div class="paragraph"><p><code>consumption = (amount_of_air_at_beginning - amount_of_air_at_end)</code></p></div>
|
||
<div class="paragraph"><p>where the amount of air is <strong>not</strong> just "tank size times pressure in bar".
|
||
It’s a combination of: "take compressibility into account" (which is a fairly
|
||
small issue under 220 bar - you’ll see more differences when you do high-pressure
|
||
tanks with 300bar) and "convert bar to atm" (which is the majority of your discrepancy).
|
||
Remember: one ATM is ~1.013 bar, so without the compressibility, your gas use is:</p></div>
|
||
<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div>
|
||
<div class="paragraph"><p>which is about 1445, not 1464. So there was 19 l too much in your simple
|
||
calculation that ignored the difference between 1 bar and one ATM.
|
||
The compressibility does show up above 200 bar, and takes that 1445 down
|
||
about eight litres more, so you really did use only about 1437 l of air at surface pressure.</p></div>
|
||
<div class="paragraph"><p>So be happy: your SAC really is better than your calculations indicated.
|
||
Or be sad: your cylinder contains less air than you thought it did.
|
||
And as mentioned, the "contains less air than you thought it did" really
|
||
starts becoming much more noticeable at high pressure. A 400 bar really does not
|
||
contain twice as much air as a 200 bar one. At lower pressures, air acts pretty much like an ideal gas.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_some_dive_profiles_have_time_discrepancies_with_the_recorded_samples_from_my_dive_computer_8230">16.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer…</h3>
|
||
<div class="paragraph"><p><em>Subsurface</em> ends up ignoring surface time for many things (average depth, divetime, SAC, etc).
|
||
<em>Question</em>: Why do dive durations in my dive computer differ from that given by <em>Subsurface</em>?</p></div>
|
||
<div class="paragraph"><p><em>Answer</em>: For example, if you end up doing a weight check (deep enough to trigger the "dive started")
|
||
but then come back up and wait five minutes for your buddies, your dive computer may say
|
||
that your dive is 50 minutes long - because you have fifty minutes worth of samples - but
|
||
subsurface will say it’s 45 minutes - because you were actually diving for 45 minutes.
|
||
It’s even more noticeable if you do things like divemastering the initial OW dives, when
|
||
you may stay in the water for a long time, but spend most of it at the surface. And then
|
||
you don’t want that to count as some kind of long dive”.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div id="footnotes"><hr /></div>
|
||
<div id="footer">
|
||
<div id="footer-text">
|
||
Last updated 2014-11-17 09:10:46 GMT
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html>
|