mirror of
https://github.com/subsurface/subsurface.git
synced 2024-11-30 22:20:21 +00:00
6589 lines
316 KiB
Text
6589 lines
316 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.9" />
|
||
<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.jpg" 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, Pedro Neves</p></div>
|
||
<div class="paragraph"><p><span class="blue"><em>Version 4.5, October 2015</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 need a flexible way of logging dives using recreational equipment,
|
||
even not using a dive computer?
|
||
</p>
|
||
</li>
|
||
<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 or recreational equipment? 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 using 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
|
||
downloading and analysing your dive logs on other operating systems.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do you need an intuitive graphical dive planner that integrates with and takes
|
||
into account the dives that have already been logged?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do you need a way of storing or backing up your dive log on the Internet, allowing
|
||
you to view your dive log from anywhere, using an Internet browser?
|
||
</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-divelog.org/"><em>Subsurface</em> web site</a>.
|
||
Please discuss issues with this program by sending an email to
|
||
<a href="mailto:subsurface@subsurface-divelog.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. Using this manual</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>When opened from within <em>Subsurface</em>, this manual does not have external controls. However,
|
||
a <em>SEARCH</em> function is important. This is activated by pressing control-F or command-F on
|
||
the keyboard. A text box appears at the bottom of the window. Use this to search for
|
||
any term in the manual.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_the_user_survey">2. 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">3. 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 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>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 single 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
|
||
several dives are selected, 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>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_f22.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 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">4. 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">5. Storing dive information in the logbook</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Now that a new logbook was created, it is simple to add dive data to it.
|
||
<em>Subsurface</em> allows several ways of adding dive data to a logbook, detailed
|
||
in the following sections.</p></div>
|
||
<div class="paragraph"><p>1) If the user has a handwritten divelog, a spreadsheet or another form of
|
||
manually maintained divelog, dive data can be added to the logbook using
|
||
one of these approaches:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Enter dive information by hand. This is useful if the diver did not
|
||
use a dive computer and dives were recorded in a written logbook. See:
|
||
<a href="#S_EnterData">Entering dive information by hand</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Import dive log information that has been maintained either as a spreadsheet
|
||
or as a CSV file. Refer to: <a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet to CSV format</a> and
|
||
to <a href="#S_ImportingCSVDives">Importing dives in CSV format</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>2) If one has dives recorded using a dive computer, the depth profile of the
|
||
dive and a large amount of additional information can be accessed. These dives
|
||
can be imported from:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The dive computer itself. See: <a href="#S_ImportDiveComputer">Importing new dive information from a Dive Computer</a> or
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Proprietary software distributed by manufacturers of dive computers. Refer
|
||
to: <a href="#S_ImportingAlienDiveLogs">Importing dive information from other digital data sources or other data formats</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Import from spreadsheet or CSV files containing dive profiles.
|
||
See: <a href="#S_ImportingCSVDives">Importing dives in CSV format from dive computers or other dive log software</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect2">
|
||
<h3 id="S_EnterData">5.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>Info</strong> panel (<strong>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_f22.jpg" alt="FIGURE: Add dive" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>When one edits a field in 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 <strong>Notes</strong> panel (see the image below). This message is
|
||
displayed in all the panels under Notes and Equipment when in <strong>Editing Mode</strong>.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/BlueEditBar_f22.jpg" alt="Blue edit bar" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The <em>Apply changes</em> button should only be selected after all the parts of a dive have been entered.
|
||
When entering dives by hand, the <em>Info</em>, <em>Equipment</em> and <em>Profile</em> tabs should be completed
|
||
before saving the information. By selecting the <em>Apply changes</em> button, a local copy of the information
|
||
for this specific dive is saved in memory. When one closes Subsurface, the program will
|
||
ask again, this time whether the complete dive log should be saved on disk or not.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="S_CreateProfile">5.1.1. 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_f20.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 right-angled red lines as shown below.
|
||
The time and depth
|
||
represented by the cursor 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. Drag the waypoints to represent an
|
||
accurate
|
||
time duration for the dive. Below is a dive profile for 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_f20.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 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 (see image below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DiveProfile3_f20.jpg" alt="FIGURE: Gas composition context menu" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>With the profile having been defined, more details must be added in order to have
|
||
a fuller record of the dive. To do this,
|
||
the <strong>Notes</strong> and the <strong>Equipment</strong> tabs on the top left hand of the
|
||
<em>Subsurface</em> window should be used. Click on
|
||
<a href="#S_Notes_dc"><strong>this link</strong></a> for instructions to use these tabs.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportDiveComputer">5.2. Importing new dive information from a Dive Computer</h3>
|
||
<div class="sect3">
|
||
<h4 id="_connecting_and_importing_data_from_a_dive_computer">5.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-divelog.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.
|
||
(Refer to the manual of the specific dive computer)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In <em>Subsurface</em>, from the Main Menu, 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/DC_import_f20.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, if
|
||
the dive computer allows this,
|
||
<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).</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 dive in the <em>Subsurface</em> divelog will be overwritten
|
||
by the dive record from the dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The checkbox marked <em>Download into new trip</em> ensures that, after upload, the downloaded dives
|
||
are grouped together as a new trip(s) in the <strong>Dive List</strong>.
|
||
</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>
|
||
Then select the <em>Download</em> button.
|
||
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. 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). After successful download, Dialogue <strong>B</strong>
|
||
in the figure above appears.
|
||
After the dives have been downloaded, they appear in a tabular format on the right-hand
|
||
side of the dialogue (see image <strong>B</strong>, above). Each dive comprises a row in the table, with the date, duration
|
||
and depth shown. Next to each dive is a checkbox: check all the dives that need to
|
||
be transferred to the <strong>Dive List</strong>. In the case of the image above, the last six dives are
|
||
checked and will be transferred to the <strong>Dive List</strong>. Then
|
||
click the <em>OK</em> button at the bottom of the dialogue. 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.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>After this has been completed, select the OK button.
|
||
The checked dives are transferred to the <strong>Dive List</strong>.</p></div>
|
||
<div class="ulist"><ul>
|
||
<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@subsurface-divelog.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_Bluetooth">5.2.2. Connecting <em>Subsurface</em> to a Bluetooth-enabled dive computer</h4>
|
||
<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive computers
|
||
and <em>Subsurface</em>, for instance, the Shearwater Petrel
|
||
Mk2 and the OSTC Mk3. <em>Subsurface</em> provides a largely operating system independent
|
||
Bluetooth interface. Setting up <em>Subsurface</em> for Bluetooth communication requires
|
||
four steps:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Ensure that Bluetooth is activated on the host computer running <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ensure that <em>Subsurface</em> sees the Bluetooth adapter on the host computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in PC upload mode.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ensure that <em>Subsurface</em> is paired with the Bluetooth-enabled dive computer.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Select the Download dialogue by selecting
|
||
<em>Import → Import from dive computer</em> from the <strong>Main Menu</strong>. If one checks the
|
||
check box labelled <em>"Choose Bluetooth download mode"</em>, the dialogue below appears.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="_on_linux_or_macos">On Linux or MacOS:</h5>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DC_import_Bluetooth.jpg" alt="FIGURE: Download Bluetooth" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>On the <em>Linux</em> or <em>MacOS</em> platforms the name
|
||
of the <em>Subsurface</em> computer and its Bluetooth address are shown on the right-hand side, On the lefthand side, if the
|
||
computer has connected more than one local Bluetooth devices the user can use
|
||
the list box to indicate which one needs to connect to <em>Subsurface</em>.
|
||
The power state (on/off) of the Bluetooth adapter is shown below
|
||
the address and can be changed by checking the <em>Turn on/off</em> check box.</p></div>
|
||
<div class="paragraph"><p>If the Bluetooth address is not shown, then <em>Subsurface</em> does not see the local
|
||
Bluetooth device. Ensure that the Bluetooth driver is installed correctly on the
|
||
<em>Subsurface</em> computer and check if it can be used by other Bluetooth utilities like
|
||
<em>bluetoothctl</em> or <em>bluemoon</em>. This achieves the first two steps above.</p></div>
|
||
<div class="paragraph"><p>Ensure that the Bluetooth-enabled dive computer is in PC-upload mode and that it
|
||
is discoverable by other Bluetooth devices. Consult the manual of the dive
|
||
computer to perform this. Now the third item in the list above has been achieved.</p></div>
|
||
<div class="paragraph"><p>Select the <em>Scan</em> button towards the bottom left of the dialogue above. After
|
||
searching for a small amount of time, the dive computer should be listed
|
||
(perhaps as one of a number of Bluetooth devices) in the main list box on the
|
||
lefthand side of the dialogue (see image above). If this is not achieved, select
|
||
the <em>Clear</em> button and then scan again for Bluetooth devices using the <em>Scan</em>
|
||
button. After performing these actions <em>Subsurface</em> should see the dive computer.
|
||
The label of the discovered dive computer contains the name of the device, its
|
||
address and its pairing status. If the device is not paired and has a red
|
||
background colour, a context menu can be opened by selecting the item with a
|
||
right-click.
|
||
Select the the <em>Pair</em> option and wait for the task to complete.</p></div>
|
||
<div class="sidebarblock">
|
||
<div class="content">
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Currently <em>Subsurface</em> does not support Bluetooth pairing with dive
|
||
computers that require a custom PIN code. In order to pair the devices, use other
|
||
OS utilities as suggested below.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>One way to achieve this is to use <code>bluetoothctl</code>:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>$ bluetoothctl
|
||
[bluetooth]# agent KeyboardOnly
|
||
Agent registered
|
||
[bluetooth]# default-agent
|
||
Default agent request successful
|
||
[bluetooth]# pair 00:80:25:49:6C:E3
|
||
Attempting to pair with 00:80:25:49:6C:E3
|
||
[CHG] Device 00:80:25:49:6C:E3 Connected: yes
|
||
Request PIN code
|
||
[agent] Enter PIN code: 0000</code></pre>
|
||
</div></div>
|
||
</div></div>
|
||
<div class="paragraph"><p>After the devices are paired the <em>Save</em> button of the dialogue can be pressed.
|
||
This closes the Bluetooth dialogue. Now select <em>Download</em> in the <em>Download from
|
||
dive computer</em> dialogue which should still be open. The downloaded dives are
|
||
shown on the righthand side of the download dialogue.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_on_windows">On Windows:</h5>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Download Bluetooth on Windows" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>On <em>Windows</em> platforms the <em>Local Bluetooth device details section</em> on the right is not displayed.
|
||
To successfully initiate a scan (by pressing the <em>Scan</em> button)
|
||
check that the Bluetooth device on the <em>Subsurface</em> computer is turned on.</p></div>
|
||
<div class="paragraph"><p>The pairing step is checked and done automatically during
|
||
the download process. If the devices have never been paired the system will ask
|
||
for your permissions and put a message on the right side of the screen: <em>Add a
|
||
device, Tap to set up your DC device</em>. Always allow this pairing. After a
|
||
discovered item is selected, select the <em>Save</em> button.
|
||
Finally select the <em>Download</em> button on the <em>Download</em> dialogue and wait for the process to complete.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Be aware that currently <em>Subsurface</em> works only with local Bluetooth
|
||
adapters which use Microsoft Bluetooth Stack. If the local device uses
|
||
<em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> or <em>BlueSolei</em> drivers it
|
||
will definitely not work.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>A log messageOn the bottom left of the <em>Remote Bluetooth device selection</em>
|
||
shows details about the current status of the Bluetooth agent. To
|
||
select another dive computer for download using the "Remote Bluetooth selection dialogue"
|
||
press the three-dots button from the <em>"Choose Bluetooth download mode"</em> option.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content"><strong>IN CASE OF PROBLEMS</strong>: If the Bluetooth adapter from the <em>Subsurface</em> computer
|
||
gets stuck and the <em>Download</em> process fails repeatedly,
|
||
<em>unpair</em> the devices and then repeat the above steps. If this is not successful,
|
||
<a href="#S_HowFindBluetoothDeviceName"><em>Appendix A</em></a> contains
|
||
information for manually setting up and inspecting the Bluetooth connection
|
||
with <em>Subsurface</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_DeviceNames">5.2.3. 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, consider 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">5.2.4. Updating the dive information imported from the dive computer.</h4>
|
||
<div class="paragraph"><p>With the uploaded dives in the <strong>Dive List</strong>, 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>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 class="sect4">
|
||
<h5 id="S_Notes_dc">Notes</h5>
|
||
<div class="paragraph"><p>To have a more complete dive record the user needs to add
|
||
additional information by hand. The procedure
|
||
below is virtually identical for hand-entered dives and for dives downloaded from a dive computer.</p></div>
|
||
<div class="paragraph"><p>In some cases,
|
||
one has to provide the date and time of the dive, e.g. when entering a dive by hand or when a
|
||
dive computer does not provide the date and time of the dive.
|
||
(Usually the date and time of the dive, gas mixture and water temperature are
|
||
shown as obtained from the dive computer)
|
||
If the contents of the <strong>Notes tab</strong> 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>Notes</strong> tab, the following fields are
|
||
visible (left hand image, below):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/AddDive3_f22.jpg" alt="FIGURE: The Notes tab" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The right hand image, above, shows a <strong>Notes tab</strong> filled with dive information.
|
||
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 over-typing the
|
||
information displayed.</p></div>
|
||
<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown
|
||
in text boxes to the right of the Start time. Many dive computers supply water
|
||
temperature information and this box may therefore contain information.
|
||
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> (following the <em>Preferences</em>, metric or imperial units will
|
||
be used).</p></div>
|
||
<div class="paragraph"><p><strong>Location</strong>:</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Dive locations are managed as a <strong>separate</strong> part of the dive log.
|
||
The dive information in the <strong>Notes</strong> and <strong>Equipment</strong> tabs can therefore not be edited at the same
|
||
time as the dive site information. Save all the other dive information (e.g.
|
||
divemaster, buddy, protective gear, notes about the dive) by selecting <em>Apply changes</em> on the
|
||
<strong>Notes</strong> tab before editing the dive site information. Only then, supply a dive site name in the
|
||
textbox labelled <em>Location</em> on the <strong>Notes</strong> tab.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>Type the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary".
|
||
If several dives are
|
||
performed at the same location, the dive site information for the first dive is re-used.
|
||
Existing dive location information
|
||
can be edited at any time by selecting (on the <strong>Dive List</strong> panel) a dive performed at that site
|
||
and by opening the location information by clicking the globe button on the
|
||
right of the location name (see image on the right, above). When entering a dive location name, auto location of
|
||
dive site names makes it easy to select an existing dive site name
|
||
(i.e. when typing the name of a dive site,
|
||
a dropdown list appears showing all sites with similar names). If the dive
|
||
site has been used before, click on the already-existing name.
|
||
The dive site names in the dropdown list contain either a globe symbol (indicating
|
||
existing dive sites in the <em>Subsurface</em> database)
|
||
or a <strong>+</strong> symbol (indicating dive site names that appear consistent with the
|
||
current dive site name but which have not been added to the dive site database).
|
||
Therefore, if the present
|
||
dive site has not been used before, a message appears as follows (image <strong>A</strong> below):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Locations1_f22.jpg" alt="FIGURE:Location description panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Doubleclick on the new dive site name. A panel appears to enter the coordinates and
|
||
other important information about the site (image <strong>B</strong>, above). The most important
|
||
items are the coordinates of the site. There are three ways of specifying the coordinates:</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 <em>Subsurface</em> window. The map displays an orange bar indicating "No location
|
||
data - Move the map and double-click to set the dive location". Upon a doubleclick
|
||
at the appropriate place, the orange 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 or iPhone 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. Some keyboards
|
||
don’t have the degree sign (°). It can be replaced by a <strong>d</strong> like this: N30d W20d.
|
||
If both a dive site name and coordinates have been provided, Save the
|
||
dive site information by selecting the button <em>Apply changes</em> at the top of
|
||
the panel.</p></div>
|
||
<div class="paragraph"><p><strong>Important</strong>: GPS coordinates of a dive site are linked to the Location
|
||
name - so <strong>saving</strong> a dive site with only coordinates and no dive site name
|
||
causes 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>Dive site name lookup:</strong> If coordinates have been typed into the appropriate
|
||
text box, one can perform an automated name lookup based on the coordinates.
|
||
This is achieved when <em>Subsurface</em> uses the Internet to find the name of the dive site
|
||
based on the coordinates that were typed. If a name has been found, it is
|
||
automatically inserted into the tags box. The list box
|
||
(Titled <em>Dive sites on same coordinates</em>") at the bottom
|
||
of the dive site panel contains the names of other dives sites used at the
|
||
current location. For instance if the dive site is "Blue Hole" and there are several
|
||
dive sites named "Blue Hole", all these sites are listed in this list box.</p></div>
|
||
<div class="paragraph"><p>Enter any other textual information about the dive site (Description and Notes),
|
||
then select <em>Apply Changes</em> to save the geolocation for this dive site. At a later stage
|
||
the dive site information can be edited by clicking the globe icon to the right of the
|
||
dive site name in the <strong>Notes tab</strong>.</p></div>
|
||
<div class="paragraph"><p><strong>Dive mode</strong>: This is a dropdown box allowing one to choose the type of dive
|
||
performed. The options are OC (Open Circuit SCUBA, the default seting, meant for most recreational dives),
|
||
Freedive (dive without SCUBA equipment), CCR (Closed-circuit
|
||
rebreather) and pSCR (Passive semi-closed rebreather).</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 selection 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 selection 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 dive suit used can be entered.
|
||
Auto selection of the suit description is available.
|
||
Some dry-suit users may choose to use this field to record what combination of
|
||
suit and thermal 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 <em>Apply changes</em> and <em>Discard changes</em> buttons are used to save all the information for tabs
|
||
in the <strong>Info</strong> panel and in the <strong>Dive Profile</strong> panel, so there’s no need to use them
|
||
until <strong>ALL</strong> other information has been added. The image <a href="#S_Notes_dc">at the beginning of this section</a>
|
||
shows an example of a <strong>Notes tab</strong> after completion of the dive information.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_equipment">Equipment</h5>
|
||
<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_f22.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 <strong>Dive profile</strong>
|
||
(top right-hand panel).</p></div>
|
||
<div class="paragraph" id="cylinder_definitions"><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_f20.jpg" alt="FIGURE: Initial cylinder dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>For hand-entered dives, this information needs to be typed in. For dive computers,
|
||
<em>Subsurface</em> often obtains the gas used from the dive computer and
|
||
automatically inserts the gas composition(% oxygen or % helium) 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 <em>Type</em> 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_f20.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 (<em>Work.press</em>) will
|
||
automatically be shown in the dialogue.</p></div>
|
||
<div class="paragraph"><p>Next, 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, save the data
|
||
either by pressing <em>ENTER</em> on the keyboard or by clicking outside the cell
|
||
containing
|
||
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_f20.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_f20.jpg" alt="FIGURE:The Weights dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>By clicking on the <em>Type</em> 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_f20.jpg" alt="FIGURE:Weights type drop-down list button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This can be used to select the type of weight system
|
||
used during the dive or the user may start typing in the box
|
||
to specify a different weighting mechanism that will be saved by <em>Subsurface</em>.
|
||
In the <strong>Weight</strong>
|
||
field, type in the amount of weight used during the dive. After
|
||
specifying the weight
|
||
system, save the data by either pressing <em>ENTER</em> on the keyboard or by clicking 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_f20.jpg" alt="FIGURE: A completed weights information table" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_editing_several_selected_dives_simultaneously">5.2.5. 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 each uploaded dive is shown in the <strong>Dive profile</strong> tab, as well
|
||
as a few items of information
|
||
in the <strong>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>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>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>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>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">5.2.6. 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 buoy". 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">5.2.7. Saving the updated dive information</h4>
|
||
<div class="paragraph"><p>The information entered in the <strong>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>Notes</strong> tab. If the <em>Apply changes</em> button
|
||
is clicked,
|
||
the dive data are saved in the memory image of the dive. If the <em>Discard changes</em>
|
||
button is clicked, then the newly entered dive data are
|
||
erased from the computer memory, although the dive profile is
|
||
retained. When the user exits <em>Subsurface</em> there is a final prompt to confirm
|
||
that the new data should now be saved permanently on the computer disk.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importing_dive_information_from_other_digital_data_sources_or_other_data_formats">5.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. a 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. Below follows more specific information
|
||
to achieve data import to <em>Subsurface</em>.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_using_the_universal_import_dialogue">5.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
|
||
activated by selecting <em>Import</em> from the Main Menu, then clicking on
|
||
<em>Import Log Files</em>. This brings up dialogue <strong>A</strong>, below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Import1_f20.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>
|
||
Cochran dive logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
UDDF-formatted dive logs (e.g. Kenozoooid)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
UDCF-formatted dive logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Poseidon MkVI CCR logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
APD Inspiration/Evolution CCR logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
LiquiVision logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
divelog.de logs
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
OSTC Tools 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 format and then the specific log file in the large window
|
||
containing the file list on the right 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_from_ostctools">5.3.2. Importing from OSTCTools</h4>
|
||
<div class="paragraph"><p><em>OSTC Tools</em> is a Microsoft-based suite of dive download and dive management tools for the OSTC
|
||
family of dive computers. <em>OSTC Tools</em> downloads dive data from the dive computer and stores it
|
||
as a binary file with file extension <em>.dive</em> . Subsurface can directly import these files when using
|
||
the universal import dialogue. From the dropdown list at the bottom right select
|
||
<em>OSTCTools Files (.dive .DIVE)</em>. This makes the <em>OSTC Tools</em> dive logs visible in the file list
|
||
panel. Select one or more dive, then click the <em>Open</em> button. The OSTC dives are shown in the
|
||
<strong>Dive List</strong> panel.</p></div>
|
||
<div class="paragraph"><p>Actually, all H&W devices supported by OSTCTools can be imported to <em>Subsurface</em>, this includes
|
||
OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably although untested, Frog, OSTC2 and
|
||
OSTC CR.</p></div>
|
||
<div class="paragraph"><p>Please, remember that OSTCTools is <strong>not</strong> a true diving log software, but a useful set of tools
|
||
for analysis and management of OSTC devices. This way, only raw dive computer data will be
|
||
performed with the import to <em>Subsurface</em>; one has to to manually complete the rest of
|
||
data which may be important (buddies, equipment, notes, etc).</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_importing_from_mares_dive_organiser_v2_1">5.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>
|
||
Export the dive log data from Mares Dive Organiser 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">5.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 from Divelogs.de</em> option should be selected
|
||
from the Main Menu. This
|
||
brings up a dialogue box (see image <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 image <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_ImportingCSVData">5.3.5. Importing data in CSV format</h4>
|
||
<div class="paragraph"><p>A comma-separated file (.csv) can be used to import dive information either as dive profiles
|
||
(as in the case of the APD Inspiration and Evolution closed circuit rebreathers) or as dive
|
||
metadata (in case the user keeps dive data in a spreadsheet). The <em>CSV</em> format is a universal
|
||
simplified format that allows for easy information exchange between different computers or
|
||
software packages. For an introduction to CSV-formatted files see <a href="#S_CSV_Intro">A Diver’s
|
||
Introduction To CSV Files</a>. <em>Subsurface</em> dive logs can also be exported in <em>CSV</em> format to
|
||
other software that reads this format. See <a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet
|
||
to CSV format</a> for information that may be helpful for importing spreadsheet-based data
|
||
into <em>Subsurface</em>.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="S_ImportingCSVDives">Importing dives in CSV format from dive computers or other dive log software</h5>
|
||
<div class="paragraph"><p>One can view a <em>CSV</em> file by using an ordinary text editor. It is normally organised into
|
||
a single line that provides the headers (or <em>field names</em> or <em>column headings</em>) of the data
|
||
columns, followed by the data, one record per line.</p></div>
|
||
<div class="paragraph"><p>There are two types of <em>CSV</em> dive logs that can be imported into <em>Subsurface</em>:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
<em>CSV dive details</em>: This dive log format contains similar information to that of a
|
||
typical written dive log, e.g. dive date and time, dive depth, dive duration, names of
|
||
buddy and dive master and perhaps some information about cylinder pressures before and
|
||
after the dive, as well as a comment or two about the dive. All the data for a single
|
||
dive go on a single line of text, following the order of the column headings.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CSV dive profile</em>: This dive log format includes much more information about a single
|
||
dive. For instance there may be information at 30-second intervals, indicating depth, water
|
||
temperature at that depth, and cylinder pressure at that moment in time. Each line contains
|
||
the information for a single instant in time during the dive, 30 seconds after that
|
||
of the previous instant. Many lines
|
||
are required to complete the depth profile information for a single dive. This is a common
|
||
export format used by closed-circuit rebreather (CCR) dive equipment and many software
|
||
packages that handle dive computer data and/or dive logs.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Before being able to import the <em>CSV</em> data to <em>Subsurface</em> <strong>one needs to know a few
|
||
things about the data being imported</strong>:</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 (,) a semicolon (;) or a TAB character.
|
||
This can be determined by opening the file with a text editor. If it is
|
||
comma-delimited or semicolon-delimited, the comma or semicolon
|
||
characters between the values are clearly visible. If these are not evident and
|
||
the numbers are aligned in columns,
|
||
the file is probably TAB-delimited (i.e. it uses a TAB as a field separator).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Which data columns need to be imported into <em>Subsurface</em>? Is it a <em>CSV dive details</em>
|
||
file or a <em>CSV dive profile</em> file? Open the file using a text editor and note
|
||
the titles of the columns to be imported and their column positions.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Is the numeric information (e.g. dive depth) in metric or in imperial units?
|
||
</p>
|
||
</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> (towards the bottom right). This shows all .CSV files in the selected
|
||
directory. Select the file that needs to be imported. A configuration panel
|
||
appears as depicted below:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/csv_import1_f20.jpg" alt="FIGURE: CSV download dialogue 1" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Notice that, at the top left, there is a dropdown list containing pre-configured
|
||
settings for some of the more common dive computers and software packages
|
||
encountered by divers. If the <em>CSV</em> file being imported originated from any of
|
||
these pre-configured items, then select it. Otherwise use the <em>Manual Import</em>
|
||
option. The configuration panel also has dropdown lists for the specification of the appropriate
|
||
field separator (Tab, comma or semicolon), the date format used in the <em>CSV</em> file,
|
||
the time units (seconds, minutes or minutes:seconds), as well as the unit system
|
||
(metric or imperial). Selecting the appropriate options among these is critical for
|
||
the successful import of the data.</p></div>
|
||
<div class="paragraph"><p>The last remaining task is to ensure that all the data columns have the appropriate
|
||
column headings. The top blue row of the data table contains the column
|
||
headings found in the <em>CSV</em> data file. The blue row of balloons immediately above these
|
||
contains the names understood by <em>Subsurface</em>. These balloons can be moved using a drag-and-drop action. For
|
||
instance, <em>Subsurface</em> expects the column heading for Dive number (" # ") to be "Dive # ". If
|
||
the column heading that <em>Subsurface</em> expects is not in the blue row, then drag the
|
||
appropriate balloon from the upper area and drop it in the appropriate blue
|
||
cell at the top of the table. To indicate the correct column for "Dive #", drag
|
||
the ballooned item labelled "Dive # " and drop it in the blue
|
||
cell immediately above the white cell containing " # ". This is depicted in
|
||
the image below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/csv_import2_f20.jpg" alt="FIGURE: CSV download dialogue 2" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Continue in this way to ensure that all the column headings in the blue row of
|
||
cells correspond to the headings listed in the top part of the dialogue. Having
|
||
completed this task, select the <em>OK</em> button to the bottom right of the dialogue.
|
||
The data from the <em>CSV</em> file are imported and shown in the <strong>Dive List</strong> panel.</p></div>
|
||
<div class="sidebarblock" id="S_CSV_Intro">
|
||
<div class="content">
|
||
<div class="paragraph"><p><strong>A Diver’s Introduction to <em>CSV</em> Files</strong></p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content"><em>CSV</em> is an abbreviation for a data file format: <em>Comma-Separated Values</em>. It is a
|
||
file format allowing someone to view or edit the information using a text editor such
|
||
as Notepad (Windows), gedit (Linux) or TextWrangler (OS/X). The two main advantages of
|
||
the <em>CSV</em> format is that the data are easily editable as text without any proprietary software
|
||
and ensuring all information is human-readable, not being obscured by any custom or
|
||
proprietary attributes that proprietary software insert into files.
|
||
Because of its simplicity the <em>CSV</em> format is used
|
||
as an interchange format between many software packages, e.g. between
|
||
spreadsheet, statistical, graphics, database and diving software. Within <em>Subsurface</em>, <em>CSV</em> files can also
|
||
be used to import information from other sources such as spreadsheet-based dive logs and
|
||
even from some dive computers.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><em>CSV</em> files can be created or edited with a normal text editor. The most important attribute of a
|
||
<em>CSV</em> file is the <em>field separator</em>, the character used to separate fields within a single line. The
|
||
field separator is frequently a comma, a colon, a SPACE character or a TAB character. When exporting data from
|
||
spreadsheet software, the field separator needs to be specified in order to create the <em>CSV</em> file. <em>CSV</em> files are
|
||
normally organised into a single line that provides the headers (or <em>field names</em>) of the data columns,
|
||
followed by the data, one record per line. Note that each field name
|
||
may comprise more than one word separated by spaces; for instance <em>Dive site</em>, below. Here is an example of
|
||
dive information for four dives using a comma as a field separator:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Dive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy
|
||
Illovo Beach,2012-11-23,10:45,46:15,18.4,John Smith
|
||
Key Largo,2012-11-24,09:12,34:15,20.4,Jason McDonald
|
||
Wismar Baltic,2012-12-01,10:13,35:27,15.4,Dieter Albrecht
|
||
Pulau Weh,2012-12-20,09:46,55:56,38.6,Karaeng Bontonompo</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>The above data are not easily read by a human. Here is the same information in TAB-delimited format:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Dive site Dive date Time Dive_duration Dive_depth Dive buddy
|
||
Illovo Beach 2012-11-23 10:45 46:15 18.4 John Smith
|
||
Key Largo 2012-11-24 09:12 34:15 20.4 Jason McDonald
|
||
Wismar Baltic 2012-12-01 10:13 35:27 15.4 Dieter Albrecht
|
||
Pulau Weh 2012-12-20 09:46 55:56 38.6 Karaeng Bontonompo</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>It is clear why many people prefer the TAB-delimited format to the comma-delimited format. The
|
||
disadvantage is that one cannot see
|
||
the TAB characters. For instance, the space between <em>Dive</em> and <em>date</em> in the top line may be
|
||
a SPACE character or a TAB character (in this case it is a SPACE character: the tabs are before and
|
||
after <em>Dive date</em>). If the field names in the first line are long, the alignment with data in the other lines
|
||
cannot be maintained. Here is a highly simplified and shortened TAB-delimited example of a <em>CSV</em> dive log
|
||
from an APD closed-circuit rebreather (CCR) dive computer:</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</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>When a <em>CSV</em> file is selected for import, <em>Subsurface</em> displays the column headers as well as some of the data
|
||
in the first few lines of the <em>CSV</em> file, making it much easier to work with <em>CSV</em> files.
|
||
<em>CSV</em> files can therefore be used in many contexts for importing data into a <em>Subsurface</em> dive log.
|
||
Knowledge of a few basic things about the content of the <em>CSV</em> file allows a smooth import
|
||
of the dives into <em>Subsurface</em>.</p></div>
|
||
</div></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">The <em>CSV</em> import has a couple of caveats. One should avoid some special characters
|
||
like ampersand (&), less than (<), greater than (>) and double quotes (") as part
|
||
of the numbers or text within a cell. The
|
||
file should use UTF-8 character set, if using non-ASCII characters. Also the
|
||
size of the <em>CSV</em> file might cause problems. Importing 100 dives at a time
|
||
(<em>CSV dive details</em>) works, but larger files might exceed
|
||
the limits of the parser used. When encountering problems with <em>CSV</em> imports, first try with
|
||
a smaller file to make sure everything works.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Companion">5.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 <em>Android device</em> or
|
||
<a href="#S_iphone"><em>iPhone</em></a> with 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 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">5.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_an_android_smartphone">5.4.2. Using the Subsurface companion app on an Android 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 selects 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 50 m
|
||
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="S_iphone">5.4.3. Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h4>
|
||
<div class="paragraph"><p>The iPhone interface is quite simple. One needs to type the user ID (obtained
|
||
during registration) into the space reserved for it, then select "Dive in"
|
||
(see left part of the image below) and start collecting dive location information.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/iphone.jpg" alt="FIGURE: Using iPhone companion application" width="640" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Dives can be added automatically or manually. In manual mode, a dive location or waypoint is added to the GPS input stream. In automatic mode, a continuous path of GPS locations is created from which, much later, after import, subsurface can select the appropriate GPS locations based on the times of dives. The default mode for the <em>iphone</em> is automatic. When one adds a dive, the
|
||
location service is started automatically and a red bar appears at the bottom
|
||
of the screen. After the dive one can click on the red
|
||
bar to end the location service. While the location
|
||
service is running one can only add dives using the manual mechanism.</p></div>
|
||
<div class="paragraph"><p>One can edit the site name afterwards by selecting the dive
|
||
from the dive list and clicking on the site name. There are no other
|
||
editable fields. The dive list is automatically uploaded from the iPhone
|
||
to the webservice and there is not an option to
|
||
trigger upload manually.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">5.4.4. 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">5.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">5.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_f20.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_f20.jpg" alt="FIGURE: Load images option" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This brings up 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 three ways:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Pro-actively</strong>: Before the dive, ensure synchronisation of the dive computer time settings with
|
||
the time settings of the camera by changing the date-time settings on one or both of these devices.
|
||
</p>
|
||
</li>
|
||
<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_f20.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 <em>Time shift</em> 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 dive computer showing time</em>. This brings up
|
||
a file browser with which one can select the photograph of the dive computer time. 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.
|
||
Image <strong>B</strong> above shows a photograph of the face of the dive computer and with the date-time tool set to the
|
||
date-time.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If the timestamp of a photograph is more than 30 minutes before or after the dive, it is not placed on
|
||
the dive profile.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_viewing_the_photos">5.5.2. Viewing the photos</h4>
|
||
<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>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.
|
||
In order to view the photos on the dive profile, activate the <em>show-photos</em> button in the tool bar
|
||
to the left of the dive profile:
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:left;">
|
||
<div class="content">
|
||
<img src="images/icons/ShowPhotos_f20.png" alt="FIGURE:Show photos toolbar button" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This results in a profile display as in the image below:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage4_f20.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_f20.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_f20.jpg" alt="FIGURE: Full-screen photo on dive profile" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_the_em_photos_em_tab">5.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>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">5.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 by the operating system
|
||
(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 class="sect3">
|
||
<h4 id="S_FindMovedImages">5.5.5. Moving photographs among directories, hard disks or computers</h4>
|
||
<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive, the directory
|
||
where the photo lies is stored, allowing <em>Subsurface</em> to find the photograph when the dive is
|
||
opened again. If the photo or the whole photo collection is moved to another drive or to a different
|
||
machine, it is unlikely that the directory structure will remain identical to that of the original uploaded
|
||
photo. When this happens, <em>Subsurface</em> looks for the photos at their original location before they were moved,
|
||
cannot find them and therefore cannot display them. Because, after moving photos, large numbers of photos
|
||
may need to be deleted and re-imported from the new location, <em>Subsurface</em> has a mechanism that eases the
|
||
process of updating the directory information for each photo: automatic updates using fingerprints.</p></div>
|
||
<div class="paragraph"><p>When a photo is loaded into <em>Subsurface</em>, a fingerprint for the image is calculated and stored with the
|
||
other reference information for that photo. After moving a photo collection (that has already been loaded
|
||
into <em>Subsurface</em>) to a different directory, disk or computer, <em>Subsurface</em> can perform the
|
||
following steps:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
look through a particular directory (and all its subdirectories recursively) where photos have been moved
|
||
to,
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
calculate fingerprints for all photos in this directory, and
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
if there is a match between a calculated fingerprint and the one originally calculated when a photo was
|
||
loaded into <em>Subsurface</em> (even if the original file name has changed), to automatically update the
|
||
directory information so that <em>Subsurface</em> can find the photo in the new moved directory.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>This is achieved by selecting from the Main Menu: <em>File → Find moved images</em>. This brings up a window within
|
||
which the NEW directory of the photos needs to be specified. Select the appropriate directory and click
|
||
the <em>Scan</em> button towards the bottom right of the panel. The process may require several minutes to
|
||
complete, after which <em>Subsurface</em> will show the appropriate photographs when a particular dive is opened.</p></div>
|
||
<div class="sidebarblock" id="Image_fingerprint_upgrade">
|
||
<div class="content">
|
||
<div class="paragraph"><p><strong>Upgrading existing photo collections without fingerprints</strong></p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content"><em>Subsurface</em> automatically calculates fingerprints for all images that can be accessed by <em>Subsurface</em>.
|
||
When manipulating images, ensure that all the images associated with the dive log can be accessed by <em>Subsurface</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><em>Subsurface</em> automatically checks and, if necessary, updates the fingerprints associated with a single dive if:
|
||
- The images associated with that dive are visible as thumbnails on the <strong>Dive Profile</strong>.
|
||
- One edits anything in the <strong>Notes tab</strong> panel and save the edits by selecting <em>Apply changes</em>.</p></div>
|
||
</div></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_logging_special_types_of_dives">5.6. Logging special types of dives</h3>
|
||
<div class="sect3">
|
||
<h4 id="S_MulticylinderDives">5.6.1. Multicylinder dives</h4>
|
||
<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one cylinder. Multi-cylinder diving usually happens
|
||
(a) if a diver does not have enough gas for the complete dive in a single cylinder; (b) if the diver
|
||
needs more than one gas mixture because of the depth or the decompression needs of the dive. For this reason
|
||
multi-cylinder dives are often used by technical divers who dive deep or long. As far
|
||
as <em>Subsurface</em> is concerned, there are only two types of information that need to be provided:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Describe the cylinders used during the dive</strong> This is performed in the <strong>Equipment tab</strong> of
|
||
the <strong>Info</strong> panel, as <a href="#cylinder_definitions">described above</a>. Enter the cylinders one by one,
|
||
specifying the characteristics of the cylinder and the gas composition within each cylinder.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Record the times at which switches from one cylinder to another was done:</strong> This is information
|
||
provided by some dive computers (provided the diver indicated these changes to the dive computer
|
||
by pressing specific buttons). If the dive computer does not provide the information, the diver has to
|
||
record these changes using a different method, e.g. writing it on a slate.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Record the cylinder changes on the dive profile</strong>: If the latter option
|
||
was followed, the diver needs to indicate the gas change event by right-clicking at the appropriate point
|
||
in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After
|
||
right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from
|
||
those defined during the first step, above (see image below). If the
|
||
<strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the
|
||
tank bar.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Having performed these tasks, <em>Subsurface</em> indicates the appropriate use of cylinders in the dive profile.
|
||
Below is a multi-cylinder dive, starting off with EAN28, then changing cylinders to EAN50 after 26 minutes
|
||
to perform decompression.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/multicylinder_dive.jpg" alt="FIGURE: Multicylinder profile" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_sidemount_dives">5.6.2. Sidemount dives</h4>
|
||
<div class="paragraph"><p>Sidemount diving is just another form of multi-cylinder diving, often with both or all cylinders having
|
||
the same gas mixture. Although it is a popular configuration for cave divers, sidemount
|
||
diving can be performed by recreational divers who have completed the appropriate training. Sidemount
|
||
dive logging involves, exactly as with multi-cylinder dives, above, three steps:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>During the dive, record cylinder switch events</strong>. Since sidemount diving normally involves two
|
||
cylinders with air or with the same gas mixture, <em>Subsurface</em> distinguishes among these different
|
||
cylinders. In contrast, many dive computers that allow gas switching only distinguish among different
|
||
<em>gases</em> used, not among different <em>cylinders</em> used. This means that when sidemount dives are downloaded
|
||
from these dive computers, the events of switching between cylinders with the same gas are not downloaded. This may mean
|
||
that one may have to keep a written log of cylinder switch times using a slate, or (if the dive computer
|
||
has this facility) marking each cylinder switch with a bookmark that can be retrieved later. Returning
|
||
from a dive with the times of cylinder changes is the only tricky part of logging sidemount dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Within <em>Subsurface</em> describe the cylinders used during the dive</strong>. The diver needs to provide the
|
||
specifications of the different cylinders, using the <strong>Equipment</strong> tab of the <strong>Info Panel</strong> (see
|
||
image below where two 12 litre cylinder were used).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Indicate cylinder change events on the <em>Subsurface</em> dive profile</strong>. Once the dive log has been imported
|
||
from a dive computer into <em>Subsurface</em>, the cylinder switch events need to be indicated on the dive profile.
|
||
Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile and then
|
||
selecting <em>Add gas change</em>. A list of the appropriate cylinders is shown with the
|
||
currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2
|
||
to be selected. Select the appropriate cylinder. The cylinder change is then indicated on the dive
|
||
profile with a cylinder symbol. If the <strong>Tank Bar</strong> is activated using the toolbar to the left of the
|
||
profile, then the cylinder change is also indicated on the Tank Bar (see image below). After all
|
||
the cylinder change events have been recorded on the dive profile, the correct cylinder pressures
|
||
for both cylinders are shown on the dive profile, as in the image below.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This section gives an example of the versatility of <em>Subsurface</em> as a dive logging tool.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_sSCR_dives">5.6.3. Semi-closed circuit rebreather (SCR) dives</h4>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/halcyon_RB80.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Passive semi-closed rebreathers (pSCR) comprise a technical advance in diving equipment that
|
||
recirculates the breathing gas that a diver breathes, while removing carbon dioxide from
|
||
the exhaled gas. While a small amount (typically a tenth) of the exhaled breathing gas is released into the water,
|
||
a small amount of fresh gas is released from the back gas cylinder (typically containing nitrox).
|
||
A diver, using a single cylinder of breathing gas can therefore dive for much longer periods than
|
||
using a recreational open-circuit configuration. With pSCR equipment, a very small amount of breathing
|
||
gas is released every time the breather inhales. With active SCR (aSCR) equipment, in contrast, a small amount of
|
||
breathing gas is released continuously from the back cylinder.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>To log pSCR dives, no special procedures are required, just the normal steps outlined above:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Select pSCR in the <em>Dive Mode</em> dropdown list on the <strong>Info</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
pSCR diving often involves gas changes, requiring an additional cylinder.
|
||
Define all the appropriate cylinders as described above
|
||
and indicate the cylinder/gas changes as described above in the section on <a href="#S_MulticylinderDives">multicylinder dives</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If a pSCR <em>Dive Mode</em> has been selected, the dive ceiling for pSCR dives is adjusted for the oxygen
|
||
drop across the mouthpiece which often requires longer decompression periods. Below is a dive profile
|
||
of a pSCR dive using EAN36 on the back cylinder and oxygen for decompression. Note that this dive lasted
|
||
over two hours.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/pSCR_profile.jpg" alt="FIGURE: pSCR profile" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_CCR_dives">5.6.4. Closed circuit rebreather (CCR) dives</h4>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/APD.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Closed system rebreathers use advanced 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.
|
||
The CCR interface of <em>Subsurface</em> is currently experimental
|
||
and under active development. Subsurface currently supports Poseidon MkVI
|
||
and APD Discovery/Evolution dive computers. In contrast to a conventional recreational
|
||
dive computer, a CCR system computer does not allow the download of a log
|
||
containing 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 digital databases: one dive at a time.</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 that section, the bottom right
|
||
hand of the import dialogue contains a dropdown list (labled <em>Filter:</em>) of appropriate devices
|
||
that currently includes(Poseidon) MkVI or APD log viewer files (import for other
|
||
CCR equipment is under active development). 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.
|
||
The selected dive is imported to the <em>Subsurface</em> dive list.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_displayed_information_for_a_ccr_dive">Displayed information for a CCR 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 contrast to recreational
|
||
equipment (where pO<sub>2</sub> values are calculated based on gas composition and dive depth),
|
||
CCR equipment provide actual measurements of pO<sub>2</sub>, derived from oxygen sensors.
|
||
In this case the graph for oxygen partial pressure
|
||
should be fairly flat, reflecting the setpoint settings during the dive. The mean
|
||
pO<sub>2</sub> is NOT the mean oxygen partial pressure as given by the CCR equipment, but
|
||
a value calculated by <em>Subsurface</em> as follows:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
For TWO O<sub>2</sub> sensors the mean value of the two sensors are given.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
For THREE-sensor systems (e.g. APD), the mean value is also used. However
|
||
differences of more than 0,1 bar in the simultaneous readings of different sensors are
|
||
treated as spurious. If one of the three sensors provides spurious data, it is ignored.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If no sensor data are available, the pO<sub>2</sub> value is assumed to be equal to the setpoint.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The mean pO<sub>2</sub> of the sensors is indicated with a green line,</p></div>
|
||
<div class="paragraph"><p>The oxygen setpoint values as well as the readings from the individual
|
||
oxygen sensors can be shown. The display of additional CCR information is turned on by
|
||
checking the appropriate checkboxes in the <em>Preferences</em> panel (accessible by
|
||
selecting <a href="#S_CCR_options"><em>File → Preferences → Graph</em></a>). This part of
|
||
the <em>Preferences</em> panel is shown in the image below, representing two checkboxes that modify
|
||
the display of pO<sub>2</sub> when the appropriate toolbar button on the Dive Profile
|
||
has been activated.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CCR_preferences_f20.jpg" alt="FIGURE: CCR preferences panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Checking any of these check boxes allows the display of additional oxygen-related
|
||
information whenever the pO<sub>2</sub> toolbar button on the <em>Profile</em> panel is activated.
|
||
The first checkbox allows the display of setpoint information. This is a red line
|
||
superimposed on the green oxygen partial pressure graph and allows a comparison of the
|
||
mean measured oxygen partial pressure and the setpoint values, as shown below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CCR_setpoint_f20.jpg" alt="FIGURE: CCR setpoint and po2 graph" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The second checkbox allows the display of the data from each individual oxygen sensor
|
||
of the CCR equipment. The data for each sensor is colour-coded as follows:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Sensor 1: grey
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Sensor 2: blue
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Sensor 3: brown
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The mean oxygen pO<sub>2</sub> is indicated by the green line. This allows the direct comparison
|
||
of data from each of the oxygen sensors, useful for detecting abnormally low or erratic
|
||
readings from a particular sensor.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURE: CCR sensor data graph" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The setpoint data can be overlaid on the oxygen sensor data by activating both of the above
|
||
check boxes. Partial pressures for nitrogen (and helium, if applicable) are shown in the
|
||
usual way as for open circuit dives.</p></div>
|
||
<div class="paragraph"><p><em>Events</em>: Several events are logged, e.g. switching the mouthpiece to open circuit.
|
||
These events are indicated by yellow triangles and, if one hovers over a triangle,
|
||
a description of that event is given as the bottom line in the <a href="#S_InfoBox">Information Box</a>.</p></div>
|
||
<div class="paragraph"><p><em>Cylinder pressures</em>: Some CCR dive computers like the Poseidon MkVI record the
|
||
pressures of the oxygen and diluent cylinders. The pressures of these two cylinders
|
||
are shown as green lines overlapping the depth profile. In addition, start and
|
||
end pressures for both oxygen and diluent cylinders are shown in the <em>Equipment Tab</em>.
|
||
Below is a dive profile for a CCR dive, including an overlay
|
||
of setpoint and oxygen sensor data, as well as the cylinder pressure data. In this
|
||
case there is good agreement from the readings of the two oxygen sensors.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURE: CCR dive profile" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by
|
||
<em>Subsurface</em> is shown in the <a href="#S_ExtraDataTab">Extra data tab</a>. This may include setup information
|
||
or metadata about the dive.</p></div>
|
||
<div class="paragraph"><p>The deco ceiling calculated by Subsurface is not very accurate because the precise pressure of nitrogen
|
||
in the loop can usually not be determined from the dive log imported from the CCR equipment. Many CCR dive
|
||
computers, however, report an internally-calculated deco ceiling that is reported in the dive log,
|
||
reflecting a more accurate assessment. The display of this ceiling is activated
|
||
by clicking the appropriate button to the left of the dive profile:</p></div>
|
||
<div class="imageblock">
|
||
<div class="content">
|
||
<img src="images/icons/cceiling.jpg" alt="DC ceiling icon" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The default colour of the computer-generated deco ceiling is white. However, this can be set to red
|
||
by checking the appropriate check box after selecting <em>File → Preferences → Graph</em>.
|
||
Below is a dive profile indicating the dive computer-generated deco ceiling:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURE: CCR computer-generated deco ceiling" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs for
|
||
Poseidon MkVI and APD equipment can be found in <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a>.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">6. Obtaining more information about dives entered into the logbook</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_the_strong_info_strong_tab_for_individual_dives">6.1. The <strong>Info</strong> tab (for individual dives)</h3>
|
||
<div class="paragraph"><p>The 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="S_ExtraDataTab">6.2. The <strong>Extra Data</strong> tab (usually for individual dives)</h3>
|
||
<div class="paragraph"><p>When using a dive computer, it often reports several data items that cannot easily be
|
||
presented in a standardised way because the nature of the information differs from one
|
||
dive computer to another. These data often comprise setup information, metadata about
|
||
a dive, battery levels, no fly times, or gradient factors used during the dive. When
|
||
possible, this information is presented in the <strong>Extra Data</strong> tab. Below is an
|
||
image showing extra data for a dive using a Poseidon rebreather.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/ExtraDataTab_f20.jpg" alt="FIGURE: Extra Data tab" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_the_strong_stats_strong_tab_for_groups_of_dives">6.3. 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">6.4. 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 plotted as a grey line, indicating mean dive depth up to a particular moment during the dive.</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 O<sub>2</sub>, N<sub>2</sub>, 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/icons/ShowCylindersButton.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">By selecting this icon, the different cylinders used during a dive can be represented as a coloured bar at the bottom
|
||
of the <strong>Dive Profile</strong>. In general oxygen is represented by a green bar, nitrogen with a yellow bar and helium with a
|
||
red bar. The image below shows a dive which first uses a trimix cylinder (red and green), followed by a switch to a nitrox cylinder
|
||
(yellow and green) after 23 minutes. Cylinders with air are shown as a light blue bar.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/ShowCylinders_f20.jpg" alt="Figure: Cylinder use graph" />
|
||
</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 contrast, 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">6.5. 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 or manual CCR set-point changes 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
|
||
involve a selection of which gas is being switched to, the list of choices being based on
|
||
the available gases defined in the <strong>Equipment</strong> Tab. Set-point change
|
||
events open a dialog allowing to choose the next set-point value. As
|
||
in the planner, a set-point value of zero indicates the diver is
|
||
breathing from an open circuit system while any non-zero value
|
||
indicates the use of a closed circuit rebreather (CCR).
|
||
By right-clicking while over
|
||
an existing marker a menu appears, 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="S_InfoBox">6.6. 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 if a maximum pO<sub>2</sub> of 1.4 is specified in the <strong>Preferences</strong> section
|
||
(select <em>File</em> → Preferences → Graph_ and edit the text box <em>Max pO<sub>2</sub> when showing MOD</em>.
|
||
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">6.6.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 gradient factor that applies to the depth of
|
||
the diver at the particular point on the <strong>Dive Profile</strong>. The gradient factor shown is an
|
||
interpolation between the GFLow 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 equilibrium 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">7. Organising the logbook (Manipulating groups of dives)</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_the_dive_list_context_menu">7.1. The Dive List context menu</h3>
|
||
<div class="paragraph"><p>Several actions on either a single dive or a group of dives can be performed using the Dive List
|
||
Context Menu, found by selecting either a single 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_columns_showed_in_the_strong_dive_list_strong_panel">7.1.1. Customising the columns showed in the <strong>Dive List</strong> panel</h4>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<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 controlled 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 (reflected by the check symbols) and the list is immediately updated. Preferences for information
|
||
shown in the <strong>Dive List</strong> are saved and used when <em>Subsurface</em> is re-opened.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Renumber">7.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 class="paragraph"><p>One can also renumber a few selected dives in the dive list. Select the dives that
|
||
need renumbering. Right-click on the selected list and use the Dive List Context Menu
|
||
to perform the renumbering. A popup window appears requiring the user to specify
|
||
the starting number for the renumbering process.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Group">7.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 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) 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">7.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>Notes</strong> panel. Here
|
||
one 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, 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 the
|
||
edited information.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_viewing_the_dives_during_a_particular_trip">7.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">7.3.3. Collapsing or expanding dive information for different trips</h4>
|
||
<div class="paragraph"><p>After selecting a particular trip in the dive list, the
|
||
context menu allows several possibilities to expand or collapse dives
|
||
within trips. This includes expanding all trips and collapsing all trips.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">7.3.4. Merging dives from more than one trip into a single trip</h4>
|
||
<div class="paragraph"><p>After selecting a trip title, the context menu allows the merging
|
||
of trips by either merging the selected trip with the trip below or with the
|
||
trip above. (Merge trip with trip below; Merge trip with trip above)</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_splitting_a_single_trip_into_more_than_one_trip">7.3.5. Splitting a single trip into more than one trip</h4>
|
||
<div class="paragraph"><p>If a trip includes ten dives, the user can split this trip into two trips (trip 1:
|
||
top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the top
|
||
four 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 four 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">7.4. Manipulating single dives</h3>
|
||
<div class="sect3">
|
||
<h4 id="_delete_a_dive_from_the_dive_log">7.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">7.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 or below the trip to
|
||
which they belonged, depending on the date and time of the unlinked dive.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_add_a_dive_to_the_trip_immediately_above">7.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
|
||
a separate trip. To do this, select and right-click
|
||
the dive(s) to bring up the context menu, and then select <strong>Create new trip above</strong>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_shift_the_start_time_of_dive_s">7.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, 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 ealier or later.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_merge_dives_into_a_single_dive">7.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>Notes</strong>
|
||
panel to reflect events or conditions that apply to the merged dive. The figure
|
||
below shows the depth profile of two 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 class="sect3">
|
||
<h4 id="_undo_dive_manipulations">7.4.6. Undo dive manipulations</h4>
|
||
<div class="paragraph"><p>Important actions on dives or trips, described above, can be undone or redone.
|
||
This includes: <em>delete dives</em>, <em>merge dives</em>, <em>renumber dives</em> and <em>shift dive times</em>.
|
||
To do this after performing any of these actions, from the <strong>Main Menu</strong> select
|
||
<em>Edit</em>. This brings up the possibility to <em>Undo</em> or <em>Redo</em> an action.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Filter">7.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 (see image below). The <em>Filter Panel</em> can be reset
|
||
(i.e. all current filters cleared) by selecting the <strong>yellow angled arrow</strong>. The <em>Filter Panel</em> may also be
|
||
minimised by selecting the <strong>green up-arrow". 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 *red button</strong> with the white cross.</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, check at least one check box in one of
|
||
the four check lists. The dive list is then shortened to include
|
||
only the dives that pertain to the criteria specified in the check lists.
|
||
The four check lists work as a filter with <em>AND</em> operators, Subsurface
|
||
filters therefore 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">8. Exporting the dive log or parts of the dive log</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>There are two routes for the export of dive information from Subsurface:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Export dive information to <em>Facebook</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Export_other">Export dive information to other destinations or formats</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect2">
|
||
<h3 id="S_facebook">8.1. Exporting dive information to <em>Facebook</em></h3>
|
||
<div class="paragraph"><p>Export of dives to <em>Facebook</em> is handled differently from other types of export because
|
||
a connection to <em>Facebook</em> is required, needing a <em>Facebook</em> userID and password.
|
||
If, from the <strong>Main Menu</strong>, one selects <em>File → Preferences → Facebook</em>, a login screen is presented
|
||
(image <strong>A</strong> to the left, below). Provide a <em>Facebook</em> userID and password.
|
||
Once a successful login to <em>Facebook</em> has been achieved, the panel
|
||
in image <strong>B</strong>, below is presented, including a <em>Disconnect from Facebook</em> button to close the
|
||
<em>Facebook</em> connection.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/facebook1_f20.jpg" alt="Figure: Facebook login" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>From the <em>Subsurface</em> window it is easy to determe whether <em>Subsurface</em> has a valid connection to <em>Facebook</em>
|
||
From the <strong>Main Menu</strong>, select <em>Share on → Facebook</em> (image <strong>A</strong>, below). Normally, the <em>Facebook</em> option is greyed out. But
|
||
if there is a connection to <em>Facebook</em>, this option is active (i.e. in black colour and can be selected).</p></div>
|
||
<div class="paragraph"><p>Having established a login to <em>Facebook</em>, transfer of a dive profile to one’s <em>Facebook</em> timeline is easy.
|
||
Ensure that the dive to be transfered to the timeline is depicted in the <em>Subsurface</em> <strong>Dive Profile</strong> panel. If, from the <strong>Main Menu</strong>, one selects <em>Share on → Facebook</em> (see image <strong>A</strong> below), a dialogue is shown, determining the amount of additional information transferred
|
||
with the dive profile (image <strong>B</strong>, below). In order to transfer a dive profile to <em>Facebook</em>, the name of a
|
||
<em>Facebook</em> album needs to be provided. The checkboxes on the lefthand side allow one to determine how much
|
||
additional information should be transferred with the dive profile. This information is shown in the text box
|
||
on the right hand side of the panel (image <strong>B</strong>, below). One can easily edit the message that will be posted
|
||
with the dive profile. Having specified the additional information and verified the text, select
|
||
the <em>OK</em> button that triggers the transfer to <em>Facebook</em>. After a while, an acknowledgement dialogue appears,
|
||
indicating successful transfer to <em>Facebook</em>.</p></div>
|
||
<div class="paragraph"><p>Both the album created and the post to one’s timeline will be marked as
|
||
private. In order for friends to be able to see the post,
|
||
change its permissions from a regular Facebook login either in a browser
|
||
or a Facebook app. While this is an extra step
|
||
this is the better solution to avoid having unwanted posts in one’s public
|
||
timeline.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>If required, then close the <em>Facebook</em> connection by either closing <em>Subsurface</em> or by selecting <em>File → Preferences → Facebook</em> from
|
||
the Main Menu, and clicking the appropriate button on the Facebook Preferences panel.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Export_other">8.2. Export dive information to other destinations or formats</h3>
|
||
<div class="paragraph"><p>For non-<em>Facebook exports</em>, 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_f20.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>DiveShare</em> is also a dive log repository on the Internet focusing on the recreational
|
||
dives. In order to upload dives one has to provide a used ID, so registration with
|
||
<em>http://scubadiveshare.com</em> is required.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CSV dive details</em>, that includes the most critical information of the dive
|
||
profile. Included information of a dive is: dive number, date, time, buddy,
|
||
duration, depth, temperature and pressure: in short, most of the information
|
||
that recreational divers enter into handwritten log books.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CSV dive profile</em>, that includes a large amount of detail for each dive, including
|
||
the depth profile, temperature and pressure information of each dive.
|
||
</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. The HTML export cannot be changed or edited.
|
||
It contains most of the information recorded in the dive log. However, it does not show the
|
||
calculated values in the <strong>Dive Profile</strong> panel, e.g. calculated cylinder pressure, gas
|
||
pressures and MOD. The HTML export 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). A typical use of this option is to export all one’s
|
||
dives to a smartphone or a tablet where it would serve as a very portable record
|
||
of dives useful for dive companies that wish to verify the dive history of a diver,
|
||
often doing away with the need to carry one’s original logbook with one
|
||
when doing dives with dive companies.
|
||
</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. If one selects any
|
||
of the dive sites on the map, a summary of the dive is available in text, as shown
|
||
in the image below.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/mapview_f20.jpg" alt="Figure: HTML Map export view" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Image depths</em>, which creates a text file that contains the file names of all
|
||
photos or images attached
|
||
to any of the selected dives in the <em>Dive List</em>, together with the depth under water where
|
||
of each of those photos were taken.
|
||
</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 to the HTML exports.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Export List only: a list of dives only (date, time, depth, duration) will be exported
|
||
and the detailed dive information, e.g. dive profile, 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>
|
||
<div class="sect1">
|
||
<h2 id="S_Cloud_access">9. 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 to store
|
||
dive log information on the Internet.</p></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> includes access to a transparently integrated cloud storage
|
||
back end that is available to all Subsurface users. Storing and retrieving a dive log
|
||
from the cloud is no more difficult than accessing the dives on the local hard disk.
|
||
The only requirement is that one should first register as a user on the cloud.
|
||
To use <em>Subsurface cloud storage</em> , follow these steps:</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_create_a_cloud_storage_account">9.1. Create a cloud storage account</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Open the <strong>Network Preferences</strong> by selecting <em>File</em> → <em>Preferences</em> → <em>Network</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the section headed <em>Subsurface cloud storage</em>, enter an email address that
|
||
<em>Subsurface</em> can use for user registration.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Enter a novel password that <em>Subsurface</em> will use to store the
|
||
dive log in the cloud.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Apply</em> to send the above email address and password to the
|
||
(remote) cloud server. The server responds by sending a verification PIN to
|
||
the above email address (This is the <strong>only</strong> occasion that <em>Subsurface</em> uses the
|
||
email address provided above). The <strong>Network Preferences</strong> dialog now has a new PIN text
|
||
box, not visible previously.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Enter the PIN in the corresponding text box in the <strong>Network Preferences</strong> dialog
|
||
(this field is only visible while the server is waiting for email
|
||
address confirmation)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Apply</em> again. The <em>Subsurface cloud storage</em> account
|
||
will be marked as verified and the <em>Subsurface cloud storage</em> service is initialised for use.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_using_em_subsurface_cloud_storage_em">9.2. Using <em>Subsurface cloud storage</em></h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Once the cloud storage has been initialised, two new items appear in the
|
||
<em>File</em> menu of the main menu system: <em>Open cloud storage</em> and <em>Save to cloud storage</em>.
|
||
These options allow the user to load and save data to the <em>Subsurface
|
||
cloud storage</em> server.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the <em>Defaults Preferences</em> tab, one can select to use the <em>Subsurface cloud
|
||
storage</em> data as one’s default data file by checking the check box marked <em>Cloud storage default file</em>.
|
||
This means that the data from
|
||
the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts ans saved there when one closes <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface</em> keeps a local copy of the data and the cloud facility remains fully
|
||
functional even if used while disconnected to the Internet. <em>Subsurface</em> simply synchronises the
|
||
data with the cloud server the next time ithe program is used while the computer is
|
||
connected to the Internet.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Cloud_storage">9.3. Web access to <em>Subsurface cloud storage</em></h3>
|
||
<div class="paragraph"><p>One of the nice side benefits of using <em>Subsurface cloud storage</em> is that
|
||
one can also access one’s dive data from any web browser. Simply open
|
||
<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>,
|
||
log in with the same email and password, and you can see an HTML export of
|
||
the last dive data that was synced to the <em>Subsurface cloud storage</em>. The dive information
|
||
that is shown is only the contents of the recorded dive logs, NOT the calculated values
|
||
shown in the <strong>Profile</strong> panel,
|
||
including some cylinder pressures, deco ceilings and O<sub>2</sub>/He/N<sub>2</sub> partial pressures.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_other_cloud_services">9.4. Other cloud services</h3>
|
||
<div class="paragraph"><p>If one prefers not to use the integrated cloud storage of dive logs (and
|
||
don’t need the web access), it is also simple to store
|
||
dive logs in the cloud using several of the existing facilities on the
|
||
Internet.
|
||
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 on <em>Dropbox</em>, 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 <em>Dropbox</em>, 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>
|
||
<div class="sect1">
|
||
<h2 id="S_PrintDivelog">10. Printing a dive log</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible interface to print a whole dive log or only a few selected dives.
|
||
Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.</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 select the required dives from the <strong>Dive List</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If the dive profiles needs printing, what gas partial pressure information should be shown? Select
|
||
the appropriate toggle-buttons on the button bar to the left of the <strong>Dive Profile</strong> panel.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If <em>File → Print</em> is selected from the Main menu, the the dialogue below (image <strong>A</strong>) appears. Three
|
||
specifications are needed to achieve the desired information and page layout:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Under <em>Print type</em> select one of two options:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Dive list print</em>: Print dives from the <strong>Dive List</strong> panel with profiles and other information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Statistics print</em>: Print yearly statistics of the dives.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Under <em>Print options</em> select:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Printing only the dives selected from the dive list prior to
|
||
activating the print dialogue by checking the box <em>Print only
|
||
selected dives</em>. If this check box is <strong>not</strong> checked all dives in
|
||
the <strong>Dive List</strong> panel are printed.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Printing in colour, achieved by checking the box with <em>Print in colour</em>. If this check box
|
||
is not checked, printing is in monochrome (grey scale).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Under <em>Template</em> select a template to be used as the page layout. There are several templates
|
||
(see image <strong>B</strong>, above).
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Table</em>: This prints a summary table of all dives selected (see below).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ol></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Print_summarylist_f22.jpg" alt="FIGURE: Print summary table" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Flow layout</em>: Print the text associated with each dive without printing the dive profiles
|
||
of each dive (see below):
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>One Dive</em>: Print one dive per page, also showing the dive profile (see below)
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Two Dives</em>: Print two dives per page, also showing the dive profiles.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Six Dives</em>: Print six dives per page, also showing the dive profiles.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Users can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on the
|
||
dialogue (see image <strong>A</strong> at the start of this section). 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 (see image <strong>A</strong> at the start of this section). This activates the regular print
|
||
dialogue used by the user operating system,
|
||
allowing one to choose a printer and to set its properties (see image below):</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Print_print_f22.jpg" alt="FIGURE: Print dialog" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Set the print resolution of the printer to an appropriate value by changing
|
||
the printer <em>Properties</em>. Finally, select the <em>Print</em> button to 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 class="sect2">
|
||
<h3 id="_writing_a_custom_print_template_advanced">10.1. Writing a custom print template (advanced)</h3>
|
||
<div class="paragraph"><p>Writing a custom template is an effective way to produce highly customized printouts. Subsurface uses HTML templates
|
||
to render printing. One can create a template, export a new template, import an existing template and delete an existing template by using the appropriate buttons under the <em>Template</em> dropdown list in the print dialogue. See <a href="#S_APPENDIX_E">APPENDIX E</a> for information on how to write or modify a template.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_Configure">11. Configuring a dive computer</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> enables one to configure a dive computer. Currently the Heinrichs-Weikamp (OSTC 2, OSTC 3) and
|
||
Suunto Vyper (Stinger, Mosquito, D3, Vyper, Vytec,
|
||
Cobra, Gekko and Zoop) family of dive computers are supported. A large number of settings of these dive computers
|
||
can be read and changed to different values. As a first step, ensure that the appropriate hardware driver
|
||
is installed for the dive computer (also required for downloading dives) and that the device name of the dive computer is known.
|
||
See <a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">APPENDIX A</a> for information on how to do this.</p></div>
|
||
<div class="paragraph"><p>Once the dive computer is connected to the <em>Subsurface</em> computer, select <em>File → Configure dive
|
||
computer</em> from the <em>Main Menu</em>. Provide the appropriate device name in the text box at the
|
||
top of the configuration panel and select the appropriate dive
|
||
computer model from the panel on the left-hand (see image below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Configure_dc_f20.jpg" alt="FIGURE: Configure dive computer" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Using the appropriate buttons on the configuration panel, the following actions can be performed:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Retrieve available details</strong>. This loads the existing configuration from the dive computer
|
||
to <em>Subsurface</em>, showing it in the configuration panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Save changes to device</strong>. This changes the configuration of the
|
||
dive computer to correspond to the information shown in the configuration panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Backup</strong>. This saves the configuration data to a file. <em>Subsurface</em> asks for
|
||
a file location and file name for the saved information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Restore backup</strong>. This loads the information from a backup file and displays it
|
||
in the configuration panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Update firmware</strong>. If new firmware is available for the dive computer, this is
|
||
loaded into the dive computer.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_Preferences">12. Setting user <em>Preferences</em> for <em>Subsurface</em></h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>There are several user-definable settings within <em>Subsurface</em>, found by selecting
|
||
<em>File → Preferences</em>. The settings are performed in
|
||
seven groups: <strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>, <strong>Facebook</strong> and <strong>Georeference</strong>,
|
||
all of which
|
||
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>. If <strong>Discard</strong> is selected, changes to the preferences
|
||
are not saved.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_defaults">12.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_f20.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 needs to specify the directory and
|
||
file name of one’s
|
||
electronic dive log book. This is a file with filename extension of either <em>.xml</em> or <em>ssrf</em>. When
|
||
launched, <em>Subsurface</em> will automatically load the specified dive log book. There are three options:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>No default file</em>: When checked, <em>Subsurface</em> does not automatically load a dive log at startup.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Local default file</em>: When checked, <em>Subsurface</em> automatically loads a dive log from the local hard disk
|
||
as described above.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Cloud storage default file</em>: When checked, <em>Subsurface automatically loads the dive log from the cloud
|
||
device that was initialised using the <strong>Preferences</strong> _Network</em> tab (see below).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide
|
||
dives that he/she doesn’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>: Specify the default cylinder listed in
|
||
the <strong>Equipment</strong> tab of the <strong>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, and a 0 value representing no animation
|
||
at all.
|
||
</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">12.2. Units</h3>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref2_f20.jpg" alt="FIGURE: Preferences Units page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Here users 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, one 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 class="paragraph"><p>Irrespective
|
||
of the above settings, dive time measurements can be either in seconds or minutes.
|
||
Choose the appropriate option. GPS coordinates can be represented either as
|
||
traditional coordinates (degrees, minutes, seconds) or as decimal degrees
|
||
Choose the appropriate option.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_graph">12.3. Graph</h3>
|
||
<div class="imageblock" id="S_CCR_options" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref3_f20.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, enabled by 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 the specified threshold level, the graph is
|
||
highlighted in red, indicating that the particular partial pressure threshold has been exceeded.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
_Max pO<sub>2</sub> is used for calculating the MOD when displaying the maximum operative depth (MOD)
|
||
for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Draw dive computer reported ceiling red</em>: This checkbox allows exactly what it says. By default
|
||
the computer reported ceiling is shown in white.
|
||
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> because of the different algorithms and
|
||
gradient factors, 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 if 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>: If this box is checked, the <strong>Dive Profile</strong> panel contains a grey line that indicates
|
||
the mean depth of the dive up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before the
|
||
ascent.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Misc</strong>:
|
||
</p>
|
||
<div class="ulist" id="GradientFactors_Ref"><ul>
|
||
<li>
|
||
<p>
|
||
Gradient Factors (GFLow and GFHigh):* 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 70/90 are considered
|
||
harsh. Checking the <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>
|
||
<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>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CCR: Show setpoints when viewing pO2:</em> With this checkbox ativated, the pO<sub>2</sub>
|
||
graph on the dive profile has an overlay in red which inticates the CCR setpoint
|
||
values. See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>CCR: Show individual O<sub>2</sub> sensor values when viewing pO<sub>2</sub>:</em> Show the pO<sub>2</sub>
|
||
values associated with each of the individual oxygen sensors of a CCR system.
|
||
See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Configuring dive planning using rebreather equipment:</strong>
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Default CCR setpoint for dive planning:</em> Specify the O<sub>2</sub> setpoint for a
|
||
CCR dive plan. This determines the pO<sub>2</sub> maintained
|
||
during a particular dive. Setpoint changes during the dive can be added via the
|
||
profile context menu.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>pSCR O<sub>2</sub> metabolism rate:</em> For a semiclosed rebreather (pSCR) system, this is the
|
||
volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning
|
||
and decompression calculations.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>pSCR ratio:</em> For pSCR equipment the dump ratio is the ratio of gas released to the
|
||
environment to that of the gas recirculated to the diver. Set this value for a
|
||
pSCR dive plan. A 1:10 ratio is commonly used.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_language">12.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_f20.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 operating system. If this is for some reason
|
||
undesirable one 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. <strong>This particular preference requires a restart of <em>Subsurface</em> to take
|
||
effect</strong>.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_network">12.5. Network</h3>
|
||
<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources on the Internet.
|
||
This is important, for instance, when <em>Subsurface</em> needs to communicate with Internet
|
||
services such as Cloud storage or the <a href="#S_Companion"><em>Subsurface Companion app</em></a>. 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.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref5_f20.jpg" alt="FIGURE: Preferences Network page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>This dialogue has three sections:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Proxy type</em>:
|
||
If a proxy server is used for Internet access, 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 are required so that <em>Subsurface</em> can automatically pass
|
||
through the proxy server to access the Internet. This information is usually obtained
|
||
from one’s ISP.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface cloud storage</em>: To store one’s dive log in the cloud, a valid email address
|
||
and password are required. This allows <em>Subsurface</em> to email security information
|
||
regarding cloud storage to a user, and to set up the cloud storage appropriately.
|
||
Two additional options are given:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Sync to cloud in the background</em>: This option allows saving of dive information to the cloud storage
|
||
while the user performs other tasks within <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Save password locally</em>: This allows local storage of the cloud storage password. Note that this
|
||
information is saved in raw text form, not encoded in any way.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface web service</em>: 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>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Facebook">12.6. Facebook Accesss</h3>
|
||
<div class="paragraph"><p>This panel allows one to log into a Facebook account in order to transfer information
|
||
from Subsurface to Facefook.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>If one provides a valid Facebook userID and password, a
|
||
connection to Facebook is created. The connection to Facebook is closed when one
|
||
closes down Subsurface. Currently the checkbox labelled "Keep me logged in to Subsurface",
|
||
on the login screen has no effect.
|
||
See the section <a href="#S_facebook">Exporting dive profiles to Facebook</a>
|
||
for more information.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_georeference">12.7. Georeference</h3>
|
||
<div class="paragraph"><p><em>Subsurface</em> provides a geo-lookup service (that is, given the coordinates of a dive site (derived from
|
||
a click on the <strong>Dive Map panel</strong> at the bottom right of the <em>Subsurface</em> window, or from a GPS instrument or
|
||
from the <em>Subsurface</em> Companion app), a lookup on the Internet is performed to find
|
||
the name of the closest known location. Obviously this function only works if <em>Subsurface</em> has an
|
||
Internet connection. The preference of the dive site name can be configured, e.g. <em>Country/State/City</em>
|
||
or <em>City/State/Country</em> (see image below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_DivePlanner">13. 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">13.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 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_f20.jpg" alt="FIGURE: Dive planner startup window" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_open_circuit_dives">13.2. Open circuit dives</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Towards the centre bottom of the planner (circled in blue in the image above) is a dropbox with three options. Select the appropriate one of these:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Open Circuit (the default)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
CCR
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
pSCR
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Choose the Open Circuit option.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the top left-hand area of the planning screen, ensure that the constant dive parameters are
|
||
appropriate. These are: Start date and time of the intended 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 a sea-level 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 cylinder is assumed to contain 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 right-hand of the dialogue.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The profile of the planned dive can be created in two ways:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Drag the waypoints
|
||
(the small white circles) on the existing dive profile in a way to represent the dive. Additional
|
||
waypoints can be created by double-clicking the existing dive profile. Waypoints can be deleted
|
||
by right-clicking a particular waypoint and selecting the <em>delete</em> item from the resulting
|
||
context menu.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The most efficient way to create a dive profile is to enter the appropriate values into the table
|
||
marked <em>Dive planner points</em>. The first line of the table represents the duration and the final
|
||
depth of the descent from the surface. Subsequent segments describe the bottom phase of the dive.
|
||
The <em>CC set point</em> column is only relevant for closed circuit divers.
|
||
The ascent is usually not specified because this is what the planner is supposed to calculate.
|
||
Add additional segments to the profile by selecting the "+" icon at the top right hand of the
|
||
table. Segments entered into the <em>Dive planner points</em> table automatically appear in the <strong>Dive
|
||
Profile</strong> diagram.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect3">
|
||
<h4 id="_recreational_dives">13.2.1. Recreational dives</h4>
|
||
<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL).
|
||
It computes the maximal time a diver can stay at the current depth without incurring any mandatory decompression
|
||
stops and without using more than the existing gas (minus a reserve). The planner automatically takes
|
||
into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a
|
||
way that can take into account previous dives. Why use a dive planner for recreational dives? Using
|
||
recreational dive tables, the maximum depth of a dive is taken into account. However, few dives are
|
||
undertaken at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means
|
||
that dive tables overestimate the nitrogen load incurred during previous dives. The <em>Subsurface</em>
|
||
dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives,
|
||
in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets <em>credit</em>
|
||
in terms of nitrogen loading for not remaining at maximum depth during previous dives, enabling planning of a
|
||
longer subsequent dive. For the planner to work it is therefore crucial to upload all previous dives
|
||
onto <em>Subsurface</em> before performing dive planning.</p></div>
|
||
<div class="paragraph"><p>To plan a dive, the appropriate settings need to be defined.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Ensure that the date and time is set to that of the intended dive. This allows calculation of
|
||
the nitrogen load incurred during previous dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Immediately under the heading <em>Planning</em> are two checkboxes <em>Recreational</em> and <em>Safety Stop</em>.
|
||
Check these two boxes.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Then define the cylinder size,
|
||
the gas mixture (air or % oxygen) and the starting cylinder pressure in the top left-hand
|
||
section of the planner under <em>Available gases</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The planner calculates whether the specified cylinder contains enough air/gas to complete
|
||
the planned dive. In order for this to be realistic, under <em>Gas options</em>, specify an appropriate
|
||
surface air consumption (SAC) rate for <em>Bottom SAC</em>. Suitable values are between 15 l/min and 30 l/min,
|
||
with novice divers or difficult dives requiring SAC rates closer to 30l/min.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Define the amount of gas that the cylinder must have at the end of the bottom section of the
|
||
dive just before ascent. A value of 50 bar is often used. The reason for this reserve gas is to provide for the possible
|
||
need need to bring one’s buddy to the surface using gas sharing. How much gas is used in
|
||
sharing depends on the depth of the ascent. This can be a bit hard to estimate, so most agencies assume a
|
||
fixed amount of gas, or actually of pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em> can do better
|
||
because it knows about the ascent and that is why we add the amount of gas during the ascent (i.e. the "deco gas“).
|
||
Subsurface still uses a fixed pressure „reserve“ but that is supposed to be for the additional gas used around the realisation
|
||
that there is a problem and one’s pulse rate goes up when one starts to buddy breathe. This reserve amount is user configurable.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Define the depth of the dive by dragging the waypoints (white dots) on the dive profile or
|
||
(even better) defining the appropriate depths using the table under <em>Dive planner points</em> as
|
||
desribed under the previous heading. If
|
||
this is a multilevel dive, set the appropriate dive depths to represent the dive plan by adding
|
||
waypoints to the dive profile or by adding appropriate dive planner points to the <em>Dive Planner Points</em>
|
||
table. <em>Subsurface</em> will automatically extend the bottom section of the dive to the maximum
|
||
duration within the no-decompression limits (NDL).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The ascent speed can be changed. The default ascent speeds are those considered safe for recreational
|
||
divers.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The dive profile in the planner indicates the maximum dive time within no-deco limits using the
|
||
Bühlmann ZH-L16 algorithm and the gas and depth settings specified as described above. The <em>Subsurface</em> planner
|
||
allows rapid assessment of dive duration as a function of dive depth, given the nitrogen load incurred during previous dives. The
|
||
dive plan includes estimates of the amount of air/gas used, depending on the cylinder settings specified
|
||
under <em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive duration shown is the
|
||
true no-deco limit (NDL) without taking into account gas used during the dive. If the surface above the dive profile is RED
|
||
it means that recreational dive limits are exceeded and either the dive duration or the dive depth needs to be reduced.</p></div>
|
||
<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30 metres. Although the no-deco limit (NDL) is 23
|
||
minutes, the duration of the dive is limited by the amount of air in the cylinder, reflected by the information in the
|
||
text box at the bottom right of the panel that requires sufficient air for buddy-sharing during the ascent.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_non_recreational_open_circuit_dives_including_decompression">13.2.2. Non-recreational open circuit dives, including decompression</h4>
|
||
<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or using multiple breathing gases.
|
||
Such dives are planned in three stages:</p></div>
|
||
<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is performed by specifying the rates for descent and ascent,
|
||
as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings <em>Rates</em> and <em>Planning</em>
|
||
to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B
|
||
model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low
|
||
need to be specified. 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 values 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.
|
||
** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.</p></div>
|
||
<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified on a scale of 0 (least conservative) to 4 (most conservative).
|
||
This model tends to give deco stops at deeper levels than the Bühlmann model and often results in slightly shorter
|
||
dive durations than the Bühlmann model. When selecting one of these models, keep in mind that they are NOT exact physiological models but
|
||
only mathematical models that appear to work in practice.</p></div>
|
||
<div class="paragraph"><p>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>
|
||
<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 that discusses both the Bühlmann deco model and the VPM-B model.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><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 by a light grey line on the dive profile. 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></div>
|
||
<div class="paragraph"><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 increased to 1.6 bar.</p></div>
|
||
<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary consideration. One needs to keep within the limits of the amount of gas within the dive
|
||
cylinder(s), allowing for an appropriate margin for a 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 15-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 calculates the total volume of gas used during the dive and issues 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></div>
|
||
<div class="paragraph"><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 bue 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. It is NOT necessary to specify the ascent part of the dive
|
||
since the planner calculates this, based on the settings that have been specified.
|
||
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></div>
|
||
<div class="paragraph"><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 <em>Available Gases</em> table.
|
||
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. A waypoint can be moved by selecting that waypoint and by using the arrow keys.
|
||
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></div>
|
||
<div class="paragraph"><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></div>
|
||
<div class="paragraph"><p>A non-zero value in the "CC set point" column of the table of dive planner points
|
||
indicates a valid setpoint for oxygen partial pressure and that the segment
|
||
is dived using a closed circuit rebreather (CCR). If the last manually entered
|
||
segment is a CCR segment, the decompression phase is computed assuming the diver
|
||
uses a CCR with the specified set-point. If the last segment (however
|
||
short) is on open circuit (OC, indicated by a zero set-point) the
|
||
decompression is computed in OC mode. The planner only considers gas
|
||
changes in OC mode.</p></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_f20.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 top middle of the planner. The saved dive plan will appear
|
||
in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
|
||
<div class="paragraph"><p><strong>The dive plan details</strong></p></div>
|
||
<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>Notes</em> section of the dive planner, immediately to the left
|
||
of the <em>Dive Plan Details</em>. If a <em>Verbatim dive plan</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>
|
||
<div class="sect2">
|
||
<h3 id="_planning_pscr_dives">13.3. Planning pSCR dives</h3>
|
||
<div class="paragraph"><p>To plan a dive using a passive semi-closed rebreather (pSCR), select <em>pSCR</em> rather than
|
||
<em>Open circuit</em> in the dropdown list.
|
||
The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Graph</em>
|
||
from the main menu, where the gas consumption calculation takes into account the pSCR dump
|
||
ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop
|
||
accross the mouthpiece of the rebreather into account. If the
|
||
pO<sub>2</sub> drops below what is considered a save value, a warning appears in the <em>Dive plan
|
||
details</em>. A typical pSCR configuration is with a single cylinder and one or more bail-out
|
||
cylinders. Therefore the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables
|
||
are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints
|
||
are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive is comparable
|
||
to that of the CCR dive below, but note the longer ascent duration due to the lower oxygen
|
||
in the loop due to the oxygen drop across the mouthpiece of the pSCR equipment.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_planning_ccr_dives">13.4. Planning CCR dives</h3>
|
||
<div class="paragraph"><p>To plan a dive using a closed circuit rebreather, select the <em>CCR</em> option in the dropdown
|
||
list, circled in blue in the image below.</p></div>
|
||
<div class="paragraph"><p><strong>Available gases</strong>: In the <em>Available gases</em> table, enter the cylinder information for the
|
||
diluent cylinder and for any bail-out cylinders. Do NOT enter the information for the oxygen
|
||
cylinder since it is implied when the <em>CCR</em> dropdown selection is made.</p></div>
|
||
<div class="paragraph"><p><strong>Entering setpoints</strong>: Specify a default setpoint in the Preferences tab, by selecting <em>File → Preferences → Graph</em> from
|
||
the main menu. All user-entered segments in the <em>Dive planner points</em> table
|
||
use the default setpoint value. Then, different setpoints can be specified for dive segments
|
||
in the <em>Dive planner points</em> table. A zero setpoint
|
||
means the diver bails out to open circuit mode for that segment. The decompression is always calculated
|
||
using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a
|
||
CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression
|
||
algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but,
|
||
of course, this is calculated for bail out ascents.</p></div>
|
||
<div class="paragraph"><p>The dive profile for a CCR dive may look something like the image below.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Note that, in the <em>Dive plan details</em>, the gas consumption for a CCR segment is not calculated,
|
||
so gas consumptions of 0 litres are the norm.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Replan">13.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 class="paragraph"><p>In addition there is the option "Save new". This keeps the original
|
||
planned dive and adds a (possibly modified) copy to the dive list. If
|
||
that copy is saved with the same start time as the original, the two
|
||
dives are considered two versions of the same dive and do not
|
||
influence other each during decompression calculation (see next section).</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_planning_for_repetitive_dives">13.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">13.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>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 or by copy and paste to a word processor.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_description_of_the_subsurface_main_menu_items">14. 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">14.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>Open cloud storage</em> - Open the dive log previously saved in <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Save</em> - Save the dive logbook that is currently open.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Save to cloud storage</em> - Save the current dive log to <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
|
||
</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>
|
||
<a href="#S_FindMovedImages"><em>Find moved images</em></a> - If photos taken during dives have been moved to
|
||
a different disk or directory, locate them and link them to the appropriate dives.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Configure"><em>Configure dive computer</em></a> - Edit the configuration of a dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Quit</em> - Quit <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_import">14.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 web 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">14.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>
|
||
<em>Edit dive</em> - Edit a dive of which the profile was entered by hande and not from a dive computer.
|
||
</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>Edit dive in planner</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>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Filter"><em>Filter divelist</em></a> - Select only some dives, based on specific tags or dive criteria.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_view">14.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>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> - If a single dive was logged from more than one dive computer, switch to data from
|
||
previous dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Next DC</em> - Switch to next dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Full Screen</em> - Toggles Full Screen mode.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_share_on">14.5. Share on</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Facebook"><em>Facebook</em></a> - Share the currently selected dive on your Facebook timeline.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_help">14.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-divelog.org/"><em>Subsurface</em> web site</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_UserSurvey"><em>User survey</em></a> - Help to make <em>Subsurface</em> even better by taking part in our user survey
|
||
or by completing another survey if your diving habits have changed.
|
||
</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">15. 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">15.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">15.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>
|
||
<li>
|
||
<p>
|
||
Under some circumstances this change takes only effect (eg. on Ubuntu) after
|
||
one logs out and then logs in again.
|
||
</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">15.3. Manually 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="sect3">
|
||
<h4 id="_on_windows_2">15.3.1. On Windows:</h4>
|
||
<div class="paragraph"><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 (which should be 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>
|
||
<div class="sect3">
|
||
<h4 id="_on_macos">15.3.2. On MacOS:</h4>
|
||
<div class="paragraph"><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>
|
||
<div class="sect3">
|
||
<h4 id="_on_linux">15.3.3. On Linux</h4>
|
||
<div class="paragraph"><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 on the right of the toolbar at the top of the screen.
|
||
Users have reported difficulties with some Bluetooth controllers. If you have an onboard controller,
|
||
try that first. It is simplest if you remove any USB Bluetooth dongles. If you have a USB dongle that
|
||
came with your dive computer, try that before any others.</p></div>
|
||
<div class="paragraph"><p>Setting up a connection to download dives from your Bluetooth-enabled device, such as the
|
||
<em>Shearwater Petrel</em>, is not yet an automated process and will generally require the command prompt.
|
||
It is essentially a three step process.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Enable the Bluetooth controller and pair your dive computer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Establish an RFCOMM connection
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Download the dives with Subsurface
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Ensure the dive computer is in upload mode. On the <em>Shearwater Petrel</em> and <em>Petrel 2</em>,
|
||
cycle through the menu, select <em>Dive Log</em>, then <em>Upload Log</em>. The display will read <em>Initializing</em>, then
|
||
<em>Wait PC 3:00</em> and will countdown. Once the connection is established, the display reads <em>Wait CMD …</em>
|
||
and the countdown continues. When downloading the dive from Subsurface, the display reads <em>Sending</em> then
|
||
<em>Sent Dive</em>.</p></div>
|
||
<div class="paragraph"><p>To establish the connection, establish root access through <code>sudo</code> or <code>su</code>.
|
||
The correct permission is required to download the dives in the computer. On most Linux systems this means becoming
|
||
a member of the dialout group (This is identical as for many dive computers using a Linux USB port, described
|
||
in the previous section). On the command terminal, enter:</p></div>
|
||
<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div>
|
||
<div class="paragraph"><p>Then log out and log in for the change to take effect.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="_enabling_the_bluetooth_controller_and_pairing_your_dive_computer">Enabling the Bluetooth controller and pairing your dive computer</h5>
|
||
<div class="paragraph"><p>Attempt to set up the Bluetooth controller and pair your dive computer using the graphical
|
||
environment of the operating system. After setting the dive computer to upload mode, click the Bluetooth icon in the system tray
|
||
and select <em>Add new device</em>. The dive computer should appear. If asked for a password, enter 0000.
|
||
Write down or copy the MAC address of your dive computer - this needed later and should be in the form 00:11:22:33:44:55.</p></div>
|
||
<div class="paragraph"><p>If the graphical method didn’t work, pair the device from the command line. Open a terminal
|
||
and use <code>hciconfig</code> to check the Bluetooth controller status</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>$ hciconfig
|
||
hci0: Type: BR/EDR Bus: USB
|
||
BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
|
||
*DOWN*
|
||
RX bytes:504 acl:0 sco:0 events:22 errors:0
|
||
TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, connected as hci0.
|
||
Its status is <em>DOWN</em>, i.e. not powered. Additional controllers will appear as hci1, etc.
|
||
If there is not a Bluetooth dongle plugged in upon booting the computer, hci0 is probably the onboard.
|
||
Now power on the controller and enable authentication:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted)
|
||
hciconfig
|
||
hci0: Type: BR/EDR Bus: USB
|
||
BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
|
||
*UP RUNNING PSCAN AUTH*
|
||
RX bytes:1026 acl:0 sco:0 events:47 errors:0
|
||
TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Check that the status now includes <code><em>UP</em>, <em>RUNNING</em> AND <em>AUTH</em></code>.</p></div>
|
||
<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to off the unused controller(s). For example, for <code>hci1</code>:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>sudo hciconfig hci1 down</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Next step is to <em>trust</em> and <em>pair</em> the dive computer. On distros with Bluez 5, such as Fedora 22,
|
||
one can use a tool called <code>blutootctl</code>, which will bring up its own command prompt.</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>bluetoothctl
|
||
[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]
|
||
[bluetooth]# agent on
|
||
Agent registered
|
||
[bluetooth]# default-agent
|
||
Default agent request successful
|
||
[bluetooth]# scan on <----now set your dive computer to upload mode
|
||
Discovery started
|
||
[CHG] Controller 01:23:45:67:89:AB Discovering: yes
|
||
[NEW] Device 00:11:22:33:44:55 Petrel
|
||
[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address
|
||
[CHG] Device 00:11:22:33:44:55 Trusted: yes
|
||
Changing 00:11:22:33:44:55 trust succeeded
|
||
[bluetooth]# pair 00:11:22:33:44:55
|
||
Attempting to pair with 00:11:22:33:44:55
|
||
[CHG] Device 00:11:22:33:44:55 Connected: yes
|
||
[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345
|
||
[CHG] Device 00:11:22:33:44:55 Paired: yes
|
||
Pairing successful
|
||
[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>If asked for a password, enter 0000. It’s ok if the last line says <em>Connected: no</em>. The important part
|
||
is the line above, <code>Pairing successful</code>.</p></div>
|
||
<div class="paragraph"><p>If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), there is probably not a
|
||
<code>bluetoothctl</code>, but a script called <code>bluez-simple-agent</code> or just <code>simple-agent</code>.</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>hcitool -i hci0 scanning
|
||
Scanning ...
|
||
00:11:22:33:44:55 Petrel
|
||
bluez-simple-agent hci0 00:11:22:33:44:55</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Once ther dive computer is pired, set up the RFCOMM connection</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_establishing_the_rfcomm_connection">Establishing the RFCOMM connection</h5>
|
||
<div class="paragraph"><p>The command to establish an RFCOMM connection is:</p></div>
|
||
<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<code><controller></code> is the Bluetooth controller, <code>hci0</code>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<code><dev></code> is the RFCOMM device file, <code>rfcomm0</code>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<code><bdaddr></code> is the dive computer’s MAC address, <code>00:11:22:33:44:55</code>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<code>[channel]</code> is the dive computer’s Bluetooth channel we need to connect to.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>If one omits it, channel 1 is assumed. Based on a limited number of user reports,
|
||
the appropriate channel for the dive computer is probably:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Shearwater Petrel 2</em>: channel 5
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Shearwater Petrel 1</em>: channel 1
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>E.g. to connect a <em>Shearwater Petrel 2</em>, set the dive computer to upload mode and enter:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>This gives the response:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5
|
||
Press CTRL-C for hangup</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive computer to upload mode and enter:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted)
|
||
Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
|
||
Press CTRL-C for hangup</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>If the specific channel the dive computer needs is not known, or the channel in the list above doesn’t
|
||
work, the command <code>sdptool records</code> should help determine the appropriate channel. The output
|
||
below is for a <em>Shearwater Petrel 2</em>.</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>sdptool -i hci0 records 00:11:22:33:44:55
|
||
Service Name: Serial Port
|
||
Service RecHandle: 0x10000
|
||
Service Class ID List:
|
||
"Serial Port" (0x1101)
|
||
Protocol Descriptor List:
|
||
"L2CAP" (0x0100)
|
||
"RFCOMM" (0x0003)
|
||
Channel: 5</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>For a Bluetooth dive computer not in the list above, or if the channel listed is not correct, please
|
||
let the Subsurface developers know on the user forum or the developer mailing list <em>subsurface@subsurface-divelog.org</em>.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_download_the_dives_with_subsurface">Download the dives with Subsurface</h5>
|
||
<div class="paragraph"><p>After establishing the RFCOMM connection and while the dive computer’s upload mode countdown is still running, go to_Subsurface_, select <em>Import→Import from dive computer</em> and enter appropriate Vendor (e.g. <em>Shearwater</em>), Dive Computer (<em>Petrel</em>), Device or Mount Point (<em>/dev/rfcomm0</em>) and click <em>Download</em>.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">16. APPENDIX B: Dive Computer specific information for importing dive data.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_ImportUemis">16.1. Importing from 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">16.2. Importing from 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>. Windows-based IrDA
|
||
drivers for the Uwatec can also be downloaded from the ScubaPro web site, drivers being located on
|
||
the download page for the ScubaPro SmartTrak software.</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">16.3. Importing 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="S_ImportingXDeep">16.4. Importing from xDEEP BLACK</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/HW_xdeepblack.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Each dive has to be individually saved as UDDF file using "Export UDDF" option in BLACK’s logbook menu.
|
||
When mounted as a USB drive UDDF files are available in LOGBOOK directory.
|
||
Note: The xDEEP BLACK saves NDL time but 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 xDEEP BLACK.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importing_from_shearwater_predator_petrel_using_bluetooth">16.5. Importing from Shearwater Predator/Petrel using Bluetooth</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/predator.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Specific instructions for downloading dives using Bluetooth are given in the section above, <a href="#S_Bluetooth"><em>Connecting Subsurface to a Bluetooth-enabled dive computer</em></a>.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_PoseidonMkVI">16.6. Importing from 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 proprietary 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_from_apd_inspiration_evolution_ccr">16.7. Importing from APD Inspiration/Evolution 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>
|
||
Download the dive using <em>AP Communicator</em>.
|
||
</p>
|
||
</li>
|
||
<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>
|
||
With 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) or 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 <em>.apd</em>
|
||
</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 (labled <em>Filter:</em>), select "APD log viewer".
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
On the list of file names select the <em>.apd</em> file that has been created above. An import
|
||
dialogue opens indicating the default settings for the data in the <em>.apd</em> file. If any changes are required,
|
||
do this as for <a href="#S_ImportingCSVDives">CSV imports</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The top left hand dropdown box in the import panel allows one to select the APD dive computer
|
||
for which the dive log needs to be imported. The default it is DC1, <em>i.e.</em> the
|
||
first of the two dive computers the APD uses. It is possible to sequentially
|
||
import the data for both dive computers by first importing CD1 and then DC2.(<strong>Hint</strong>: The logs
|
||
for the two dive computers are viewed by selecting <em>View → Next DC</em> from
|
||
the Main Menu after the uploading has been completed)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click the <em>Ok</em> button at the bottom of the import panel.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>. The dive computer-generated ceiling
|
||
generated by the Inspiration can be viewed by selecting the appropriate
|
||
button on the left of the <strong>Dive Profile</strong>. Cylinder pressure data are not logged
|
||
by the APD equipment but can be manually entered in the <em>Equipment</em> Tab.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">17. 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">17.1. Exporting from <strong>Suunto Divemanager (DM3, DM4 or DM5)</strong></h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/suuntologo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">DiveManager is a MS Windows application for Suunto dive computers.
|
||
Divemanager 3 (DM3) is an older version of the Suunto software. More recent
|
||
Suunto dive computers use Divemanager version 4 or 5 (DM4 or DM5). The
|
||
different 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) and Divemanager 5 (DM5):</strong></p></div>
|
||
<div class="paragraph"><p>DM4 and DM5 use identical mechanisms for exporting dive logs.
|
||
To export a divelog from Divemanager one needs to locate the DM4/DM5 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 (or DM5) database:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Start Suunto DM4/DM5
|
||
</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 or DM5.db
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Making a backup copy of the Suunto DM4/DM5 database:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Start Suunto DM4/DM5
|
||
</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 (or DM5) 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 (or DM5.bak)
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_exporting_from_atomic_logbook">17.2. Exporting from Atomic Logbook</h3>
|
||
<div class="admonitionblock" id="Atomic_Export">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/atomiclogo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Atomic Logbook is a Windows software by Atomic Aquatics. It allows
|
||
downloading of dive information from Cobalt and Cobalt 2 dive computers.
|
||
The divelog is kept in a SQLite database at
|
||
C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. This file can
|
||
be directly imported to Subsurface.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_exporting_from_mares_dive_organiser_v2_1">17.3. 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">17.4. Exporting from <strong>DivingLog 5.0 and 6.0</strong></h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/divingloglogo.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">The best way to bring your logs from DivingLog to Subsurface is to
|
||
convert the whole database. This is because other export formats do not
|
||
include all the details, and we would lack e.g. gas switches and
|
||
information of what units are used. With database import, all this
|
||
information is included and readily available for us.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface, do the following:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
In DivingLog open the <em>File → Export → SQLite</em> menu
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select <em>Settings</em> button
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Set the <em>RTF2Plaintext</em> to <em>true</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Close the Settings dialog
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>Export</em> button and select the filename
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Once this is done, open the saved database file with Subsurface and the
|
||
dives are automatically converted to our own format. Last step to do is
|
||
save the log file in Subsurface.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_d_exporting_a_spreadsheet_to_csv_format">18. APPENDIX D: Exporting a spreadsheet to CSV format</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph" id="S_Appendix_D"><p>Many divers keep a diving log in some form of a digital file, commonly a spreadsheet
|
||
with various fields of information. These logs can be easily imported into <em>Subsurface</em> after the
|
||
spreadsheet is converted in a .CSV file.
|
||
This section explains the procedure to convert a diving logbook stored in a spreadsheet
|
||
to a .CSV file that will later be imported from <em>Subsurface</em>.
|
||
Creating a .CSV is a straightforward task, although the procedure is somewhat different
|
||
according to which spreadsheet program is used.</p></div>
|
||
<div class="paragraph"><p>The first step is to organize the diving data in the spreadsheet, so that the first row
|
||
contains the names (or titles) of each column and the information for each dive is stored in a single row.
|
||
<em>Subsurface</em> supports many data items (Dive #, Date,
|
||
Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight and Tags).
|
||
The user can organize dive data following a few simple rules:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Duration: the format should be minutes:seconds.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Unit system: only one unit system should be used (i.e., no mixture between imperial and metric units)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Tags and buddies: values should be separated using a comma.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
GPS position: users must use decimal degrees, e.g. 30.22496 30.821798
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="sect2">
|
||
<h3 id="_em_libreoffice_calc_em_and_em_openoffice_calc_em">18.1. <em>LibreOffice Calc</em> and <em>OpenOffice Calc</em></h3>
|
||
<div class="paragraph"><p>These are open source spreadsheet applications forming parts of larger open source office suite applications. The user interaction with <em>LibreOffice</em> and <em>OpenOffice</em> is very similar.
|
||
In Libreoffice Calc the time format should be set to minutes:seconds - [mm]:ss and dates should be set to one of: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. A typical dive log may look like this:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LOffice_spreadsheetdata.jpg" alt="FIGURE: Spreadsheet data" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>To export the data as a .CSV file from within LibreOffice click <em>File → Save As</em>. On the dialogue that comes up, select the <em>Text CSV (.csv)</em> as the file type and select the option <em>Edit filter settings</em>.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LOffice_save_as_options.jpg" alt="FIGURE: Save as options" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>After selecting <em>Save</em>, select the appropriate field delimiter (choose <em>Tab</em> to prevent conflicts with the comma when using this as a decimal point), then select <em>OK</em>.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LOffice_field_options.jpg" alt="FIGURE: Field options" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>One can double check the .CSV file by opening it with a text editor, and then import the dive data as explained on the section <a href="#S_ImportingCSVDives">Importing CSV dives</a>.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_microsoft_em_excel_em">18.2. Microsoft <em>Excel</em></h3>
|
||
<div class="paragraph"><p>The field delimiter (called "<em>list separator</em>" in Microsoft manuals) is not accessible
|
||
from within <em>Excel</em> and needs to be set through the <em>Microsoft Control Panel</em>. After changing the
|
||
separator character, all software on the Windows machine use the new character as a separator.
|
||
One can change the character back to the default character by following the same procedure, outlined below.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
In Microsoft Windows, click the <strong>Start</strong> button, and then select <em>Control Panel</em> from the list on the right-hand side.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Open the <em>Regional and Language Options</em> dialog box.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Do one of the following:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
In Windows 7, click the <em>Formats</em> tab, and then click <em>Customize this format</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In Windows XP, click the <em>Regional Options</em> tab, and then click <em>Customize</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Type a new separator in the <em>List separator</em> box. To use a TAB-delimited file, type the word TAB in the box.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Click <em>OK</em> twice.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Below is an image of the <em>Control Panel</em>:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Win_SaveCSV2.jpg" alt="FIGURE: Win List separator" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>To export the dive log in CSV format:</p></div>
|
||
<div class="paragraph"><p>With the dive log opened in <em>Excel</em>, select the round Windows button at the top left, then <em>Save As</em>.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Win_SaveCSV1.jpg" alt="FIGURE: Excel save as option" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Click on the left-hand part of the <em>Save as</em> option, NOT on the arrow on the right-hand. This brings up a dialogue for saving the spreadsheet in an alternative format. From the dropdown list at the bottom of the dialogue, marked <em>Save as Type:</em>, select <em>CSV(Comma delimited) (*.CSV)</em>. Ensure that the appropriate folder has been selected to save the CSV file into.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Win_SaveCSV3.jpg" alt="FIGURE: Excel save CSV dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Select the <em>Save</em> button. The CSV-formatted file is saved into the folder that was selected. One can double check the .CSV file by opening it with a text editor, and then import the dive data as explained on the section <a href="#S_ImportingCSVDives">Importing CSV dives</a>.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_APPENDIX_E">19. APPENDIX E: Writing a custom print template</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> provides a mechanism to create or modify templates for printing dive logs in order to
|
||
produce customised printouts of dive logs. Templates, written in HTML as well as a simple
|
||
Grantlee instruction set, are rendered to the print device by <em>Subsurface</em>.</p></div>
|
||
<div class="paragraph"><p>Templates are accessed using the print dialogue (see image <strong>B</strong> below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The buttons under the <em>Template</em> dropdown box allows one to <em>Edit</em>, <em>Delete</em>,
|
||
<em>Import</em> and to <em>Export</em> templates (see image <strong>A</strong> above). New or modified templates are stored as HTML
|
||
files in the same directory as the dive log being processed. In order to create or modify
|
||
a template, select one of the templates from the template dropdown list in the print dialogue
|
||
(see image <strong>B</strong> above). Choose an existing template that resembles the final desired printout. Then select <em>Edit</em>.</p></div>
|
||
<div class="paragraph"><p>The Edit Panel comprises three tabs:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Template1_f22.jpg" alt="FIGURE: template edit dialogue" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>1) The <em>Style</em> tab (image <strong>A</strong> above) controls the font, line spacing and colour template used for printing the dive log.
|
||
The style attributes are editable. Choose one of the four colour palets used for colour printing.</p></div>
|
||
<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colours used for printing the dive log. The colours are highly
|
||
customisable: the <em>Edit</em> buttons in the <em>Colors</em> tab allows choosing abritrary colours for different
|
||
components of the dive log printout.</p></div>
|
||
<div class="paragraph"><p>3) The <em>Template</em> tab of the Edit Panel (see image below) allows creating a template using HTML as well as a few
|
||
Grantlee programming primitives. Grantlee provides the ability to create and format HTML code in
|
||
a highly simple but efficient way (see below). The HTML of the template can be edited and saved. The saved
|
||
template is stored in the same directory as the dive being processed. By default, a <em>Custom</em>
|
||
template is a skeleton with no specific print instructions. The informastion being printed
|
||
needs to be specified and formatted in the by replacing the section marked with:
|
||
"<!-- Template must be filled -→". Writing HTML code with Grantlee instructions allows unlimited
|
||
freedom in determining what is printed an in which way it should be rendered.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>One can adapt any of the existing templates and save it to the dive log directory. The standard templates (e.g. One dive, Six dives, Table) can be modified in this way. After completing the edits, use the <em>Export</em> button in the print
|
||
dialogue to save the new template using a new template name.</p></div>
|
||
<div class="paragraph"><p>To write a custom template the following elements must exist so that the template will be correctly handled and rendered.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_main_dive_loop">19.1. Main dive loop</h3>
|
||
<div class="paragraph"><p><em>Subsurface</em> exports a dive list called (<strong>dives</strong>) to the <em>Grantlee</em> backend. It is possible to iterate over the list as follows:</p></div>
|
||
<div class="literalblock">
|
||
<div class="title">template.html</div>
|
||
<div class="content">
|
||
<pre><code> {% for dive in dives %}
|
||
<h1> {{ dive.number }} </h1>
|
||
{% endfor %}</code></pre>
|
||
</div></div>
|
||
<div class="literalblock">
|
||
<div class="title">output.html</div>
|
||
<div class="content">
|
||
<pre><code> <h1> 1 </h1>
|
||
<h1> 2 </h1>
|
||
<h1> 3 </h1></code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Additional information about <em>Grantlee</em> can be found <a href="http://www.grantlee.org/apidox/for_themers.html">here</a></p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_grantlee_exported_variables">19.2. Grantlee exported variables</h3>
|
||
<div class="paragraph"><p>Only a subset of the dive data is exported:</p></div>
|
||
<div class="tableblock">
|
||
<table rules="all"
|
||
width="100%"
|
||
frame="border"
|
||
cellspacing="0" cellpadding="4">
|
||
<col width="50%" />
|
||
<col width="50%" />
|
||
<tbody>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">number</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive number</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">id</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>int</strong>) unique dive ID, should be used to fetch the dive profile</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">date</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) data of the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">time</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) time of the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">location</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) location of the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">duration</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) duration of the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">depth</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) depth of the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">divemaster</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) divemaster data</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">buddy</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) buddy data</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">airTemp</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) air temperature of dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">waterTemp</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) water temperature of dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">notes</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive notes</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">rating</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive rating ranges from 0 to 5</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">sac</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) sac value</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">tags</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) all dive tags concatenate together</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">gas</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) used gas cylinder</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
<div class="paragraph"><p><em>Subsurface</em> also exports <strong>template_options</strong> data. This data must be used as <em>CSS</em> values to provide a dynamically
|
||
editable template. The exported data is shown in the following table:</p></div>
|
||
<div class="tableblock">
|
||
<table rules="all"
|
||
width="100%"
|
||
frame="border"
|
||
cellspacing="0" cellpadding="4">
|
||
<col width="50%" />
|
||
<col width="50%" />
|
||
<tbody>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">font</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) font family</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">borderwidth</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>int</strong>) border-width value dynamically calculated as 0.1% of the page width with minimum value of 1px</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">font_size</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>double</strong>) size of fonts in vw, ranges between 1.0 and 2.0</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">line_spacing</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>double</strong>) distance between text lines, ranges between 1.0 and 3.0</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color1</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) background color</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color2</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary table cell color</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color3</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary table cell color</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color4</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary text color</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color5</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary text color</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">color6</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) border colors</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
<div class="literalblock">
|
||
<div class="title">template.html</div>
|
||
<div class="content">
|
||
<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre>
|
||
</div></div>
|
||
<div class="literalblock">
|
||
<div class="title">output.html</div>
|
||
<div class="content">
|
||
<pre><code> border-width: 3px;</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Another variable that <em>Subsurface</em> exports is <strong>print_options</strong>. This variable contains a single member:</p></div>
|
||
<div class="tableblock">
|
||
<table rules="all"
|
||
width="100%"
|
||
frame="border"
|
||
cellspacing="0" cellpadding="4">
|
||
<col width="50%" />
|
||
<col width="50%" />
|
||
<tbody>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">grayscale</p></td>
|
||
<td align="left" valign="top"><p class="table">Use <em>CSS</em> filters to convert the page into grayscale (should be added to body style to enable printing grayscale prints)</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
<div class="literalblock">
|
||
<div class="title">template.html</div>
|
||
<div class="content">
|
||
<pre><code> body {
|
||
{{ print_options.grayscale }};
|
||
}</code></pre>
|
||
</div></div>
|
||
<div class="literalblock">
|
||
<div class="title">output.html</div>
|
||
<div class="content">
|
||
<pre><code> body {
|
||
-webkit-filter: grayscale(100%);
|
||
}</code></pre>
|
||
</div></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_defined_css_selectors">19.3. Defined CSS selectors</h3>
|
||
<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses a special <em>CSS</em> selectors to do some searches
|
||
in the HTML output. The <em>CSS</em> selectors in the following table should be added.</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>Selector</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Type</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td>
|
||
<td align="left" valign="top"><p class="table">id</p></td>
|
||
<td align="left" valign="top"><p class="table">is used to fetch the relevant dive profile</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">diveProfile</p></td>
|
||
<td align="left" valign="top"><p class="table">class</p></td>
|
||
<td align="left" valign="top"><p class="table">each div that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">dontbreak</p></td>
|
||
<td align="left" valign="top"><p class="table">class</p></td>
|
||
<td align="left" valign="top"><p class="table">prevents the div with this class to be divided into two pages, this can be used
|
||
in flow layout templates only (when data-numberofdives = 0)</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="./images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Rendering dive profiles is not supported for flow layout templates (when data-numberofdives = 0).</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_special_attributes">19.4. Special attributes</h3>
|
||
<div class="paragraph"><p>There are two ways of rendering- either rendering a specific number of dives in each page or make <em>Subsurface</em> try to
|
||
fit as much dives as possible into one page (<em>flow</em> rendering).</p></div>
|
||
<div class="paragraph"><p>The <strong>data-numberofdives</strong> data attribute is added to the body tag to set the rendering mode</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
render 6 dives per page:
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code> <body data-numberofdives = 6></code></pre>
|
||
</div></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
render as much dives as possible:
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code> <body data-numberofdives = 0></code></pre>
|
||
</div></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="./images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">All CSS units should be in relative lengths only, to support printing on any page size.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_appendix_f_faqs">20. APPENDIX F: FAQs.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_APPENDIX_F">20.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">20.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 class="sect2">
|
||
<h3 id="_some_dive_profiles_are_missing_from_the_download">20.3. Some dive profiles are missing from the download</h3>
|
||
<div class="paragraph" id="DC_HISTORY"><p><em>Question</em>: I cannot download all my dives, only the most recent ones
|
||
even though my dive computer’s manual states that it records history of
|
||
e.g. 999 dives.</p></div>
|
||
<div class="paragraph"><p><em>Answer</em>: Dive history is different than the dive profiles on the log.
|
||
The history only keeps track of the total number of dives and total
|
||
amount of time spent below surface. The logs, on the other hand, store
|
||
the dive profile, but they have limited amount of memory to do so. The
|
||
exact amount of dive profiles that can be stored on the device depend on
|
||
sample interval and duration of the dives. Once the memory is full the
|
||
oldest dives get overwritten with new dives. Thus we are only able to
|
||
download the last 13, 30 or 199 dives.</p></div>
|
||
<div class="paragraph"><p>If you have downloaded your dives to different dive logging software
|
||
before they were overwritten, there is a high chance that Subsurface can
|
||
import these. However, if the logs are only on your dive computer, they
|
||
cannot be salvaged after being over written by new dives.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div id="footnotes"><hr /></div>
|
||
<div id="footer">
|
||
<div id="footer-text">
|
||
Last updated 2015-10-13 08:46:54 PDT
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html>
|