mirror of
https://github.com/subsurface/subsurface.git
synced 2024-11-28 21:20:19 +00:00
7927 lines
377 KiB
Text
7927 lines
377 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; }
|
||
|
||
|
||
@media screen {
|
||
body {
|
||
max-width: 50em; /* approximately 80 characters wide */
|
||
margin-left: 16em;
|
||
}
|
||
|
||
#toc {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
bottom: 0;
|
||
width: 13em;
|
||
padding: 0.5em;
|
||
padding-bottom: 1.5em;
|
||
margin: 0;
|
||
overflow: auto;
|
||
border-right: 3px solid #f8f8f8;
|
||
background-color: white;
|
||
}
|
||
|
||
#toc .toclevel1 {
|
||
margin-top: 0.5em;
|
||
}
|
||
|
||
#toc .toclevel2 {
|
||
margin-top: 0.25em;
|
||
display: list-item;
|
||
color: #aaaaaa;
|
||
}
|
||
|
||
#toctitle {
|
||
margin-top: 0.5em;
|
||
}
|
||
}
|
||
</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">MANUEL UTILISATEUR</span></p></div>
|
||
<div class="paragraph"><p><strong>Auteurs du manuel</strong> : Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,
|
||
Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, Pedro Neves,
|
||
Stefan Fuchs</p></div>
|
||
<div class="paragraph"><p><span class="blue"><em>Version 4.7, octobre 2017</em></span></p></div>
|
||
<div class="paragraph"><p>Bienvenue en tant qu’utilisateur de <em>Subsurface</em>, un programme avancé
|
||
d’enregistrement de plongées (carnet de plongées) avec une bonne
|
||
infrastructure pour décrire, organiser, interpréter et imprimer des plongées
|
||
en scaphandre et en apnée. <em>Subsurface</em> offre de nombreux avantages par
|
||
rapport à d’autres solutions logicielles similaires :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Avez-vous besoin d’une façon d’enregistrer vos plongées utilisant des
|
||
équipements loisirs, même sans utiliser d’ordinateur de plongée ?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Souhaitez-vous inclure facilement les positions GPS des sites de plongées
|
||
dans votre carnet de plongée ?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Utilisez-vous deux marques différentes d’ordinateurs de plongée, chacun avec
|
||
son propre logiciel propriétaire pour télécharger les enregistrements des
|
||
plongées ? Plongez-vous avec un recycleur ou un équipement en circuit ouvert
|
||
ou de loisir ? Utilisez-vous un enregistreur de profondeur et de durée
|
||
Reefnet Sensus avec un ordinateur de plongée ? <em>Subsurface</em> offre une
|
||
interface standard pour télécharger les enregistrements des plongées à
|
||
partir de tous ces équipements de plongée, en enregistrant et en analysant
|
||
ces enregistrements dans un système unique.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Utilisez-vous plus d’un système d’exploitation ? <em>Subsurface</em> est
|
||
intégralement compatible avec Mac, Linux et Windows, ce qui vous permet
|
||
d’accéder à votre carnet de plongées sur chaque système d’exploitation en
|
||
utilisant une application unique.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Utilisez-vous Linux ou Mac mais votre ordinateur de plongée n’a que des
|
||
logiciels pour Windows pour télécharger les informations de plongées (par
|
||
exemple Mares ou scubapro) ? <em>Subsurface</em> fournit un moyen de télécharger et
|
||
d’analyser vos enregistrements de plongées sur d’autres systèmes
|
||
d’exploitation.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Avez-vous besoin d’un planificateur de plongée graphique intuitif qui
|
||
intègre et prend en compte les plongées qui ont déjà été enregistrées ?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Avez-vous besoin d’un moyen d’enregistrer ou de sauvegarder votre carnet de
|
||
plongée sur Internet, vous permettant de visualiser votre carnet depuis
|
||
n’importe où, en utilisant un navigateur Internet ?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Souhaitez-vous pouvoir accéder ou modifier votre carnet de plongée en
|
||
utilisant un smartphone ?
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> est disponible pour Windows (Win 7 ou plus récent, à partir de
|
||
la version 4.6 de <em>Subsurface</em>), les Macs basés sur processeurs Intel (OS/X)
|
||
et de nombreuses distributions Linux. <em>Subsurface</em> peut être compilé pour
|
||
bien plus de plateformes matérielles et d’environnements logiciels où Qt et
|
||
libdivecomputer sont disponibles.</p></div>
|
||
<div class="paragraph"><p>Ce manuel explique comment utiliser le programme <em>Subsurface</em>. Pour
|
||
installer le logiciel, consultez la page <em>Téléchargement</em> sur le
|
||
<a href="https://subsurface-divelog.org/">site web de <em>Subsurface</em></a>. En cas de
|
||
problème, vous pouvez envoyer un e-mail sur
|
||
<a href="mailto:subsurface@subsurface-divelog.org">notre liste de diffusion</a> et
|
||
rapportez les bogues sur <a href="http://trac.hohndel.org">notre bugtracker</a>. Pour
|
||
des instructions de compilation du logiciel et (si besoin) de ses
|
||
dépendances, merci de consulter le fichier INSTALL inclus dans les sources
|
||
logicielles.</p></div>
|
||
<div class="paragraph"><p><strong>Public</strong> : Plongeurs loisirs, apnéistes, plongeurs Tek et plongeurs
|
||
professionnels</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="_utilisation_de_ce_manuel">1. Utilisation de ce manuel</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Lorsqu’il est ouvert depuis <em>Subsurface</em>, ce manuel ne dispose pas de
|
||
contrôles externes pour la pagination ou la sélection des pages
|
||
précédentes. Cependant, deux options sont disponibles:</p></div>
|
||
<div class="paragraph"><p>La fonction <em>RECHERCHE</em> est activée avec le raccourci clavier Contrôle-F ou
|
||
Commande-F. Une boîte de texte apparaît en bas à droite de la fenêtre (voir
|
||
image ci-dessous). Par exemple, entrer le mot "<em>weights</em>" dans la boîte de
|
||
texte de recherche lancera la recherche dans tout le manuel utilisateur. À
|
||
droite de la boîte de recherche se trouvent deux flèches, l’une vers le haut
|
||
l’autre vers le bas. Elles mènent respectivement vers l’occurence précédente
|
||
et suivante du terme recherché.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/UserManualSearch.jpg" alt="User manual functions" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><em>LIEN PRÉCÉDENT/SUIVANT</em>. Naviguez entre les liens (les mots soulignés qui
|
||
vous conduisent vers des sections précises du manuel utilisateur) en
|
||
cliquant-droit sur le texte du manuel. Cela fera apparaître un menu
|
||
contextuel vers les liens PRÉCÉDENTS sélectionnés (voir image
|
||
ci-dessous). Par exemple, si un lien a été sélectionné, l’option <em>Retour
|
||
lien précédent</em> affiche le texte au lien précédent sélectionné (comme le
|
||
fait le bouton Page Précédente d’un navigateur). Inversement, l’option
|
||
<em>Aller au lien suivant</em> navigue vers le texte vu avant l’utilisation de
|
||
l’option <em>Retour lien précédent</em>. L’option <em>Recharger</em> recharge le manuel
|
||
utilisateur complet dans la fenêtre.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/UserManualLinksBack.jpg" alt="User manual functions" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_UserSurvey">2. Le sondage utilisateur</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Dans le but de développer <em>Subsurface</em> pour servir ses utilisateurs de la
|
||
meilleur manière qui soit, il est important d’avoir des informations sur les
|
||
utilisateurs. À l’ouverture de <em>Subsurface</em> après avoir utilisé le logiciel
|
||
pendant une semaine environ, une fenêtre de sondage apparait. Cela est
|
||
complètement optionnel et l’utilisateur contrôle quelles informations sont
|
||
envoyées ou non à l'équipe de développement de <em>Subsurface</em>. Toutes les
|
||
données que l’utilisateur envoie sont utiles et ne seront utilisées que pour
|
||
les futurs développements et modifications du logiciel pour coller au mieux
|
||
aux besoins des utilisateurs de <em>Subsurface</em>. Si vous complétez le sondage
|
||
ou cliquez sur l’option pour ne plus être sondé, cela devrait être la
|
||
dernière communication de ce type que vous recevrez. Cependant, si vos
|
||
habitudes de plongées ou d’utilisation de Subsurface changent, vous pouvez
|
||
envoyer un nouveau sondage en démarrant <em>Subsurface</em> avec l’option
|
||
<em>--survey</em> sur la ligne de commande.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_StartUsing">3. Commencer à utiliser le programme</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>La fenêtre <em>Subsurface</em> est généralement divisée en 4 panneaux avec un <strong>Menu
|
||
principal</strong> (Fichier Édition Importer Journal Vue Partager Aide) en haut de
|
||
la fenêtre (pour Windows et Linux) ou en haut de l'écran (pour Mac et Ubuntu
|
||
Unity). Les quatre panneaux sont :</p></div>
|
||
<div class="paragraph"><p>La <strong>liste des plongées</strong> en bas à gauche, affichant toutes les plongées du
|
||
journal (carnet) de plongées de l’utilisateur. Une plongée peut être
|
||
sélectionnée et mise en surbrillance dans la liste en cliquant dessus. Dans
|
||
la plupart des cas, les touches haut/bas peuvent être utilisées pour passer
|
||
d’une plongée à l’autre. La <strong>liste des plongées</strong> est un outil important pour
|
||
manipuler un journal (carnet) de plongée.</p></div>
|
||
<div class="paragraph"><p>La <strong>carte de plongée</strong> en bas à droite, affiche les sites de plongées de
|
||
l’utilisateur, sur une carte mondiale et centrée sur le site de la dernière
|
||
plongée sélectionnée dans la <strong>liste des plongées</strong>. L'échelle de la carte
|
||
peut être augmentée ou réduite.</p></div>
|
||
<div class="paragraph"><p>Les <strong>informations</strong> en haut à gauche, fournissent des informations détaillées
|
||
sur la plongée sélectionnée dans la <strong>liste des plongées</strong>, dont des
|
||
statistiques pour la plongée sélectionnée ou pour toutes les plongées mises
|
||
en surbrillance.</p></div>
|
||
<div class="paragraph"><p>Le <strong>profil de plongée</strong> en haut à droite, affiche un profil de plongée
|
||
graphique de la plongée sélectionnée dans la <strong>liste des plongées</strong>. Vous
|
||
pouvez zoomer sur le profil de plongée pour une vue plus détaillée.</p></div>
|
||
<div class="paragraph"><p>Les séparateurs entre ces panneaux peuvent être déplacés pour modifier la
|
||
taille de chaque panneau. <em>Subsurface</em> mémorise la position de ces
|
||
séparateurs, pour qu’au prochain lancement <em>Subsurface</em> utilise ces
|
||
positions.</p></div>
|
||
<div class="paragraph"><p>Si une unique plongée est sélectionnée dans la <strong>liste des plongées</strong>,
|
||
l’emplacement de la plongée, les informations détaillées et le profil de la
|
||
<em>plongée sélectionnée</em> sont affichées dans les panneaux respectifs. Si
|
||
plusieurs plongées sont sélectionnées, la dernière mise en surbrillance est
|
||
la <em>plongée sélectionnée</em>, mais les données de <em>toutes les plongées mises en
|
||
surbrillances</em> sont affichées dans l’onglet <strong>Statistiques</strong> du panneau
|
||
<strong>Informations</strong> (profondeur maximale, minimale et moyenne, les durées, les
|
||
températures de l’eau et le SAC (air consommé); temps total et nombre de
|
||
plongées sélectionnées).</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>L’utilisateur décide quels panneaux sont affichés, parmi les 4, en
|
||
sélectionnant l’option <strong>Vue</strong> dans le menu principal. Cette fonctionnalité
|
||
permet plusieurs choix d’affichage :</p></div>
|
||
<div class="paragraph"><p><strong>Tout</strong> : affiche les quatre panneaux tels que sur la capture d'écran ci-dessus.</p></div>
|
||
<div class="paragraph"><p><strong>Liste des plongées</strong> : affiche uniquement la liste des plongées.</p></div>
|
||
<div class="paragraph"><p><strong>Profil</strong> : affiche uniquement le profile de plongée de la plongée sélectionnée.</p></div>
|
||
<div class="paragraph"><p><strong>Info</strong> : affiche uniquement les notes de plongées de la dernière plongée sélectionnée et les statistiques pour
|
||
toutes les plongées mises en surbrillance.</p></div>
|
||
<div class="paragraph"><p><strong>Globe</strong> : affiche uniquement la carte mondiale, centrée sur la dernière plongée sélectionnée.</p></div>
|
||
<div class="paragraph"><p>Comme d’autres fonctions auxquelles on peut accéder via le menu principal,
|
||
ces options peuvent aussi être activées par des raccourcis clavier. Les
|
||
raccourcis pour un système particulier sont affichés avec un souligné dans
|
||
les entrées de menu. À cause des différents systèmes d’exploitation et
|
||
langues, <em>Subsurface</em> peut utiliser différentes touches de raccourcis et ne
|
||
sont donc pas détaillées ici.</p></div>
|
||
<div class="paragraph"><p>Lorsque le programme est lancé pour la première fois, il n’affiche aucune
|
||
information, parce qu’il n’a aucune information de plongée disponible. Dans
|
||
les sections suivantes, la procédure pour créer un nouveau carnet de plongée
|
||
sera détaillée.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_NewLogbook">4. Créer un nouveau carnet de plongée</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Sélectionner <em>Fichier → Nouveau carnet de plongée</em> à partir du menu
|
||
principal. Toutes les données de plongées sont effacées pour que de
|
||
nouvelles puissent être ajoutées. S’il existe des données non encore
|
||
enregistrées dans le carnet ouvert, l’utilisateur devra sélectionner s’il
|
||
faut les enregistrer ou non avant de créer le nouveau carnet.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_GetInformation">5. Enregistrement des informations de plongée dans le carnet</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Maintenant qu’un nouveau carnet de plongée a été créé, il est simple de lui
|
||
ajouter des données. <em>Subsurface</em> comporte plusieurs façons pour ajouter des
|
||
données de plongée au carnet.</p></div>
|
||
<div class="paragraph"><p>1) Si l’utilisateur possède un carnet manuscrit, un tableur ou une autre forme
|
||
de
|
||
carnet maintenu manuellement, les données de plongée peuvent être ajoutées
|
||
au carnet en utilisant une des approches suivantes :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Entrer les informations de plongée à la main. Cela est utile si le plongeur
|
||
n’a pas
|
||
utilisé d’ordinateur de plongée et que les plongées sont inscrites dans un
|
||
carnet manuscrit. Voir <a href="#S_EnterData">Entrer les informations de plongée
|
||
à la main</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Importer les informations de plongée qui ont été maintenues soit dans un
|
||
tableur
|
||
soit dans un fichier CSV. Se reporter à : <a href="#S_Appendix_D">ANNEXE D :
|
||
Exporter un tableur vers le format CSV</a> et à
|
||
<a href="#S_ImportingCSVDives">Importer des plongées au format CSV</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Si une plongée est enregistrée par un ordinateur de plongée, le profil de
|
||
profondeur et de nombreuses informations supplémentaires peuvent être
|
||
obtenues. Ces plongées peuvent être importées à partir de :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
L’ordinateur de plongée lui-même. Voir : <a href="#S_ImportDiveComputer">Importer
|
||
de nouvelles informations de plongée à partir de l’ordinateur de plongée</a>;
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logiciels propriétaires fournis par les fabricants d’ordinateurs de
|
||
plongée. Voir
|
||
<a href="#S_ImportingAlienDiveLogs">Importer les informations à partir d’autres
|
||
sources de données numériques ou d’autres formats de données</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Tableur ou de fichiers CSV contenant les profils de plongées.
|
||
Voir : <a href="#S_ImportingCSVDives">Importer les plongées au format CSV à partir
|
||
des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect2">
|
||
<h3 id="S_EnterData">5.1. Entrer les informations de plongée à la main</h3>
|
||
<div class="paragraph"><p>C’est en général l’approche des plongées sans ordinateur. L’enregistrement
|
||
de l’information de base dans <em>Subsurface</em> est une plongée. L’information la
|
||
plus importante dans un simple carnet de plongée inclut généralement le type
|
||
de plongée, la date et l’heure, la durée, la profondeur, le nom des
|
||
équipiers et du moniteur ou du guide de palanquée, et quelques remarques à
|
||
propos de la plongée. <em>Subsurface</em> peut stocker bien plus d’informations
|
||
pour chaque plongée. Pour ajouter une plongée au carnet, sélectionner
|
||
<em>Journal → Ajouter une plongée</em> depuis le menu principal. Le logiciel
|
||
affiche alors trois panneaux sur lesquels on peut entrer des informations
|
||
pour une plongée: deux onglets dans le panneau <strong>Informations</strong> (<strong>Notes</strong> et
|
||
<strong>Équipement</strong>), ainsi que le panneau <strong>Profil de plongée</strong> qui affiche un
|
||
profil graphique pour chaque ploingée. Ces panneaux sont respectivement
|
||
marqués <span class="red">A</span>, <span class="red">B</span> et <span class="red">C</span> dans l’llustration ci-dessous. Chaque
|
||
de ces onglets sera expliqué pour l’entrée de données.</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>Lorsque vous éditez un champ dans Notes ou Équipement, <em>Subsurface</em> entre en
|
||
<strong>Mode édition</strong>, indiqué par un message dans une boîte bleue en haut du
|
||
panneau <strong>Notes</strong> (voir image ci-dessous). Ce message est affiché dans tous
|
||
les panneau sous Notes et Équipement en <strong>Mode édition</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>Le bouton <em>Appliquer les modifications</em> ne doit être cliqué qu’après avoir
|
||
complété toutes les parties d’une plongée. Lors de l’entrée manuelle d’une
|
||
plongée, les onglets <em>Informations</em>, <em>Équipement</em> et <em>Profil</em> doivent être
|
||
complétés avant d’appliquer les modifications. En cliquant le bouton
|
||
<em>Appliquer les modifications</em>, une copie locale des informations d’une
|
||
plongée sont sauvegardées dans la mémoire, mais ne sont pas écrites sur le
|
||
disque. Le bouton <em>Appliquer lesmodifications</em> ne devrait UNIQUEMENT être
|
||
utilisé qu’après avoir entré toutes les informations d’une plongée. En
|
||
quittant Subsurface, le logiciel demandera si les carnet de plongée complet
|
||
doit être enregistré sur le disque ou non.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="S_CreateProfile">5.1.1. Création d’un profil de plongée</h4>
|
||
<div class="paragraph"><p>Le <strong>Profil de plongée</strong> (une représentation graphique de la profondeur d’une
|
||
plongée en fonction du temps) est affiché dans le panneau en haut à droite
|
||
de la fenêtre de <em>Subsurface</em>. Lorsqu’il est ajouté manuellement au carnet,
|
||
<em>Subsurface</em> affiche un profil de plongée par défaut qui nécessite d'être
|
||
modifié pour représenter au mieux la plongée décrite:</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>Modifier le profile de plongée</em>: lorsque le curseur est déplacé dans la
|
||
zone du profil, sa position est affichée par deux lignes rouges à angle
|
||
droit, comme illustré ci-dessous. Le temps et la profondeur sont représentés
|
||
en haut de la boîte noire d’information (@ et D). Les unités
|
||
(métriques/impériales) sur les axes sont déterminées dans les réglages des
|
||
<strong>Préférences</strong>. Le profil de plongée lui-même comporte plusieurs segments de
|
||
ligne séparés par des points de passage (les points blancs sur le profil,
|
||
voir ci-dessous). La profondeur par défaut d’une plongée est de 15m. Si la
|
||
prfondeur de votre plongée était de 20m, vous devez glisser le point de
|
||
passage approprié jusqu'à 20m. Pour ajouter un point de passage,
|
||
double-cliquez sur n’importe quel segment de la ligne. Pour bouger un point
|
||
de passage supplémentaire, glissez-le. Le bouger peut également être réalisé
|
||
en le sélectionnant et en utilisant les flèches du clavier. Pour supprimer
|
||
un point de passage, faites un clic-droit dessus et choisissez "Supprimer ce
|
||
point" dans le menu contextuel. Glissez les points de passage pour
|
||
représenter une durée correspondante à celle de votre plongée. Ci-dessous se
|
||
trouve un profil pour une plongée à 20m durant 30min, suivie d’un palier de
|
||
sécurité de 5 minutes à 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>Spécifier la composition du gaz:</em> la composition du gaz utilisé est
|
||
indiquée le long des segments de ligne du profil de plongée. Ceci est le
|
||
réglage par défaut pour le premier mélange gazeux spécifié dans l’ongle
|
||
<strong>Équipement</strong>, qui était de l’air dans le cas du profil ci-dessus. Les
|
||
mélanges gazeux des segments du profil peuvent être modifiés dans
|
||
cliquant-droit sur un point de passage précis et en sélectionnant le gaz
|
||
approprié dans le menu contextuel. Changer un gaz à un point de passage
|
||
modifie le gaz affiché dans le segment <em>à droite</em> du point de passage. Notez
|
||
que seuls les gaz définis dans l’onglet <strong>Équipement</strong> apparaissent dans le
|
||
menu contextuel (voir image ci-dessous).</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>Une fois le profil déterminé, d’autres détails doivent être ajoutés pour
|
||
obtenir un enregistrement complet de la plongée. Pour y arriver, les onglets
|
||
<strong>Notes</strong> et <strong>Équipement</strong> en haut à gauche de la fenêtre de <em>Subsurface</em>
|
||
doivent être utilisés. Cliquez sur <a href="#S_Notes_dc"><strong>ce lien</strong></a> pour plus
|
||
d’informations sur l’utilisation de ces onglets.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportDiveComputer">5.2. Importer de nouvelles informations de plongée à partir de l’ordinateur de plongée</h3>
|
||
<div class="sect3">
|
||
<h4 id="_connecter_et_importer_des_données_depuis_un_ordinateur_de_plongée">5.2.1. Connecter et importer des données depuis un ordinateur de plongée.</h4>
|
||
<div class="paragraph"><p>L’utilisation d’ordinateurs de plongée permet la collecte d’un grand nombre
|
||
d’informations à propos de chaque plongée, comme un enregistrement détaillé
|
||
de la profondeur, la durée, la vitesse de remontée ou de descente et les
|
||
pression partielles des gaz. <em>Subsurface</em> peut récupérer ces informations,
|
||
en utilisant les données venant d’une grande variété d’ordinateurs de
|
||
plongée. La liste la plus récente des ordinateurs supportés peut être trouvé
|
||
ici:
|
||
<a href="https://subsurface-divelog.org/documentation/supported-dive-computers/">Ordinateurs
|
||
de plongée supportés</a>.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Certains ordinateurs de plongée consomme plus d'énergie lorsqu’ils sont en
|
||
mode Communication PC. <strong>Ceci peut consommer une grande partie de la
|
||
batterie de votre ordinateur de plongée</strong>. Nous recommandons à l’utilisateur
|
||
de vérifier que l’ordinateur de plongée est chargé lorsqu’il est connecté au
|
||
port USB du PC. Par exemple, certains ordinateurs Suunto et Mares ne se
|
||
rechargent pas via la connection USB. Les utilisateurs doivent se reporter
|
||
au manuel de leur ordinateur de plongée s’ils ne savent pas si leur
|
||
ordinateur de plongée recharge ou non ses batteries lorsqu’il est connecté
|
||
au port USB.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>Pour importer les informations depuis un ordinateur de plongée vers un
|
||
ordinateur utilisant <em>Subsurface</em>, les deux pièces d'équipement doivent
|
||
communiquer entre elles. Ceci implique la configuration des ports de
|
||
communication (ou point de montage) de l’ordinateur sur lequel tourne
|
||
<em>Subsurface</em> qui communique avec l’ordinateur de plongée. Pour configurer
|
||
cette communication, les utilisateurs doivent trouver l’information
|
||
appropriée pour renseigner à <em>Subsurface</em> d’où et comment importer les
|
||
informations de
|
||
plongée.
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Annexe
|
||
A</a> donne les informations techniques pour aider l’utilisateur à configurer
|
||
ceci pour les différents systèmes d’exploitation et
|
||
<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Annexe
|
||
B</a> contient des informations spécifiques à chaque ordinateur de plongée.</p></div>
|
||
<div class="paragraph"><p>Après ceci, l’ordinateur de plongée peut être branché au PC de l’utilisateur
|
||
en suivant ces étapes:</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Le cable d’interface doit être connecté à un port USB libre (ou une
|
||
connection infra-rouge
|
||
ou Bluetooth doit être configurée comme décrit ultérieurement dans ce
|
||
manuel)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
L’ordinateur de plongée doit être placé en mode Communication PC.
|
||
(Se reporter au manuel de l’ordinateur de plongée)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Dans <em>Subsurface</em>, depuis le menu principal, sélectionner <em>Importer →
|
||
Importer depuis l’ordinateur de plongée</em>. La boîte de dialogue <strong>A</strong> apparaît
|
||
comme sur la figure ci-dessous:
|
||
</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>Les ordinateurs de plongée gardent généralement un certain nombre de
|
||
plongées en mémoire, même si ces plongées ont déjà été importées dans
|
||
<em>Subsurface</em>. Pour cette raison, si l’ordinateur de plongée le permet,
|
||
<em>Subsurface</em> importe uniquement les plongées qui n’ont pas été téléchargées
|
||
précédemment. Cela accélère le processus de téléchargement sur la plupart
|
||
des ordinateurs de plongée et cela économise la batterie de l’ordinateur de
|
||
plongée (en tout cas pour ceux qui ne se rechargent pas via USB).</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
La boîte de dialogue propose deux menus déroulants, <strong>Fournisseur</strong> et
|
||
<strong>Ordinateur de plongée</strong>. Dans le menu déroulant <strong>Fournisseur</strong>, sélectionnez
|
||
la marque de l’ordinateur, p. ex. Suunto, Oceanic, Uwatec, Mares. Dans le
|
||
menu déroulant <strong>Ordinateur de plongée</strong>, le nom du modèle doit être
|
||
sélectionné, p. ex. D4 (Suunto), Veo200 (Oceanic), ou Puck (Mares).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Le menu déroulant <strong>Périphérique ou point de montage</strong> le nom du port USB ou
|
||
Bluetooth dont <em>Subsurface</em> a besoin pour communiquer avec l’ordinateur de
|
||
plongée. Le port approprié doit être sélectionné. Consultez
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Annexe
|
||
A</a> et
|
||
<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Annexe
|
||
B</a> pour obtenir des détails techniques sur la façon de trouver des
|
||
informations sur le port approprié à chaque ordinateur de plongée et, dans
|
||
certains cas, sur les réglages requis pour le système d’exploitation de
|
||
l’ordinateur sur lequel <em>Subsurface</em> fonctionne.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Si toutes les plongées de l’ordinateur de plongée doivent être téléchargées,
|
||
cochez la case <em>Forcer le téléchargement de toutes les
|
||
plongées</em>. Normalement, <em>Subsurface</em> télécharge uniquement les plongées
|
||
postérieures à la date et heure de la dernière plongée du panneau <strong>Liste des
|
||
plongées</strong>. Si une ou plusieurs de vos plongées ont été accidentellement
|
||
effacées de <em>Subsurface</em> ou si des plongées plus anciennes doivent encore
|
||
être téléchargées depuis l’ordinateur de plongée, cette case doit être
|
||
cochée. Certains ordinateurs de plongée (p. ex. Mares Puck) ne proposent pas
|
||
de liste à <em>Subsurface</em> avant le téléchargement qui permettrait de n’en
|
||
sélectionner que certaines. Par conséquent, pour ces ordinateurs de
|
||
plongées, toutes les plongées sont téléchargées quel que soit le statut de
|
||
cette case à cocher.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Si la case <em>Toujours préférer les plongées téléchargées</em> a été cochée et
|
||
que, durant le téléchargement, des plongées avec date et heure identiques se
|
||
trouvent sur l’ordinateur de plongée et dans le panneau <strong>Liste des plongées</strong>
|
||
de <em>Subsurface</em>, la plongée dans le carnet de <em>Subsurface</em> sera écrasée par
|
||
l’enregistrement de l’ordinateur de plongée.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
La case à cocher <em>Télécharger dans un nouveau voyage</em> assure que, après
|
||
l’importation, les plongées téléchargées seront regroupées ensemble dans un
|
||
nouveau voyage dans la <strong>Liste des plongées</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ne cochez <strong>pas</strong> les cases nommées <em>Sauvegarder le fichier log de
|
||
libdivecomputer</em> et <em>Sauvegarder le fichier de données brutes de
|
||
libdivecomputer</em>. Elles sont uniquement utilisées comme outils de diagnostic
|
||
lorsque des problèmes de téléchargement se présentent (voir ci-dessous).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ensuite, cliquez sur le bouton <em>Télécharger</em>. Une fois la communication
|
||
établie, vous pouvez voir comment les données sont récupérées depuis
|
||
l’ordinateur de plongée. Selon la marque de l’ordinateur de plongée et/ou le
|
||
nombre de plongées enregistrées, cela peut prendre un certain temps. Soyez
|
||
patient. En bas de la boîte de dialogue de <em>Téléchargement</em>, vous trouverez
|
||
une barre de progression. Rappelez-vous que pour certains ordinateurs de
|
||
plongée, l’information de progression peut être incorrecte, puisque
|
||
<em>Subsurface</em> ne connait pas la quantité de données à télécharger tant que le
|
||
téléchargement n’est pas terminé. Après le téléchargement des plongées,
|
||
elles apparaissent sous forme de tableau dans la partie droite de la boîte
|
||
de dialogue (voir image <strong>B</strong>, ci-dessus). Chaque plongée comporte une rangée
|
||
dans le tableau, montrant la date, la durée et la profoneur. À côté de
|
||
chaque plongée se trouve une case à cocher: cochez toutes les plongées qui
|
||
doivent être transférées vers la <strong>Liste des plongées</strong>. Dans le cas de
|
||
l’image ci-dessus, les six dernières plongées sont cochées et seront
|
||
transférées vers la <strong>Liste des plongées</strong>. Cliquez ensuite sur le bouton <em>OK</em>
|
||
en bas de la boîte de dialogue. Toutes les plongées importées apparaissent
|
||
dans la <strong>Liste des plongées</strong>, classées par date et heure. Déconnectez et
|
||
éteignez l’ordinateur de plongée pour économiser sa batterie.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
S’il y a un problème de communication avec l’ordinateur de plongée, un
|
||
message d’erreur s’affiche, semblable à ce texte: "Impossible d’ouvrir
|
||
/dev/ttyUSB0 Mares (Puck Pro)". Rapportez-vous au texte dans le boîte de
|
||
dialogue ci-dessous.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sidebarblock">
|
||
<div class="content">
|
||
<div class="paragraph"><p><strong>PROBLÈMES AVEC LE TÉLÉCHARGEMENT DES DONNÉS DE L’ORDINATEUR DE PLONGÉE?</strong></p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Vérifiez les éléments suivants:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
L’ordinateur de plongée est-il en mode Communication PC ou Téléchargement?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
La batterie de l’ordinateur de plongée est-elle complètement chargée? Si ce
|
||
n’est pas le cas, chargez-la ou remplacez-la.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Le câble de connexion est-il fautif ? Le câble fonctionne-t-il avec d’autres
|
||
logiciels? A-t-il fonctionné précédemment, ou est-ce la première fois que ce
|
||
câble est utilisé? Les contacts sur l’ordinateur de plongée et le câble
|
||
sont-ils propres ?
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Consultez
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Annexe
|
||
A</a> pour être certain que le point de montage correct a été spécifié (voir
|
||
ci-dessus).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Sur les systèmes d’exploitation de type Unix, l’utilisateur a-t-il les
|
||
droits d'écriture sur le port USB? Si non, consultez
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Annexe
|
||
A</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Si l’ordinateur utilisant <em>Subsurface</em> ne reconnaît pas l’adaptateur USB en
|
||
ne montrant pas le bon nom de périphérique à côté du Point de montage, il
|
||
est possible que le câble ou l’adaptateur USB soit fautif. Un câble
|
||
défectueux est la cause la plus courante de problème de communication entre
|
||
un ordinateur de plongée et <em>Subsurface</em>. Il est également possible que
|
||
<em>Subsurface</em> ne puisse pas interpréter les données. Réalisez un
|
||
téléchargement de diagnostic en cochant les deux cases suivantes dans la
|
||
boîte de dialogue de téléchargement décrite ci-dessus:</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>: ces cases à cocher ne doivent être utilisées qu’en cas de problème
|
||
durant le processus de téléchargement. En temps normal, elles ne doivent pas être cochées.
|
||
En cochant ces cases, l’utilisateur doit sélectionner un dossier où l’information sera enregistrée. Le dossier par défaut est celui dans lequel
|
||
le carnet de
|
||
<em>Subsurface</em> est stocké.</p></div>
|
||
<div class="paragraph"><p><strong>Important:</strong> <em>après un téléchargement avec les cases ci-dessus
|
||
cochées, aucune plongée n’est ajoutée à la
|
||
<strong>Liste des plongées</strong> mais deux fichiers sont créés dans le dossier sélectionné précédemment</em>:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>subsurface.log
|
||
subsurface.bin</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Ces fichiers doivent être envoyés à la liste de diffusion de <em>Subsurface</em>:
|
||
<em>subsurface@subsurface-divelog.org</em> avec une demande d’analyse des
|
||
fichieres. Précisez la marque et le modèle de l’ordinateur ainsi que des
|
||
informations relatives aux plongées enregistrées sur l’ordinateur de
|
||
plongée.</p></div>
|
||
</div></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_Bluetooth">5.2.2. Connexion de <em>Subsurface</em> à un ordinateur de plongée équipé de Bluetooth</h4>
|
||
<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive
|
||
computers and <em>Subsurface</em>. <em>Subsurface</em> provides a largely operating system
|
||
independent Bluetooth interface. An increasing number of dive computers use
|
||
Bluetooth Low Energy (BTLE) as a means of communication. However, BTLE is
|
||
not a standardised protocol, consequently adaptations need to be made for
|
||
communicating with each different dive computer model. See the
|
||
<a href="https://subsurface-divelog.org/documentation/supported-dive-computers/">list
|
||
of supported dive computers</a>. Bluetooth communication is often more
|
||
reliable if all Bluetooth devices seen by the <em>Subsurface</em> computer are
|
||
removed and pairing with the Bluetooth dive computer is performed from
|
||
afresh. The Bluetooth and BTLE interfaces are under active development with
|
||
respect to new dive computers that use this mechanism of communication.</p></div>
|
||
<div class="paragraph"><p>La configuration de <em>Subsurface</em> pour une communication Bluetooth nécessite
|
||
4 étapes :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Vérifiez que Blutooth est activé sur l’ordinateur sur lequel <em>Subsurface</em>
|
||
est actif.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Vérifiez que <em>Subsurface</em> détecte l’adaptateur Bluetooth de l’ordinateur.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Vérifiez que l’ordinateur de plongée Bluetooth est détectable et en mode
|
||
Connection PC.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Vérifiez que <em>Subsurface</em> est jumelé avec l’ordinateur de plongée Bluetooth.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Faites apparaître la boîte de dialogue de téléchargement en sélectionnant
|
||
<em>Importer → Importer depuis l’ordinateur de plongée</em> depuis le <strong>Menu
|
||
principal</strong>. Après avoir coché la case <em>"Choisir le mode de téléchargement
|
||
Bluetooth"</em>, la boîte de dialogue ci-dessous apparaît.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="_sur_linux_ou_macos">Sur Linux ou 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>Although the <em>Subsurface</em> Bluetooth interface is intended to function
|
||
without Bluetooth pairing at the operating system level, it is always
|
||
prudent to follow up initial Bluetooth pairing problems by pairing the
|
||
Bluetooth dive computer with the <em>Subsurface</em> computer using the operating
|
||
system services of the desktop computer. Delete all existing pairings and
|
||
start by scanning for Bluetooth devices from an empty list (on the desktop)
|
||
of Bluetooth devices. Once <em>Subsurface</em> has recognised the Bluetooth dive
|
||
computer, subsequent divelog downloads are likely to be simple.</p></div>
|
||
<div class="paragraph"><p>Sur les plateformes <em>Linux</em> ou -MacOS_, le nom de l’ordinateur utilisant
|
||
Subsurface_ et son adresse Bluetooth sont affichées du côté droit. L'état
|
||
(allumé/éteint) de l’adaptateur Bluetooth est affiché sous l’adresse et peut
|
||
être modifié en cliquer sur la case <em>Allumer/éteindre</em>. Si l’adresse
|
||
Bluetooth n’est pas affichée, <em>Subsurface</em> ne détecte pas le périphérique
|
||
Bluetooth local. Assurez-vous que le driver Bluetooth est installé
|
||
correctement sur l’ordinateur utilisant <em>Subsurface</em> et vérifiez qu’il peut
|
||
être utilisé par d’autres utilitaires Bluetooth comme <em>bluetoothctl</em> ou
|
||
<em>bluemoon</em>. Ceci clôture les deux premières étapes. Vérifiez que
|
||
l’ordinateur de plongée avec Bluetooth est en mode Connexion PC et est
|
||
détectable pour d’autres périphériques Bluetooth. Consultez le manuel de
|
||
l’ordinateur de plongée pour plus d’information. À présent, la troisième
|
||
étape de notre liste est terminée. Sélectionnez le bouton <em>Scannez</em> en bas
|
||
à gauche de la boîte de dialogue ci-dessus. Après la recherche, l’ordinateur
|
||
de plongée devrait se trouver dans la liste (peut-être sous la norme d’un
|
||
numéro de périphérique Bluetooth) dans la liste principale sur la gauche de
|
||
la boîte de dialogue (voir image ci-dessus). Si cela ne fonctionne pas,
|
||
sélectionnez le bouton <em>Effacer</em>, puis scannez à nouveau en utilisant le
|
||
bouton <em>Scan</em>. Après avoir suivi cette procédure, <em>Subsurface</em> devrait voir
|
||
l’ordinateur de plongée. La dénomination de l’ordinateur de plongée détecté
|
||
contient le nom du périphérique, son adresse et son statut de jumelage. Si
|
||
le périphérique n’est pas jumelé et que son nom est affiché avec un
|
||
arrière-plan rouge, un menu contextuel peut être ouvert en sélectionnant ce
|
||
nom avec un cli-droit. Sélectionnez l’option <em>Jumeler</em> et attendez que la
|
||
tâche soit terminée. Si l’ordinateur est jumelé à Subsurface pour la
|
||
première fois, il est possible que Subsurface demande un nombre ou un code
|
||
PIN. Le plus utilisé est 0000, et c’est celui qui fonctionne pour un
|
||
Shearwater Petrel. Si nécessaire, consultez le manuel utilisateur de
|
||
l’ordinateur de plongée que vous utilisez.</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">Actuellement, <em>Subsurface</em> ne supporte par le jumelage Bluetooth avec les
|
||
ordinateurs de plongée qui nécessitent un code PIN personnalisé. Pour
|
||
jumeler ces périphériques, utiliser les utilitaires du système
|
||
d’exploitation comme suggéré ci-dessous.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>Une façon d’y parvenir est d’utiliser <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>Une fois que les péréphériques sont jumelés, cliquer sur le bouton
|
||
<em>Enregistrer</em> de la boîte de dialogue. Ceci fermera la boîte de dialogue
|
||
Bluetooth. Ensuite, sélectionnez <em>Télécharger</em> dans la boîte de dialogue
|
||
<em>Télécharger depuis l’ordinateur de plongée</em> qui devrait encore être
|
||
ouverte. Les plongées téléchargées sont affichées dans la partie droite de
|
||
la boîte de dialogue de téléchargement.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_sur_windows">Sur 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>Sous <em>Windows</em>, les <em>Détails du périphérique Bluetooth local</em> à droite ne
|
||
sont pas affichés comme dans les sytèmes Linux/Mac. Pour démarrer un scan
|
||
(en appuyant sur le bouton <em>Scan</em>), vérifiez que le périphérique Bluetooth
|
||
sur l’ordinateur de <em>Subsurface</em> est activé en sélectionnant l’ordinateur de
|
||
plongée dans la liste des périphériques Bluetooth disponibles (voir image
|
||
ci-dessus). Si l’ordinateur de plongée est connecté à Subsurface pour la
|
||
première fois, il est possible que Subsurface demande un nombre ou un code
|
||
PIN. Entrez le code indiqué dans le manuel utilisateur de l’ordinatuer de
|
||
plongée. Un code ou PIN de 0000 est souvent le code par défaut.</p></div>
|
||
<div class="paragraph"><p>L'étape de jumelage est vérifiée et réalisée automatiquement durant le
|
||
processus de téléchargement. Si les périphériques n’ont pas encore été
|
||
jumelés, le système demandera l’autorisation de le faire et affichera un
|
||
message sur la partie droite de l'écran. <em>Ajouter un périphérique</em>, <em>Tapez
|
||
pour configurer votre périphérique</em>. <em>Toujours autoriser le jumelage. Après
|
||
la sélection d’un item découvert, cliquez sur le bouton
|
||
_Enregistrer</em>. Enfin, sélectionnez le bouton "Télécharger_ dans la boîte de
|
||
dialogue de téléchargement et attendez la fin du processus.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content">Actuellement, <em>Subsurface</em> ne fonctionne qu’avec les adaptateurs Bluetooth
|
||
locaux qui utilisent Microsoft Bluetooth Stack. Si le périphérique local
|
||
utilise des drivers <em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> ou
|
||
<em>BlueSoleil</em>, cela ne fonctionnera pas. Cependant, les clés/dongles de ces
|
||
fabricants (p. ex. iSonic) qui supportent le Microsoft Bluetooth Stack
|
||
fonctionneront.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>Un journal de message (log) en bas à gauche de la <em>sélection de périphérique
|
||
Bluetooth distant</em> affiche des détails sur le statut actuel du l’agent
|
||
Bluetooth. Pour sélectionner un autre ordinateur de plongée utilisant la
|
||
"boîte de dialogue de sélection Bluetooth distant", cliquez sur le bouton
|
||
avec trois points à côté de l’option <em>"Choisir le mode de téléchargement
|
||
Bluetooth"</em>.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/important.png" alt="Important" />
|
||
</td>
|
||
<td class="content"><strong>EN CAS DE PROBLÈMES</strong>: si l’adaptateur Bluetooth de l’ordinateur utilisant <em>Subsurface</em>
|
||
se bloque et que le processus de <em>téléchargement</em> échoue de façon répétée,
|
||
<em>dissociez</em> les périphériques et répétez les étapes ci-dessus. Si cela ne fonctionne pas,
|
||
l' <a href="#S_HowFindBluetoothDeviceName"><em>Annexe A</em></a> contient
|
||
des informations sur la configuration manuelle et la vérification de la connection Bluetooth
|
||
avec <em>Subsurface</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_DeviceNames">5.2.3. Changement du nom d’un ordinateur de plongée</h4>
|
||
<div class="paragraph"><p>Il peut être nécessaire d'établir une distinction entre différents
|
||
ordinateurs de plongée utilisés pour télécharger des données de plongée vers
|
||
<em>Subsurface</em>. Par exemple, si l’ordinateur d’un équipier provient du même
|
||
fabriquant et est dun même modèle que le votre et que les données sont
|
||
téléchargées vers le même ordinateur utilisant <em>Subsurface</em>, vous voudirez
|
||
sans doute en appeler un "Suunto D4 d’Alice" et l’autre "Suunto D4 de
|
||
Bob". Ou encore, imaginez un plongeur Tek qui plonge avec deux ordinateurs
|
||
ou plus; les données pourraient toutes être téléchargées. Dans ce cas, il
|
||
serait prident de les appeler "Suunto D4 (1)" et "Suunto D4 (2)". Ceci est
|
||
facilement réalisable dans <em>Subsurface</em>. Dans le <strong>Menu principal</strong>,
|
||
sélectionnez <em>Journal → Éditer les noms des ordinateurs de plongée</em>. Une
|
||
boîte de dialogue s’ouvre, affichant le modèle actuel, son ID et le nom des
|
||
ordinateurs utilisés pour le téléchargement. Éditez le champ Nom de
|
||
l’ordinateur de plongée concerné. Après avoir sauvegardé le Nom, le journal
|
||
de plongée affiche le nom de l’ordinateur concerné à la place du nom du
|
||
modèle, permettant une identification plus facile des périphériques.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_MultipleDiveComputers">5.2.4. Chargement des données d’une plongée spécifique depuis plusieurs ordinateurs de plongée</h4>
|
||
<div class="paragraph"><p>Certains plongeurs utilisent plus d’un ordinateur de plongée en même,temps,
|
||
par exemple en plongée technique. Si vous importez les profils de ces
|
||
différents ordinateurs de plongée dans <em>Subsurface</em>, les profils peuvent
|
||
être vu indépendemment. Pendant le téléchargement, les données de ces
|
||
ordinateurs de plongée sont automatiquement fusionnées en une seule
|
||
plongée. Les différents profils sont présentés dans le panneau <em>Profil</em> avec
|
||
le nom de chaque ordinateur de plongée indiqué en bas à gauche. <strong>Lorsque la
|
||
plongée est en surbrillance dans la <em>Liste des plongées</em></strong>, passez du profil
|
||
d’un ordinateur de plongée à l’autre en utilisant soit les flèches
|
||
gauche/droite du clavier, soit en sélectionnant <em>Vue Ordinateur précédent</em>
|
||
ou <em>Vue → Ordinateur suivant</em>. Les données du panneau <em>Notes</em> ne sont pas
|
||
affectées par le choix de l’un ou l’autre ordinateur de plongée.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_EditDiveInfo">5.2.5. Mise à jour de l’information importée depuis un ordinateur de plongée.</h4>
|
||
<div class="paragraph"><p>Une fois les plongées chargées dans la Liste des plongées, l’information
|
||
extraite de l’ordinateur de plongée n’est pas complète et d’autres détails
|
||
doivent être ajoutés pour obtenir un enregistrement complet des
|
||
plongées. Pour ce faire, les onglets <strong>Notes</strong> et <strong>Équipement</strong> et haut à
|
||
gauche de la fenêtre de <em>Subsurface</em> doivent être utilisés.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="S_Notes_dc">Notes</h5>
|
||
<div class="paragraph"><p>Pour obtenir un enregistrement plus comple de la plongée, l’utilisateur doit
|
||
ajouter manuellement certaines informations. La procédure expliquée
|
||
ci-dessous est quasiment identique pour les plongées entrées manuellement et
|
||
celles qui sont téléchargées depuis un ordinateur de plongée.</p></div>
|
||
<div class="paragraph"><p>Dans certains cas, vous devrez préciser la date et l’heure de la plongée,
|
||
par exemple lorsque vous entrez une plongée manuellement ou qu’un ordinateur
|
||
de plongée ne précise pas la date et l’heure de cette plongée. (D’habitude,
|
||
la date et l’heure d’une plongée, le mélange de gaz et la température de
|
||
l’eau sont obtenues via l’ordinateur de plongée). Si le contenu de l’onglet
|
||
<strong>Notes</strong> est modifié ou édité d’une quelconque manière, le message dans la
|
||
boîte bleue en haut du panneau affiche que la plongée a été éditée. Si vous
|
||
cliquez sur l’onglet <strong>Notes</strong>, les champs suivants sont visibles (voir image
|
||
en bas à gauche):</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>L’image à droite, ci-dessus, montre l’onglet <strong>Notes</strong> complété avec des
|
||
informations de plongée. Les champs <strong>Date</strong> et <strong>Heure</strong> indiquent la date et
|
||
l’heure de la plongée. En cliquant sur la date, un calendrier est afficher
|
||
pour sélectionner la date correcte. Appuyez sur la touche ESC pour fermer le
|
||
calendrier. Les valeurs d’heure (heure et minutes) peuvent également être
|
||
éditées directement en cliquant sur chacune d’entre elles dans la boîte de
|
||
texte et en remplaçant l’information qui s’y trouve.</p></div>
|
||
<div class="paragraph"><p><strong>Température de l’air/eau</strong>: les températures de l’air et de l’eau pendant la plongée sont affichées
|
||
dans des boîtes de texte à droite de l’heure de début de plongée. De nombreux ordinateurs de plongée
|
||
renseignent la température de l’eau, et cette boîte peut contenir cette information.
|
||
Si la température de l’air n’est pas renseignée par l’ordinateur de plongée, la première température pour l’eau
|
||
peut être utilisée comme température de l’air. En général, elle est proche de la température de l’air.
|
||
S’il est nécessaire d'éditer ces informations, seule une valeur est nécessaire, l’unité de température étant
|
||
automatiquement fournie par
|
||
<em>Subsurface</em> (sur base des <em>Préférences</em>, les unités métriques ou impériales
|
||
seront utilisées).</p></div>
|
||
<div class="paragraph" id="S_locations"><p><strong>Lieu</strong>:</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Les lieux de plongée sont gérés comme une partie <strong>séparée</strong> du carnet de
|
||
plongée. Les informations de plongée dans les onglets <strong>Notes</strong> et
|
||
<strong>Équipement</strong> ne peuvent donc PAS être édités en même temps que les
|
||
informations sur le site de plongée. Enregistrez toutes les autres
|
||
informations (p. ex. instructeur, équipier, équipement, notes à propos de la
|
||
plongée) en sélectionnant <em>Appliquer les modifications</em> dans l’onglet
|
||
<strong>Notes</strong> AVANT d'éditer les informations sur le site de plongée. Ensuite,
|
||
nommez le site de plongée dans la bpîte de texte <em>Lieu</em> dans l’onglet
|
||
<strong>Notes</strong>.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Using existing dive locations:</strong> Type in the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary".
|
||
If several dives are
|
||
made at the same location, the site information for the first dive is re-used.
|
||
Therefore, if a dive site has been used before, the name of that site (and sometimes
|
||
the names of similar sites) appears below the dive site text box (image below). Double-click on
|
||
the appropriate dive site name and the dive location will be associated with the
|
||
dive being entered. Then select <em>Apply Changes</em> (image below) to save the geolocation for this dive site.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Location1.jpg" alt="FIGURE:Location choice panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Entering a new dive location:</strong> On the other hand, having dived at a new dive location,
|
||
a new record needs to be created
|
||
that could be used for the new and for later dives at this new site. Type the name of the new dive site into the text box
|
||
(image A below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Globe_image1.jpg" alt="FIGURE:Location creation panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Double-click on the blue bar below the new dive location name. The blue bar
|
||
disappears (image B above) and the globe icon on the right-hand of the
|
||
location name text box turns blue. In the Dive Map part of the <em>Subsurface</em>
|
||
window, a world map appears (image C above). Click on the blue globe icon to
|
||
the right of the dive site name in the <em>Notes</em> panel (image B above). This
|
||
opens a window for entering the details of the new dive location (image A
|
||
below). The globe icon changes to indicate that the location data are being
|
||
edited. The only important data here are the geographic coordinates of the
|
||
dive location.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Globe_image2.jpg" alt="FIGURE:Location creation panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Il existe trois façons d’ajouter des coordonnées :</p></div>
|
||
<div class="paragraph"><p><strong>(1):</strong> Entrer les coordonnées manuellement si vous les connaissez,
|
||
en utilisant un des quatre formats avec la latitude suivie de la longitude :</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Format ISO 6709 Annexe D, ex. 30°13'28.9"N 30°49'1.5"E
|
||
Degrés et minutes décimales, ex. N30° 13.49760' , E30° 49.30788'
|
||
Degrés minutes secondes, ex. N30° 13' 29.8" , E30° 49' 1.5"
|
||
Degrés décimaux, ex. 30.22496 , 30.821798</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Les latitudes dans l’hémisphère sud sont données avec un <strong>S</strong>, ex. S30°, ou
|
||
avec une valeur négative, ex. -30.22496. De la même façon, les longitudes
|
||
ouest sont données avec un <strong>W</strong>, ex. W07°, ou avec une valeur négative,
|
||
ex. -7.34323. Certains claviers ne comportent par le signe degré (°). Il
|
||
peut être remplacé par un <strong>d</strong> comme ceci: N30d W20d. Entrer tout autre
|
||
informations à propos du site de plongée (Description et notes), puis
|
||
sélectionner <em>Appliquer les modifications</em> pour sauvegarder la
|
||
géolocalisation de ce site. Les informations du site de plongée pourront
|
||
être modifiées ultérieurement, en cliquant sur l’icône de globe à droite du
|
||
nom du site de plongée, dans l'"onglet notes".</p></div>
|
||
<div class="paragraph"><p><strong>(2):</strong> Use the Dive Map to specify the coordinates. The Dive map now shows
|
||
all the existing dive locations in grey as well as an additional marker in red
|
||
(image B above). Drag the red marker to the location of the dive site being entered.
|
||
The map can be dragged and zoomed using the mouse wheel. Position the red marker
|
||
by dragging it on the map, zooming in on the appropriate part of the map and placing
|
||
the marker at an appropriate position (image B below). The coordinates of the dive
|
||
location are automatically inserted into the appropriate text box in the dive location
|
||
information window (image A below). Enter any other contextual information about the dive site (Description and Notes),
|
||
then select <em>Apply Changes</em> to save the geolocation for this dive site.
|
||
The dive site information can later 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="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Globe_image3.jpg" alt="FIGURE:Location creation panel" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Once the dive location data have been saved, the dive on the Dive List has a
|
||
globe icon immediately to the left of the location name of a particular
|
||
dive.</p></div>
|
||
<div class="paragraph"><p><strong>(3):</strong> Obtenir les coordonnées en utilisant soit l’application Subsurface-Mobile, soit l’application <em>Subsurface</em> Companion avec un
|
||
périphérique Android ou un iPhone avec GPS si les coordonnées du site de plongée ont été stockées
|
||
en utilisant une de ces applications.
|
||
<a href="#S_Companion">Cliquez ici pour plus d’information</a></p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Les coordonnées GPS d’un site de plongée sont liées au nom de lieu - ainsi,
|
||
<strong>enregistrer</strong> un site de plongée avec uniquement les coordonnées mais aucun
|
||
nom causera des problèmes. (Subsurface pensera que toutes cesplongées ont le
|
||
même lieu et tentera de garder leurs coordonnées GPSidentiques).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Recherche du nom d’un site de plongée</strong>: si vous avez entré les coordonnées dans la boîte
|
||
de texte appropriée, vous pouvez lancer une recherche de nom sur base des coordonnées.
|
||
Ceci est réalisé lorsque <em>Subsurface</em> utilise Internet pour trouver le nom d’un site de plongée
|
||
sur base des coordonnées que vous avez entrées. Si un nom est trouvé, il est
|
||
automatiquement inséré dans la boîte Étiquettes. La liste (intitulée <em>"Sites de plongée situés aux mêmes coordonnées</em>") en bas
|
||
du panneau du site de plongée contient les noms d’autres sites de plongée utilisés
|
||
au même endroit. Par exemple, si le site de plongée est "Blue Hole" et qu’il y a plusieurs
|
||
sites nommés "Blue Hole", ils seront tous listés.</p></div>
|
||
<div class="paragraph"><p>Entrez toute information contextuelle relative au site de plongée
|
||
(Description et Notes) puis sélectionnez <em>Appliquer les modifications</em> pour
|
||
enregistrer la géolocalisation du site de plongée. L’information concernant
|
||
le site de plongée peut être éditée ultérieurement en cliquant sur l’icone
|
||
en forme de globe à droite du nom du site de plongée dans l’onglet <strong>Notes</strong>.</p></div>
|
||
<div class="paragraph"><p><strong>Mode de plongée</strong>: cette liste déroulante vous permet de choisir le type de plongée
|
||
réalisée. Les options sont OC (scaphandre en circuit ouvert, le choix par défaut pour la plupart des plongées loisir),
|
||
Apnée (plongée sans scaphandre), CCR (recycleur
|
||
en circuit fermé) et pSCR (recycleur passif semi-fermé).</p></div>
|
||
<div class="paragraph"><p><strong>Moniteur/Guide de palanquée</strong>: le nom du moniteur ou du guide de palanquée doit être
|
||
entré dans ce champ
|
||
qui permet une sélection automatique basé sur la liste des moniteurs
|
||
déjà présents dans le carnet en cours.</p></div>
|
||
<div class="paragraph"><p><strong>Équipier</strong>: dans ce champ, entrez le(s) nom(s) de votre/vos équipier(s)
|
||
(sparés par des virgules) qui participaient à la
|
||
plongée. Une sélection automatique se base sur la liste des équipiers déjà présents dans le
|
||
carnet en cours.</p></div>
|
||
<div class="paragraph"><p><strong>Combinaison</strong>: le type de combinaison peut être entré ici.
|
||
Une sélection automatique est disponible.
|
||
Certains utilisateurs de vêtement étanche peuvent utiliser ce champ pour enregistrer quelle ensemble de
|
||
combinaison et souris ils ont utilisé.</p></div>
|
||
<div class="paragraph"><p><strong>Évaluation</strong>: attribue une évaluation subjective à une plongée sur une
|
||
échelle de 5 points en cliquant sur l'étoile correspondante.</p></div>
|
||
<div class="paragraph"><p><strong>Visibilité</strong>: attribue une évaluation de la visibilité à une plongée sur une
|
||
échelle de 5 points en cliquant sur l'étoile correspondante.</p></div>
|
||
<div class="paragraph"><p><strong>Étiquettes</strong>: il est possible de définir ici des étiquettes qui décrivent le
|
||
type de plongée (séparées par des virgules). Des exemples courants d'étiquettes sont bateau,
|
||
plongée dérivante, exercice, grotte, etc.
|
||
<em>Subsurface</em> contient de nombreuses étiquettes. En commençant à taper une étiquette, <em>Subsurface</em> liste
|
||
les étiquettes correspondant à la frappe. Par exemple, en entrant
|
||
<code>cav</code>, les étiquettes <strong>cave</strong> et <strong>caverne</strong> sont proposées.</p></div>
|
||
<div class="paragraph"><p><strong>Notes</strong>: toute information supplémentaire concernant une plongée peut être entrée ici.</p></div>
|
||
<div class="paragraph"><p>Les boutons <em>Appliquer les modifications</em> et <em>Annuler les modifications</em>
|
||
sont utilisés pour enregistrer toutes les informations des onglets du
|
||
panneau <strong>Informations</strong> et du panneau <strong>Profil de plongée</strong>. Utilisez-les
|
||
lorsque <strong>TOUTES</strong> les autres informations ont été ajoutées. L’image
|
||
<a href="#S_Notes_dc">située au début de cette section</a> montre un exemple de
|
||
l’onglet <strong>Notes</strong> après avoir complété les informations d’une plongée.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_équipement">Équipement</h5>
|
||
<div class="paragraph"><p>L’onglet Équipement permet d’entrer les informations concernant le type de
|
||
bloc et le gaz utilisé, ainsi que le lestage utilisé pour la plongée. Le
|
||
message dans la boîte bleue en haut du panneau:</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>indique que l'équipement a été édité. C’est une partie hautement interactive
|
||
de <em>Subsurface</em> et les informations sur les blocs et les gaz (entrées ici)
|
||
déterminent le comportement du <strong>Profil de plongée</strong> (panneau en haut à
|
||
droite).</p></div>
|
||
<div class="paragraph" id="cylinder_definitions"><p><strong>Blocs</strong>: les informations concernant les blocs sont entrées via une boîte de dialogue
|
||
qui ressemble à ceci:</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>Pour les plongées entrées manuellement, cette information doit être
|
||
entrée. Pour les ordinateurs de plongée, <em>Subsurface</em> reçoit souvent
|
||
l’information concernant le gaz utilisé et insère automatiquement sa
|
||
composition (% d’oxygène ou % d’hélium) dans le tableau. Le bouton + en haut
|
||
à droite permet d’ajouter des blocs pour cette plongée. L’icone de corbeille
|
||
noire à gauche permet de supprimer les informations d’un bloc. Notez qu’il
|
||
n’est pas possible de supprimer un bloc s’il est utilisé durant la
|
||
plongée. Un bloc doit être implicitement utilisé pour la plongée, même sans
|
||
événement de changement de gaz. Commencez par sélectionner un type de bloc
|
||
dans la partie gauche du tableau. Pour sélectionner un bloc, il faut
|
||
cliquer sur la boîte <em>Type</em>. Cela fera apparaître un bouton permettant
|
||
d’afficher une liste déroulante de blocs:</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>La liste déroulante peut être utilisée pour sélectionner le type de bloc
|
||
utilisé pour cette plongée, ou il suffit de commencer à taper dans la boîte
|
||
pour afficher les options disponibles selon les lettres entrées. La <strong>Taille</strong>
|
||
du bloc ainsi que sa pression de service (_Pression de service) seront
|
||
automatiquement affichées dans la boîte de dialogue.</p></div>
|
||
<div class="paragraph"><p>Ensuite, indiquez la pression de déart et celle d’arrivée pour le gaz
|
||
spécifié pendant la plongée. L’unité de pression (métrique/impériale)
|
||
correspond au réglage choisi dans les <em>Préférences</em>.</p></div>
|
||
<div class="paragraph"><p>Pour terminer, renseignez le mélange de gaz utilisé. S’il s’agit d’air, la
|
||
valeur de 21% peut être entrée dans la case Oxygène, ou ce champ peut être
|
||
laissé vide. Si du nitrox ou du trimix a été utilisé, les pourcentages
|
||
d’oxygène et/ou d’hélium doivent être entrés. Tout champ non requis
|
||
concerné doit être laissé vide. Après avoir entré les informations du bloc,
|
||
enregistrez les données soit en pressant la douche <em>ENTRÉE</em>, soit en
|
||
cliquant hors de la case contenant le curseur. Les informatioins pour les
|
||
blocs supplémentaires peuvent être ajoutées en utilisant le bouton + en haut
|
||
à droite. Voici un exemple d’une description complète pour une plongée
|
||
utilisant deux blocs (air et 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>Poids</strong>: les informations à propos du système de lestage peuvent être entrés
|
||
via une interface similaire à celles des blocs. Si vous cliquez
|
||
sur le bouton + en haut à droite , le tableau apparaît
|
||
comme suit:</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>En cliquant sur le champ: <em>Type</em>, une liste déroulante devient accessible
|
||
via une flèche vers le bas:</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>Celle-ci peut être utilisée pour sélectionner le type de poids utilisé
|
||
durant la plongée. Vous pouvez commencer à taper dans la case pour spécifier
|
||
un mécanisme différent de lestage qui sera sauvegardé par <em>Subsurface</em>. Dans
|
||
le champ <strong>Poids</strong>, entrez la quantité de poids utilisé durant la
|
||
plongée. Après avoir spécifié le système de lestage, enregistrez les données
|
||
avec la touche <em>ENTRÉE</em> du clavier ou en cliquant hors de la case contenant
|
||
le curseur. Il est possible d’entrer des informations pour plusieurs
|
||
systèmes de lestage en utilisant le pouton + en haut à droite. Les systèmes
|
||
de lestage peuvent être supprimés en utilisant l’icone de corbeille sur la
|
||
gauche. Voici un exemple d’informations pour une plongée avec deux systèmes
|
||
de lestage: des poids intégrés et une ceinture:</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="_éditer_simultanément_une_sélection_de_plusieurs_plongées">5.2.6. Éditer simultanément une sélection de plusieurs plongées</h4>
|
||
<div class="paragraph"><p><em>METHOD 1</em>: After downloading dives from a dive computer, the dive profiles
|
||
of each 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). 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’s possible that a diver
|
||
performed several dives during a single day, using identical equipment at
|
||
the same dive site, or with the same divemaster and/or buddy or
|
||
tags. Instead of completing the information for each dive separately, 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 done by editing the dive notes or the equipment for any
|
||
one of the selected dives.</p></div>
|
||
<div class="paragraph"><p>Simultaneous editing only works with fields that do not already contain
|
||
information. This means 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 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="S_Bookmarks">5.2.7. Ajout des signets à une plongée</h4>
|
||
<div class="paragraph"><p>De nombreux plongeurs désirent annonter leurs plongées avec du texte
|
||
indiquant des événements particuliers, p. ex. "J’ai vu des dauphins", ou
|
||
"Déploiement de parachute de palier". Ceci peut ^être facilement réalisé:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Cliquez-droit à l’endroit voulu dans le profil de plongée. Cela fait
|
||
apparaître le menu contextuel du profil de plongée. Sélectionnez <em>Ajouter un
|
||
signet</em>. Un drapeau rouge est alors placé à cet endroit sur le profil de
|
||
plongée (voir <strong>A</strong> ci-dessous).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Cliquez-droit sur le drapeau rouge. Ceci fait apparaître un menu contextuel
|
||
(voir <strong>B</strong> ci-dessous). Sélectionnez <em>Modifier le nom</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Une boîte de texte s’affiche. Entrez le texte explicatif pour le signet
|
||
(voir <strong>C</strong> ci-dessous). Sélectionnez <em>OK</em>. Ceci enregistrera le texte associé
|
||
au signet.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
En survolant le signet rouge avec la souris, le texte associé est affiché
|
||
dans le bas de la boîte d’information (voir <strong>D</strong> ci-dessous).
|
||
</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="_enregistrer_les_informations_de_plongée_mises_à_jour">5.2.8. Enregistrer les informations de plongée mises à jour</h4>
|
||
<div class="paragraph"><p>Les informations entrées dans les onglets <strong>Notes</strong> et <strong>Équipement</strong> peuvent
|
||
être enregistrées en utilisant les deux boutons en haut à droite de l’onglet
|
||
<strong>Notes</strong>. Si vous cliquez sur le bouton <em>Appliquer les modifications</em>, les
|
||
données de la plongée sont enregistrées dans l’image mémoire de la
|
||
plongée. Si le bouton <em>Annuler les modifications</em> est cliqué, les données de
|
||
plongées nouvellement entrées sont effacées de la mémoire de l’ordinateur,
|
||
bien que le profil de plongée soit conservé. Lorsque l’utilisateur quitte
|
||
<em>Subsurface</em>, il y a une dernière notificatioin pour confirmer que les
|
||
nouvelles données doivent être enregistrées de manière permanente sur le
|
||
disque de l’ordinateur.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importer_les_informations_à_partir_d_8217_autres_sources_de_données_numériques_ou_d_8217_autres_formats_de_données">5.3. Importer les informations à partir d’autres sources de données numériques ou d’autres formats de données</h3>
|
||
<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>Many divers log their dives using the proprietary software provided by the
|
||
manufacturers of their dive computers. <em>Subsurface</em> can import dive logs
|
||
from a range of other dive log software. While import from some software is
|
||
supported natively, others require export of the dive log to an intermediate
|
||
format that can then be imported into <em>Subsurface</em>. Currently, <em>Subsurface</em>
|
||
supports importing CSV log files from several sources. Dive log import from
|
||
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
|
||
dive log software and some dive computers, like the Heinrichs & Weikamp
|
||
DR5. Finally, for some dive log software like Mares Dive Organizer we
|
||
currently recommend importing the logbook first into a web service like
|
||
<em>divelogs.de</em> and then import from there with <em>Subsurface</em>. Divelogs.de
|
||
supports a few additional logbook formats that <em>Subsurface</em> currently cannot
|
||
handle.</p></div>
|
||
<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, select
|
||
either <em>Import → Import log files</em> or <em>File → Open log file</em>. Notice that
|
||
the import adds the imported data to the current <strong>Dive list</strong>, and the open
|
||
style starts a new dive list. <em>Subsurface</em> supports the data formats of many
|
||
dive computers, including Suunto, Shearwater and some CCR equipment. 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 is more specific information to import data to <em>Subsurface</em>.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_utilisation_de_la_boîte_de_dialogue_universelle_d_8217_importation">5.3.1. Utilisation de la boîte de dialogue universelle d’importation</h4>
|
||
<div class="paragraph" id="Unified_import"><p>L’importation de plongées depuis d’autres logiciels se fait au travers d’une
|
||
interface universelle en sélectionnant <em>Importer</em> depuis le menu principal,
|
||
puis en cliquant sur <em>Importer des fichiers de plongée</em>. Ceci fera
|
||
apparaître la boîte de dialogue <strong>A</strong>, comme ci-dessous.</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>En bas à droite se trouve la liste déroulante avec la mention par défaut
|
||
<em>Dive Log Files</em> qui permet d’accéder aux différents types d’importations
|
||
directes disponibles, comme dans le dialogue <strong>B</strong> ci-dessus. Actuellement, il
|
||
s’agit de:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Carnet de plongée formatés en XML (DivingLog 5.0, MacDive et divers autres
|
||
systèmes de carnet de plongée)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Carnets de plongée Cochran
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Carnets de plongée formatés en UDDF (p. ex. Kenozooid)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Carnets de plongée formatés en UDCF
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs Poseidon MkVI CCR
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs APD Inspiration/Evolution CCR
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs LiquiVision
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs divelogs.de
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs OSTC Tools
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
JDiveLog
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Suunto Dive Manager (DM3, DM4, DM5)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Fichers DL7 utilisés par Diver’s Alert network (DAN)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs Underwater technologies AV1
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs Divesoft
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Logs Poseidon MK VI eCCR
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Carnet de plongée CSV (format texte ou tableau), y compris les logs APD CCR
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Sélectionner le format voulu puis le fichier recherché dans la fenêtre
|
||
contenant la liste des fichiers sur la droite de la boîte de dialogue,
|
||
ouvrira le carnet de plongée importé dans la <strong>Liste des plongées</strong> de
|
||
<em>Subsurface</em>. Certains autres formats, non accessible depuis la boîte de
|
||
dialogue d’importation, sont également supportés, comme expliqué ci-dessous.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_importation_depuis_ostctools">5.3.2. Importation depuis 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>Tous les périphériques H&W supportés par OSTCTools peuvent être importés
|
||
dans <em>Subsurface</em>. Ceci comprend les modèles OSTC, OSTC Mk2, OSTC 2N/2C,
|
||
OSTC3, OSTC Sport, et probablement, bien que non testés, Frog, OSTC2 et OSTC
|
||
CR.</p></div>
|
||
<div class="paragraph"><p>Ne perdez pas de vue qu’OSTCTools n’est <strong>pas</strong> un vrai logiciel de carnet de
|
||
plongée, mais plutôt un ensemble d’outils pour l’analyse et la gestion des
|
||
périphériques OSTC. Seules les données brutes de l’ordinateur de plongée
|
||
seront importées dans <em>Subsurface</em>, le reste des données (équipiers,
|
||
équipement, notes, etc.) doit être complété manuellement.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_importation_depuis_mares_dive_organizer_v2_1">5.3.3. Importation depuis Mares Dive Organizer V2.1</h4>
|
||
<div class="paragraph"><p>Vu que Mares utilise un logiciel Windows propriétaire non-compatible avec
|
||
les applications multi-plateformes, ces carnets de plongée ne peuvent pas
|
||
être importés directement dans <em>Subsurface</em>. Ceux-ci doivent être important
|
||
en suivant une procédure en trois étapes, en utilisant <em>www.divelogs.de</em>
|
||
comme passerelle pour extraire les informations du carnet de plongée.</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Exportez les données du carnet de plongée depuis le Mares Dive Organizer
|
||
vers votre bureau, en utilisant un fichier avec l’extension
|
||
<em>.sdf</em>. référez-vous à l’<a href="#Mares_Export">Annexe C</a> pour plus
|
||
d’information.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Data should then be imported into <em>www.divelogs.de</em>. First, create a user
|
||
account in <em>www.divelogs.de</em> and Log into that web site, then select <em>Import
|
||
Logbook → Dive Organizer from the menu on the left hand side. The
|
||
instructions must be carefully followed to transfer the dive information (in
|
||
_.sdf</em> format) from the Dive Organizer database to <em>www.divelogs.de</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Enfin, importez les plongées depuis <em>divelogs.de</em> vers <em>Subsurface</em>, en
|
||
suivant les instructions ci-dessous.
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_SmartTrakImport">5.3.4. Importer les logs Scubapro <em>SmartTrak</em></h4>
|
||
<div class="paragraph"><p><em>SmartTrak</em> stores the raw data from a Uwatec/Scubapro dive computer along
|
||
with a plethora of other data manually added by the user, ranging from dive
|
||
points to buddies data or DAN survey info. However, this is Microsoft
|
||
Windows-based propietary software by Uwatec (today Scubapro) using
|
||
Microsoft Access databases, preventing the integration the importer into the
|
||
<em>Subsurface</em> core application.</p></div>
|
||
<div class="paragraph"><p>A stand alone tool for Linux has been developed to import the <em>.slg</em> files
|
||
generated by SmartTrak to Subsurface’s <em>.xml</em> format. It can be built
|
||
together with <em>Subsurface</em> for Linux systems. Two dependencies need to be
|
||
installed in your system before building: <em>libglib2.0</em> and <em>libmdb2</em>.</p></div>
|
||
<div class="paragraph"><p>In addition, a web service is available for divelog convertions from
|
||
SmartTrak to <em>Subsurface</em> (see below).</p></div>
|
||
<div class="paragraph"><p>N’hésitez pas à contacter l'équipe de développement de <em>Subsurface</em> via
|
||
<a href="mailto:subsurface@subsurface-divelog.org">notre liste de diffusion</a> pour de
|
||
l’aide à l’importation des lofs <em>SmartTrak</em>.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="_compiler_em_smtk2ssrf_em">Compiler <em>smtk2ssrf</em></h5>
|
||
<div class="paragraph"><p>Assuming the above dependencies have been installed and the <em>Subsurface</em>
|
||
source tree is in the directory <em>~/src/subsurface</em>, then:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Move to the source tree directory.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Run " $ ccmake build " and set SMARTTRAK_IMPORT option to <strong>on</strong> (off by
|
||
default).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Generate with [c] and save and exit with [g].
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Build as you prefer, using the <em>build.sh</em> script (recomended) or moving to
|
||
build directory and running <em>make</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
After a successful build, there will be an executable named <em>smtk2ssrf</em> in
|
||
the <em>subsurface/build</em> directory. Copy or move it to a directory in your
|
||
$PATH, e.g. <em>~/bin</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_utilisation">Utilisation</h5>
|
||
<div class="paragraph"><p><em>smtk2ssrf</em> accepts 0, 2 or more parameters. If it is launched without
|
||
parameters in a graphical user interface, a simple window opens for choosing
|
||
the <em>.slg</em> file(s) to import and a destination file to store the
|
||
<em>Subsurface</em>-formatted data into (see image below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/smtk2ssrf.jpg" alt="FIGURE:Download from SmartTrak" />
|
||
</div>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/warning2.png" alt="Warning" />
|
||
</td>
|
||
<td class="content">Existing data in the destination file will be erased, so <strong>DO NOT</strong> use a
|
||
regular subsurface divelog file as a destination: rather, specify a <strong>new</strong>
|
||
filename as a destination.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>If launched from a command line with two or more parameters, the format is
|
||
as follows:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>$ smrtk2ssrf /input/file_1.slg /input/file_2.slg /output/file3.xml</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>where <em>input</em> is the directory containing the .slg file(s) and <em>output</em> is
|
||
the directory where the <em>Subsurface</em>-formatted output is written to. Files
|
||
<em>file_1.slg</em> and <em>file_2.slg</em> in the <em>input</em> directory are imported and
|
||
stored in <em>file3.xml</em> in the <em>output</em> directory. Check any warning and error
|
||
messages in the console or in the graphical window: some may be relevant as
|
||
support for Galileo family of dive computers is still a work in progress.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_for_the_lazy_a_web_service_to_convert_em_smarttrak_em_to_em_subsurface_em">For the lazy: a web service to convert <em>SmartTrak</em> to <em>Subsurface</em></h5>
|
||
<div class="paragraph"><p>Open the website at:</p></div>
|
||
<div class="paragraph"><p><em>https://thetheoreticaldiver.org/rch-cgi-bin/smtk2ssrf.pl</em></p></div>
|
||
<div class="paragraph"><p>This is a no-frills web service for converting <em>SmartTrak</em> dive logs to
|
||
<em>Subsurface</em>. Select the browse button. This allows you to browse your
|
||
computer directories and to select the <em>SmartTrak</em> divelog to be
|
||
converted. Once it has been selected, click the <em>Submit query</em> button. After
|
||
a short while, a dialog box appears (image below) for saving the converted
|
||
file to the local computer.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/strk2ssrf_web.jpg" alt="FIGURE:Web service to convert SmartTrak divelog" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_fusionner_les_plongées_importées_dans_un_carnet_de_plongée_existant">Fusionner les plongées importées dans un carnet de plongée existant</h5>
|
||
<div class="paragraph"><p>Open the new file (generated in the previous steps) using <em>Subsurface</em> and
|
||
check the dives and data. If everything is fine, close the <em>.xml</em> file and
|
||
open your regular divelog. Then from the <strong>Main Menu</strong> select <em>Import →
|
||
Import log file</em> and choose the <em>.xml</em> file containing the imported dives:
|
||
these will show in the <strong>Dive List</strong>, time ordered, along with the existing
|
||
dives. The new dives, although time ordered, will keep the numbering system
|
||
from <em>SmartTrak</em>, so a renumbering action is needed. See the section on
|
||
<a href="#S_Renumber">Renumbering the dives</a> for instructions on this topic.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_ImportingDivelogsDe">5.3.5. Importer des plongées depuis <strong>divelogs.de</strong></h4>
|
||
<div class="paragraph"><p>Importing 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> 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 shown (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.6. Importer des données au format CSV</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 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">Importer les plongées au format CSV à partir des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</h5>
|
||
<div class="paragraph"><p><em>CSV</em> files can be viewed using an ordinary text editor. A <em>CSV</em> file is
|
||
normally organized 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>Il y a deux types de carnets de plongée au format <em>CSV</em> pouvant être
|
||
importées dans <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 divemaster and information about cylinder
|
||
pressures before and after the dive, as well as comments 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, 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>you need 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>
|
||
Les données numériques (p. ex. la profondeur de plongée) sont-elles en
|
||
système métrique ou mesures impériales?
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>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>At the top left, there is a dropdown list containing pre- configured
|
||
settings for common dive computers and software packages.
|
||
If the <em>CSV</em> file being imported originated from any of
|
||
these pre-configured items, 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
|
||
successful data import.</p></div>
|
||
<div class="paragraph"><p>Complete this by ensuring 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, drag the
|
||
appropriate balloon from the upper area and drop it in the appropriate blue
|
||
cell at the top of the table. For example, 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 " # ", 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 all the column headings in the blue row of
|
||
cells correspond to the headings listed in the top part of the dialogue.
|
||
When finished, select the <em>OK</em> button on 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>Introduction aux fichiers <em>CSV</em> pour la plongée</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 that allows you to view or edit information
|
||
using a text editor like Notepad (Windows), gedit (Linux) or TextWrangler
|
||
(OS/X). There are two main advantages of the <em>CSV</em> format. First, the data
|
||
are easily editable as text without any proprietary software. Second, all
|
||
information is human-readable, not obscured by any custom or proprietary
|
||
attributes that proprietary software inserts 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 like spreadsheet-based dive logs and
|
||
some dive computers.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>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
|
||
organized 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>Les données ci-dessus ne sont pas aisément lisible pour un être
|
||
humain. Voici les mêmes informations dans un format séparé par des
|
||
tabulations :</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 you 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~2~ - Setpoint (Bar) pO~2~ - 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 be
|
||
used in many contexts for importing data into a <em>Subsurface</em> dive log.
|
||
Knowing a few basic things about the content of the <em>CSV</em> file helps with 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">But, the <em>CSV</em> import has a couple of caveats. 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="_importation_des_coordonnées_de_plongée_depuis_un_appareil_mobile_avec_gps">5.4. Importation des coordonnées de plongée depuis un appareil mobile avec GPS.</h3>
|
||
<div class="paragraph"><p>Un smartphone avec GPS peut être utilisé pour stocker les lieux de
|
||
plongées. Ceci est réalisé comme suit:</p></div>
|
||
<div class="paragraph"><p>Taking the mobile device along on the dive boat / liveabord while
|
||
automatically collecting dive site coordinate information.</p></div>
|
||
<div class="paragraph"><p>2) Uploading the coordinates from the mobile device to the <em>Subsurface</em>
|
||
Internet server.</p></div>
|
||
<div class="paragraph"><p>Syncronising the dives in the <em>Subsurface</em> dive list with the coordinates
|
||
stored on the <em>Subsurface</em> Internet server.</p></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> comporte deux outils pour réaliser cela :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
L’application <em>Subsurface Companion</em> (Android et iOS).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
L’application <em>Subsurface-mobile</em> (Android et iOS)
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Both of these applications perform the collection of dive site coordinates
|
||
and the synchronisation with dives in the <em>Subsurface</em> dive list. However,
|
||
the Companion App is not being further developed and has largely been
|
||
replaced by the <em>Subsurface-mobile</em> app. While the <em>Companion app</em> serves
|
||
exclusively to collect dive site coordinates and to make these available to
|
||
the <em>Subsurface</em> desktop version, <em>Subsurface-mobile</em> performs many of the
|
||
functions of the desktop version, including the management and viewing of
|
||
dive information. Below, we describe how to perform the above three steps
|
||
using each of the two mobile apps.</p></div>
|
||
<div class="paragraph"><p>Pour plus d’information sur l’utilisation de l’application <em>Subsurface
|
||
Companion</em>, cliquez <a href="#S_Companion"><em>ici</em></a>.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_storing_and_and_using_gps_locations_using_em_subsurface_mobile_em">5.4.1. Storing and and using GPS locations using <em>Subsurface-mobile</em></h4>
|
||
<div class="sect4">
|
||
<h5 id="_install_em_subsurface_mobile_em">Install <em>Subsurface-mobile</em></h5>
|
||
<div class="paragraph"><p>Find <em>Subsurface-mobile</em> on Google Play and install it on an Android
|
||
device. The app is free. The iOS version is currently
|
||
experimental. <em>Subsurface-mobile</em> has an extensive
|
||
<a href="https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual">user
|
||
manual</a> accessible from within that app.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_create_a_em_subsurface_mobile_em_account">Create a <em>Subsurface-mobile</em> account</h5>
|
||
<div class="paragraph"><p>This topic is discussed at length in the <em>Subsurface-mobile</em> user manual. In
|
||
the Credentials screen of <em>Subsurface-mobile</em> provide an e-mail address and
|
||
a user password that enables subsequent access. A PIN number is e-mailed
|
||
from the <em>Subsurface</em> Internet server to the e-mail address that has been
|
||
provided. Type the PIN into the appropriate text field in the Credentials
|
||
screen (see image below). The <em>Subsurface</em> Internet server notifies the
|
||
user that a new user has been registered.</p></div>
|
||
<div class="paragraph"><p><strong>N.B.:</strong> To successfully create a user account, the mobile device must have Internet connectivity,
|
||
either through the cellular network or via wifi.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/MobileCredentials.jpg" alt="FIGURE: Subsurface-mobile, credentials screen" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_configure_auto_collecting_of_gps_coordinates">Configure auto-collecting of GPS coordinates</h5>
|
||
<div class="paragraph"><p>Activate the main menu of <em>Subsurface-mobile</em> by selecting the "hamburger"
|
||
menu button at the bottom left of the <em>Subsurface-mobile</em> screen (see image
|
||
above), then select <em>GPS</em> → <em>Preferences</em> (see image below). The collection
|
||
of GPS locations is done in the background and automatically, using two
|
||
settings:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Time threshold.</em> (minutes). The app will try to get a location every X
|
||
minutes
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Distance threshold.</em> (meters). Minimum distance between two locations.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><strong>How are GPS coordinates collected?</strong> Assuming the diver 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 you move 50 m
|
||
from previous location, whichever happens first.
|
||
If subsequent locations are within a radius of 50 meters from the previous one,
|
||
a new location is not saved. If the diver is not moving, only one location is
|
||
saved, at least until the <em>Time-threshold</em> period has elapsed.
|
||
If the diver moves, a trace of the route is obtained by saving a location every 50 meters.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_activate_the_automated_recording_of_gps_locations">Activate the automated recording of GPS locations</h5>
|
||
<div class="paragraph"><p>The <em>Subsurface-mobile</em> GPS menu has an option at the bottom labled <em>Run
|
||
location service</em> (see image below). Selecting this starts the automated
|
||
recording of GPS positions.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/MobileGpsMenu.jpg" alt="FIGURE: Subsurface-mobile GPS menu" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_after_the_dive_stop_the_automated_recording_of_gps_locations">After the dive, stop the automated recording of GPS locations</h5>
|
||
<div class="paragraph"><p>Select the menu option <em>Disable location service</em> at the bottom of the
|
||
<em>Subsurface-mobile</em> GPS menu.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_upload_the_gps_locations_onto_the_em_subsurface_em_internet_server">Upload the GPS locations onto the <em>Subsurface</em> Internet server.</h5>
|
||
<div class="paragraph"><p><strong>N.B.:</strong> Uploading the GPS locations to the Internet can only take place if the mobile
|
||
device has reliable access to the Internet, either via a cellular network or
|
||
via a wifi connection. If the Internet is not accessible from the dive site(s),
|
||
then GPS uploading can only take place after the dive or after the dive trip,
|
||
when an Internet connection has been re-established.</p></div>
|
||
<div class="paragraph"><p>From the <em>Subsurface-mobile</em> main menu, select <em>GPS</em> → <em>Upload GPS
|
||
data</em>. The locations are uploaded.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_apply_the_stored_gps_locations_to_dives_on_the_em_subsurface_em_dive_list">Apply the stored GPS locations to dives on the <em>Subsurface</em> dive list.</h5>
|
||
<div class="paragraph"><p><em>Subsurface</em> collects the first GPS location recorded after the start of a
|
||
dive (obtained within <em>Subsurface</em> from either the dive computer or from the
|
||
manually-entered dive information) and before the end of a dive. These
|
||
coordinates are shown in the <em>Coordinates</em> field of the dive site panel for
|
||
each dive. Within the dive site panel, provide a name for the coordinates
|
||
that have been assigned to the dive, following the instructions under the
|
||
heading above <a href="#S_locations"><em>Location</em> management</a>.</p></div>
|
||
<div class="paragraph"><p>The
|
||
<a href="https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual">user
|
||
manual for <em>Subsurface-mobile</em></a> (accessible from within that app) contains
|
||
detailed instructions for performing the collection of GPS data and for
|
||
managing, uploading and synchronising this information.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_Companion">5.4.2. Importing GPS coordinates with the <em>Subsurface Companion App</em> for mobile phones</h4>
|
||
<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 dive locations on a dedicated Internet server. <em>Subsurface</em> can collect
|
||
the locations from the server.
|
||
To do this:</p></div>
|
||
<div class="sect4">
|
||
<h5 id="_create_a_companion_app_account">Create a Companion App account</h5>
|
||
<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 enabling 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="https://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_using_the_subsurface_companion_app_on_an_android_smartphone">Using the Subsurface companion app on an Android smartphone</h5>
|
||
<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 the <em>Subsurface</em>
|
||
companion page using an Internet browser. You can request a <strong>DIVERID</strong> using
|
||
this option, but it’s supplied via email and followed up by interaction with
|
||
the <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> to
|
||
activate the account.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Retrieve an account.</em> If you forget your <strong>DIVERID</strong> you will receive an
|
||
email to recover the ID string.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Use an existing account.</em> You are prompted for your <strong>DIVERID</strong>. The app
|
||
saves this <strong>DIVERID</strong> and doesn’t ask for it again unless you use 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, by selecting <em>File → Preferences → General</em>
|
||
from the main menu in <em>Subsurface</em> itself. This helps synchronization
|
||
between <em>Subsurface</em> and the Companion App.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><strong>Créer de nouveaux emplacements de plongée</strong></p></div>
|
||
<div class="paragraph"><p>Now you are ready to get a dive position and send it to the server. The
|
||
Android display looks like the left hand image (<strong>A</strong>) below, but without any
|
||
dives.</p></div>
|
||
<div class="paragraph"><p>Touch the + icon at the top right to add a new dive site. A menu with 3
|
||
options shows:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Current: A prompt for a place name is shown (or a request to activate the
|
||
GPS if it is turned off), after which the current location is saved.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Use Map: This option allows you to fix a position by searching a world
|
||
map. A world map is shown (see <strong>B</strong> below). Specify the desired position with
|
||
a <em>long press</em> on the touch sensitive screen (if the marked location is
|
||
wrong, simply choose a new location) and select the check symbol in the
|
||
upper right. A dialog is shown allowing you to enter the name of the dive
|
||
location and the date and time of the dive (see <strong>C</strong> below). In order to
|
||
import this dive location in <em>Subsurface</em>, 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 its
|
||
locations shown. Now select the appropriate locations, and select the check
|
||
symbol in the upper right to add them.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><strong>Liste des emplacements de plongée</strong></p></div>
|
||
<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 showing they need to be uploaded to the
|
||
server. You can select individual dive locations from the list. A selected
|
||
location has a check mark in the selection box on the left. Group operations
|
||
(like <em>Delete</em> or <em>Send</em>) are performed on several selected locations.</p></div>
|
||
<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations
|
||
or a map showing them. 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). Upon selecting 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>Upon selecting a dive (<strong>not</strong> selecting the check box), the name given to it,
|
||
date/time and GPS coordinates are shown with two options at the top of the
|
||
screen:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Edit (pencil): Change the name of the dive location.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Maps: Display a map showing the dive location. After editing and saving a
|
||
dive location (see <strong>C</strong> above), upload it to the web service, as explained
|
||
below.</p></div>
|
||
<div class="paragraph"><p><strong>Uploading dive locations</strong></p></div>
|
||
<div class="paragraph"><p>There are several ways to send locations to the server. The easiest is
|
||
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">Be careful! 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 class="paragraph"><p><strong>Settings on the Companion App</strong></p></div>
|
||
<div class="paragraph"><p>Selecting the <em>Settings</em> menu option results in the right hand image above
|
||
(<strong>B</strong>).</p></div>
|
||
<div class="paragraph"><p><em>Server and account</em></p></div>
|
||
<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 get it is to copy and paste from the confirmation email or
|
||
just type it in.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><em>Synchronisation</em></p></div>
|
||
<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 synchronize 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 class="paragraph"><p><em>Background service</em></p></div>
|
||
<div class="paragraph"><p>Instead of entering an unique dive location, you can leave the service
|
||
running in the background, allowing a continuous collection of GPS
|
||
locations.</p></div>
|
||
<div class="paragraph"><p>The settings below define the behavior 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 diver 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 diver is not moving, only one location is
|
||
saved. If the diver is moving, a trace of the route is obtained by saving a
|
||
location every 50 meters.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p><em>Other</em></p></div>
|
||
<div class="paragraph"><p><em>Mailing List.</em> The mail box for <em>Subsurface</em>. Users can send an email to
|
||
the Subsurface mailing list.</p></div>
|
||
<div class="ulist"><ul>
|
||
<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 class="paragraph"><p><em>Search</em></p></div>
|
||
<div class="paragraph"><p>Search the saved dive locations by name or by date and time.</p></div>
|
||
<div class="paragraph"><p><em>Start service</em></p></div>
|
||
<div class="paragraph"><p>Starts the <em>background service</em> following the previously defined settings.</p></div>
|
||
<div class="paragraph"><p><em>Disconnect</em></p></div>
|
||
<div class="paragraph"><p>This is admittedly a badly named option that disconnects the app from the
|
||
server. It resets 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 <em>Disconnect</em> option is useful if the Android device was
|
||
used to download the dive locations of another registered diver.</p></div>
|
||
<div class="paragraph"><p><em>Send all locations</em></p></div>
|
||
<div class="paragraph"><p>This option sends all locations stored in the Android device to the server.</p></div>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="S_iphone">Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h5>
|
||
<div class="paragraph"><p>The iPhone interface is quite simple. 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, 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 adding a dive,
|
||
the location service is started automatically and a red bar appears at the
|
||
bottom of the screen. After the dive, click on the red bar to end the
|
||
location service. While the location service is running you can only add
|
||
dives manually.</p></div>
|
||
<div class="paragraph"><p>You 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 web
|
||
service. There is no option to trigger upload manually.</p></div>
|
||
<div class="paragraph"><p><strong>Downloading dive locations to the <em>Subsurface</em> divelog</strong></p></div>
|
||
<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 start 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: selecting it updates the
|
||
locations of the newly entered or uploaded dives in <em>Subsurface</em>, i.e. it
|
||
applies the coordinates and names entered on the app to all the new dives
|
||
that match the date-times of the uploaded GPS localities. The names of dive
|
||
locations entered within <em>Subsurface</em> (i.e. before downloading the GPS
|
||
coordinates) have precedence over downloaded dive locations.</p></div>
|
||
<div class="paragraph"><p>Since <em>Subsurface</em> matches GPS locations from the mobile device and dive
|
||
information from the dive computer based on date-time data, automatic
|
||
assignment of GPS data to dives depends on agreeing date-time information
|
||
between the two devices. Although <em>Subsurface</em> has a wide range tolerance,
|
||
it may not be able to identify the appropriate dive if there is a large
|
||
difference between the time in the dive computer and that of the Android
|
||
device. This results 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). <em>Subsurface</em> may also 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 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">CONSEILS:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Background service</em> may fill the location list with unnecessary locations
|
||
that don’t correspond to the exact dive point but do correspond to the
|
||
boat’s route.
|
||
Right now, these locations are difficult to delete from the server. In some
|
||
situations it
|
||
is better to clean up the list on the mobile device before sending the dive
|
||
points to the web server by simply deleting the inappropriate
|
||
locations. This might be necessary, for instance, to keep the location list
|
||
clear to see dives in the web service map display (see above).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
It may also be useful 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>
|
||
<div class="sect2">
|
||
<h3 id="S_LoadImage">5.5. Ajouter des photos aux plongées</h3>
|
||
<div class="paragraph"><p>Many (if not most) divers take photographs during a dive. <em>Subsurface</em>
|
||
allows the storage and display of photographs for each dive. Photos are
|
||
superimposed on the dive profile at the times during the dive when they were
|
||
taken. They can also be viewed from the dive profile.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_chargement_des_photos_et_synchronisation_entre_l_8217_ordinateur_de_plongée_et_l_8217_appareil_photo">5.5.1. Chargement des photos et synchronisation entre l’ordinateur de plongée et l’appareil photo</h4>
|
||
<div class="paragraph"><p>Right-click on a dive or on a group of dives on the dive list, bringing up
|
||
the <a href="#S_DiveListContextMenu">Dive list context Menu</a>. Select the
|
||
appropriate option to import images either from file or from the
|
||
Internet. 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>If photos are imported from the Internet, provide a URL pointing to a single
|
||
photograph. If the URL points to a directory, no images are imported:
|
||
photos from the Internet need to be imported one at a time. If photos are
|
||
loaded from the Internet, <em>Subsurface</em> assumes there is an Internet
|
||
connection each time this photo is viewed within <em>Subsurface</em>.</p></div>
|
||
<div class="paragraph"><p>Having selected the local folder or Internet image to be imported, the time
|
||
synchronization dialog appears (see image below). The time synchronization
|
||
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. <em>Subsurface</em> attempts to synchronize these two devices so that the
|
||
exact times of photographs can be used to position photographs on the dive
|
||
profile.</p></div>
|
||
<div class="paragraph"><p><em>Subsurface</em> synchronise l’appareil photo avec l’ordinateur de plongée de
|
||
trois façons:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Pro-actively</strong>: Before the dive, ensure synchronization 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>: Writing down the exact camera time at the start of a dive allows using the
|
||
difference in time between the two devices. As long as the device
|
||
settings for time has not been changed in either device, the times of
|
||
both devices after the dive or even at the end of the day allows manually setting the time
|
||
difference in the <em>Time shift</em> dialog (see image below). Towards the top of the dialog is a time
|
||
setting tool immediately under the heading <em>Shift times of image(s) by</em>, in the image 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 and select the <em>Earlier</em> radio button.
|
||
This 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 synchronization is done.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage3b_f23.jpg" alt="FIGURE: Synchronization dialog" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>By photograph</strong>: There is a very slick way of achieving synchronization, requiring a
|
||
photograph of the face of the dive computer showing the time. <em>Subsurface</em> gets
|
||
the exact time the photograph was taken, using the metadata the camera stores within
|
||
each photo and compares this with the time visible on the photo. To do this, use the
|
||
bottom half of the <em>Time shift</em> dialog. In this case the top part of the dialog is ignored. Click on
|
||
the horizontal bar called <em>Select image of dive computer showing time</em>. This brings up
|
||
a file browser for selecting 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 was taken. Now set the date-time dialog to the left of the photo
|
||
so it 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 it can synchronize the devices. The image below 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="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/LoadImage3c_f23.jpg" alt="FIGURE: Synchronization dialog" />
|
||
</div>
|
||
</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 (see the red warning in the image
|
||
above). However, If the appropriate checkbox is selected (see image above)
|
||
these images can still be placed on the <em>Photos</em> tab of the <strong>Notes</strong> panel so
|
||
that all photos associated with a dive are visible, including photos taken
|
||
before or after the dive.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_visualiser_les_photos">5.5.2. Visualiser les photos</h4>
|
||
<div class="paragraph"><p>Après avoir été chargées, les images apparaissent à deux endroits:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
the <em>Photos</em> tab of the <strong>Notes</strong> panel (left part of image below).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
as tiny icons (stubs) on the dive profile at the appropriate positions
|
||
reflecting the time each photograph was taken. 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>Hover the mouse over any of the photo stubs. 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, allowing a good view of the photographs (see the image
|
||
below). <strong>Note</strong> that the thumbnail has a small dustbin icon in the bottom
|
||
right hand corner (see image above). Selecting the dustbin removes the image
|
||
from the dive. Be careful 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="_l_8217_onglet_em_photos_em">5.5.3. L’onglet <em>Photos</em></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 show
|
||
when during a dive a photo was taken. Single-click a thumbnail in the
|
||
<em>Photos</em> panel to select a photo. Double-click a thumbnail to view the
|
||
full-sized image, overlaying the <em>Subsurface</em> window. Deleted a photo 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_stockées_sur_un_disque_dur_externe">5.5.4. Photos stockées sur un disque dur externe</h4>
|
||
<div class="paragraph"><p>Most underwater photographers store 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 eases 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 synchronization (see text above) is used. 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 icon to the
|
||
left of the <em>Dive Profile</em>), the program shows a small white dot where each
|
||
photo should be on the dive profile. In addition the <em>Photos</em> tab shows
|
||
only the file names of the photos. If the external drive with the photos is
|
||
re-connected, the photos can be seen in the normal way.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_trouver_quelles_plongées_ont_des_photos_associées">5.5.5. Trouver quelles plongées ont des photos associées.</h4>
|
||
<div class="paragraph"><p>Inspecting each individual dive in order to determine whether there are
|
||
associated photos can be time consuming. There is a rapid way of seeing
|
||
which dives have associated photos and which not: activate the <em>Photos</em>
|
||
checkbox in the dropdown list obtained by right-clicking on the header bar
|
||
of the <strong>Divelist</strong>. In the <strong>Divelist</strong>, all dives with associated photographs
|
||
have an icon indicating whether the photographs were taken during the dive,
|
||
just before/after the dive or both during and before/after the dive. More
|
||
information is provided in the section dealing with <a href="#S_Divelist_columns">photo icons on the <strong>Divelist</strong></a>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="S_FindMovedImages">5.5.6. Déplacer des photos entre dossiers, disques durs ou ordinateurs</h4>
|
||
<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive,
|
||
<em>Subsurface</em> saves the directory path where the photo lies as well as the file name of the photo,
|
||
in order to find it when the dive is opened again.
|
||
If the photo or the whole photo collection is moved to another drive or to a different
|
||
machine, the path to the photo changes. Now, <em>Subsurface</em> looks for the photos at their original location before they were moved,
|
||
cannot find them and 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 to ease this inconvenience: 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:</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>
|
||
</ul></div>
|
||
<div class="paragraph"><p>if there is a match between a calculated fingerprint and the one calculated
|
||
when a photo was originally loaded into <em>Subsurface</em> (even if the original
|
||
file name has changed), automatically update the directory information so
|
||
that <em>Subsurface</em> can find the photo in the new moved directory.</p></div>
|
||
<div class="paragraph"><p>This is done 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 legacy 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 it
|
||
can access. 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:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The images associated with that dive are visible as thumbnails on the <strong>Dive
|
||
Profile</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If you edit anything in the <strong>Notes</strong> panel and save the edits by selecting
|
||
<em>Apply changes</em>.
|
||
</p>
|
||
</li>
|
||
</ul></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="paragraph"><p>This section gives examples of the versatility of <em>Subsurface</em> as a dive
|
||
logging tool.</p></div>
|
||
<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 doesn’t have
|
||
enough gas for the complete dive in a single cylinder; (b) if a 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 its size and pressure, as well as the gas composition within it.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Record the times at which the switch from one cylinder to another was done:</strong> This is information
|
||
tracked 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 or by creating a bookmark on the dive
|
||
computer.
|
||
</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 (image below).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>When this is complete, <em>Subsurface</em> indicates the appropriate use of
|
||
cylinders in the dive profile. Below is a two-cylinder dive, starting off
|
||
with EAN28, then changing cylinders to EAN50 after 26 minutes for
|
||
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 class="paragraph"><p>Several dive computers perform automatic recording of cylinder pressure. In
|
||
this case no manual intervention is needed. Older dive computers
|
||
(e.g. Uwatec Galileo, several Suunto models) handle more than one pressure
|
||
transducer on cylinders, switching from one sensor to another as the diver
|
||
switches among cylinders and providing a sequential record of cylinders
|
||
pressures during a dive. Some of the latest models (e.g. Shearwater Perdix
|
||
AI, Scubapro G2) record two or more pressure transducers concurrently and
|
||
continuously during the whole dive. In these cases <em>Suburface correctly
|
||
interprets the data. There is continuous effort within the _Subsurface</em>
|
||
development team to add new dive computer models to those that can be
|
||
downloaded from and to represent cylinder pressures correctly. Regardless of
|
||
the type of sensor handling of dive computers, technical divers are likely
|
||
to use both automated and manual methods of cylinder pressure logging when
|
||
more than two gases are used. However, automated recording of cylinder
|
||
pressure simplifies logging of sidemount dives (where two cylinders are
|
||
used). See the
|
||
<a href="https://subsurface-divelog.org/documentation/supported-dive-computers/">list
|
||
of supported dive computers</a>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_plongées_sidemount">5.6.2. Plongées Sidemount</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’s a popular
|
||
configuration for cave divers, sidemount diving can be done by recreational
|
||
divers who have completed the appropriate training. See the comments in the
|
||
last paragraph, above, about automated recording of cylinder
|
||
pressures. Manual logging of cylinder pressures during sidemount involves
|
||
three steps, exactly as with multi-cylinder dives above:</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 between these different
|
||
cylinders. In contrast, many dive computers that allow gas switching only distinguish between different
|
||
<em>gases</em> used, not among different <em>cylinders</em> used. This means when sidemount dives are downloaded
|
||
from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean
|
||
that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer
|
||
has the capability) 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 tedious 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 cylinders 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 shown on the dive profile.
|
||
Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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 shown 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 shown 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>
|
||
<div class="sect3">
|
||
<h4 id="S_sSCR_dives">5.6.3. Passive semi-closed circuit rebreather (pSCR) 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) are a technical advance in diving
|
||
equipment that recirculates the breathing gas a diver uses, 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 driving gas cylinder. 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
|
||
diver inhales. With active SCR (aSCR) equipment, in contrast, a small amount
|
||
of breathing gas is released continuously from the driving cylinder.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>To log pSCR dives, no special procedures are required. Use 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 that 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 as bottom gas 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. Plongées en recycleur circuit fermé (CCR)</h4>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/APD.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Closed system rebreathers also recirculate gas that has been
|
||
breathed. However, they use advanced technology to maintain a breathable
|
||
oxygen concentration:
|
||
a) remove carbon dioxide from the exhaled gas.
|
||
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, as well as Shearwater dive computers
|
||
connected to CCR systems. In contrast to a conventional recreational dive
|
||
computer, a CCR system computer usually 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 individual CCR dive profiles in the same way
|
||
it imports dive log data from other digital databases: one dive at a
|
||
time. However, the Shearwater based CCR systems are different in this
|
||
respect and allow multi-dive downloads.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="sect4">
|
||
<h5 id="_importer_une_plongée_ccr">Importer une plongée CCR</h5>
|
||
<div class="paragraph"><p>For Shearwater CCR controllers, or independent Shearwater CCR logs, just
|
||
download the dive log as would be the case for non-CCR dives. <em>Subsurface</em>
|
||
interprets the CCR dive log correctly. Except for Shearwater CCR dive
|
||
computers, CCR dive data are currently obtained from the proprietary
|
||
software provided when purchasing CCR dive equipment. See the section
|
||
dealing with <a href="#S_ImportingAlienDiveLogs">Importing dive information from
|
||
other digital sources</a> and
|
||
<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a> for more complete information. Use that software to download the dive
|
||
data into a known directory. 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 (labeled <em>Filter:</em>) of appropriate
|
||
devices that currently include (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, 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, click 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 false. If one of the three sensors provides false
|
||
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 boxes in the <em>Preferences</em> panel
|
||
(accessible by selecting <a href="#S_CCR_options"><em>File → Preferences →
|
||
Profile</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 checked.</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 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 pO~2~ 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 color-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 you hover
|
||
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 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 color of the computer-generated deco ceiling is white. This can
|
||
be set to red by checking the appropriate check box after selecting <em>File →
|
||
Preferences → Profile</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="_utiliser_la_carte_des_plongées_pour_obtenir_plus_d_8217_informations_sur_les_plongées">6.1. Utiliser la carte des plongées pour obtenir plus d’informations sur les plongées</h3>
|
||
<div class="paragraph"><p>The Dive Map has a number of buttons useful for manipulation several aspects
|
||
of a dive. These are:</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/MapViewMode.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Select this button to show the Dive Map as a satellite image or as a Google
|
||
Maps representation.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/MapViewPlus.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Zoom in. Select a smaller area of the map.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/MapViewMinus.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Zoom out. Select a larger area of the map.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="imageblock" style="text-align:left;">
|
||
<div class="content">
|
||
<img src="images/MapMenu.jpg" alt="FIGURE: Map menu" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>The "Hamburger" button on the top right-hand of the Dive Map activates the
|
||
Map menu. The items are:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Open location in <em>Google Maps</em>. Open the location of the active dive in a
|
||
separate Google Maps window with the dive site indicated by a Google Maps
|
||
teardrop marker.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Copy location to clipboard (decimal). Copy the coordinates of the active
|
||
dive to the clipboard in decimal degrees e.g. -25.933905 30.710572
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Copy location to clipboard (sexagesimal). Copy the coordinates of the active
|
||
dive to the clipboard in sexagecimal, e.g. 25°56’02.058"S 30°42’38.059"E
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Select visible dive locations. In the Dive List panel, highlight all the
|
||
dive sites visible in the Dive Map. This allows easy selection of the dives
|
||
within a particular geographical area to inspect them or to calculate
|
||
statistics for them.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_l_8217_onglet_strong_informations_strong_pour_une_seule_plongée">6.2. L’onglet <strong>Informations</strong> (pour une seule plongée)</h3>
|
||
<div class="paragraph"><p>L’onglet Informations donnée des informations résumées sur une plongée
|
||
sélectionnée dans la <strong>Liste des plongées</strong>. Les informations utiles
|
||
comprennent l’intervalle de surface avant une plongée, les profondeurs
|
||
maximale et moyenne de la plongée, le volume de gaz consommé, la
|
||
consommation équivalente à l’air (SAC) et le nombre d’unités de toxicité de
|
||
l’oxygène (OTU) atteint.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/info.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Consommation de gaz et calculs de la SAC (consommation équivalente à l’air):
|
||
<em>Subsurface</em> calcule la SAC et la consommation de gaz et tenant compte de
|
||
l’incompressibilité du gaz, en particuliter pour des blocs à des pressions
|
||
supérieures à 200 bar, les rendant plus précises. Référez-vous à
|
||
<a href="#SAC_CALCULATION">l’Annexe F</a> pour plus d’information.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ExtraDataTab">6.3. L’onglet <strong>Extra info</strong> (généralement pour des plongées séparées)</h3>
|
||
<div class="paragraph"><p>Lors de l’utilisation d’un ordinateur de plongée, celui-ci transmet souvent
|
||
des données qui ne peuvent pas être facilement standardisées parce que la
|
||
nature de ces informations diffère d’un ordinateur à l’autre. Ces données
|
||
conprennent souvent des informations de configuration, des métadonnées à
|
||
propos d’une plongée, le niveau de batterie, le temps d’interdiction de vol
|
||
(no fly) ou les gradient factor utilisés lors de la plongée. Quand cela est
|
||
possible, ces informations sont présentées dans l’onglet <strong>Extra
|
||
Info</strong>. Ci-dessous, vous trouverez une image affichant des données
|
||
supplémentaires pour une plongée utilisant un recycleur Poseidon.</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="_l_8217_onglet_strong_statistiques_strong_pour_un_groupe_de_plongées">6.4. L’onglet <strong>Statistiques</strong> (pour un groupe de plongées)</h3>
|
||
<div class="paragraph"><p>L’onglet Statistiques donne des statistiques résumées pour plusieurs
|
||
plongées, pour autant que plusieurs plongées soient sélectionnées dans la
|
||
<strong>Liste des plongées</strong> en utilisant les raccourcis standard Ctrl-clic ou
|
||
Maj-clic avec la souris. So une seule plongée est sélectionnée, les données
|
||
ne concernent que cette seule plongée. Cet onglet affiche le nombre de
|
||
plongées sélectionnées, la durée totale de ces plongées ainsi que les durées
|
||
minimale, maximale et moyenne parmi ces plongées, la température de l’eau et
|
||
la consommation équivalente à l’air (SAC). L’onglet affiche également la
|
||
plus petite et la plus grande profondeur atteinte pour ces plongées.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_DiveProfile">6.5. Le <strong>Profil de plongée</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>Parmi toutes les panneaux de <em>Subsurface</em>, le profil de plongée contient les
|
||
informations les plus détaillées concernant chaque plongée. Le profil de
|
||
plongée possède une <strong>barre de boutons</strong> sur el côté gauche, permettant le
|
||
contrôle de nombreuses options d’affichage. Les fonctions de ces boutons
|
||
sont décrites ci-dessous. L’objet principal du profil de plongée est le
|
||
graphique de la profondeur de la plongée en fonction du temps. En plus de la
|
||
profondeur, ce graphique affiche également les vitesses de descente et de
|
||
remontée en comparaison avec la vitesse recommandée. Cette information est
|
||
donnée en utilisant différentes couleurs:</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>Couleur</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Vitesse de descente (m/min)</strong></p></td>
|
||
<td align="left" valign="top"><p class="table"><strong>Vitesse de remontée (m/min)</strong></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">Rouge</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">Jaune</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">Vert clair</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">Vert foncé</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>Le profil permet également une lecture de la profondeur via les sommets et
|
||
planchers sur le graphique. Ainsi les utilisateurs, peuvent voir la
|
||
profondeur du point le plus bas et d’autres sommets. La profondeur moyenne
|
||
est affichée sous la forme d’une ligne grise, indiquant la moyenne de
|
||
profondeur à un moment précis de la plongée.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/scale.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Dans certains cas, le profil de plongée ne remplit pas toute la zone du
|
||
panneau <strong>Profil de plongée</strong>. Cliquer sur le bouton <strong>Ajuster l'échelle du
|
||
graphique</strong> dans la barre d’outils sur la gauche du profil de plongée
|
||
augmente la taille du profil de plongée pour remplir la zone du panneau.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>La <strong>température de l’eau</strong> est indiquée par une ligne bleue avec des valeurs de
|
||
température placées lors de changements significatifs.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="S_InfoBox">6.5.1. La boîte <strong>Information</strong></h4>
|
||
<div class="paragraph"><p>La boîte Information affiche un grand nombre d’informations concernant le
|
||
profil de plongée. Normalement, la boîte Information est située dans le coin
|
||
supérieur gauche du panneau <strong>Profil de plongée</strong>. Elle peut être déplacée
|
||
dans tout le panneau <strong>Profil de plongée</strong> en la cliquant-déplaçant avec la
|
||
souris à un endroit où elle ne masquera pas d’information importante. La
|
||
position de la boîte Information est enregistrée ré-utilisée pour les
|
||
analyses de plongée suivantes.</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>When 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 shown 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). Moving the cursor
|
||
horizontally lets the Information Box show information for any point along
|
||
the dive profile. It 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, also as gas density in
|
||
g/l), decompression requirements at that instant in time (Deco), time to
|
||
surface (TTS), the calculated ceiling, as well as of the statistics in the
|
||
Information Box, shown 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">Affiche la <strong>Profondeur maximale d’utilisation (MOD)</strong> d’une plongée, en
|
||
fonction du mélange gazeux utilisé. La MOD dépend de la concentration en
|
||
oxygène du gaz respiré. Pour l’air (21% d’oxygène), il vaut envuron 57m si
|
||
une pO<sub>2 maximale de 1.4 est choisie dans la section <strong>Préférences</strong>
|
||
(sélectionnez <em>Fichier → Préférences → Profil</em> et éditez le champ <em>pO</sub>2
|
||
dans le calcul de MOD</em>). En plongeant sous la MOD, il y a un risque
|
||
important d’exposition aux dangers liés à la toxicité de l’oxygène.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/NDL.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Show either 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 a diver 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. Even if the
|
||
profile contains several gas switches, TTS at a specific moment during the
|
||
dive is calculated using the current gas. TTS longer than 2 hours is not
|
||
accurately calculated and Subsurface only indicates <em>TTS > 2h</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/SAC.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Show the <strong>Surface Air Consumption (SAC)</strong>, an indication of the
|
||
surface-normalized 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 the respiratory rates of different dives can be compared. The
|
||
units for SAC is liters/min or cubic 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">Show 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 important to
|
||
divers 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 equaling 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 equaling the END.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>La figure (<strong>B</strong>) ci-dessous affiche une boîte d’information avec un ensemble
|
||
quasiment complet de données.</p></div>
|
||
<div class="sect4">
|
||
<h5 id="S_gas_pressure_graph">The Gas Pressure Bar Graph</h5>
|
||
<div class="paragraph"><p>On the left of the <strong>Information Box</strong> is a vertical bar graph showing 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>, shown 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 gas pressure, with the top margin of the
|
||
light green area showing the total gas pressure of ALL gases 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 equilibrium
|
||
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, with fast tissues on the left hand side.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The top black horizontal line indicates the inert gas pressure limit
|
||
determined by 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 <em>Profile</em>
|
||
tab of the <strong>Preferences Panel</strong> of <em>Subsurface</em>.
|
||
</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 a significant risk of decompression
|
||
sickness.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>These five values are shown on the left in the image above. The way the Gas
|
||
Pressure Bar Graph changes during a dive can be seen 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 start of a dive with the diver at the surface. The
|
||
pressures in all the tissue compartments are still at the surface
|
||
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, so their gas
|
||
pressures are 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 height 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 approach 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 class="sect3">
|
||
<h4 id="_événements_rapportés_par_l_8217_ordinateur_durant_la_plongée">6.5.2. Événements rapportés par l’ordinateur durant la plongée</h4>
|
||
<div class="paragraph"><p>Many dive computers record events during a dive. For instance, most dive
|
||
computers report alarms relating to high partial pressures of oxygen, to
|
||
rapid ascents or the exceeding of no-deco limits (NDL). On the other hand,
|
||
other events are classified as warnings and, for instance, occur when the
|
||
remaining gas in a cylinder falls below a predetermined limit, a deep stop
|
||
needs to be performed or the need to change gas during multicylinder
|
||
dives. Some dive computers also report notifications, e.g. when a safety
|
||
stop is initiated or terminated or when a predetermined amount of OTUs have
|
||
been incurred. The alarms, warnings and notifications differs from one dive
|
||
computer to another: some dive computers do not report any of the above
|
||
events, while others provide an extensive log of events. The reporting of
|
||
events is therefore a function of the dive computer used. In addition,
|
||
<em>Subsurface</em> does not always have the ability to detect all the events
|
||
reported by a specific dive computer.</p></div>
|
||
<div class="paragraph"><p>Events are indicated by symbols on the dive profile. Notifications are shown
|
||
as a white, round symbol with a letter <em>i</em>; warnings are indicated by a
|
||
yellow triangle and alarms by a red triangle. By moving the cursor over a
|
||
symbol, the explanation is given in the bottom-most line of the <em>Information
|
||
Box</em> (see image below, where the cursor is positioned over the alarm that
|
||
was reported).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/profile_symbols.jpg" alt="FIGURE: Profile notification symbols" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Some dive computers report <em>bookmarks</em> that the diver has set during the
|
||
dive. These are indicated as a small red flag on the profile and are
|
||
discussed more fully in the section on <a href="#S_Bookmarks"><em>inserting bookmarks</em></a>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_la_barre_d_8217_outils_du_profil">6.5.3. La barre d’outils du profil</h4>
|
||
<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,
|
||
nitrogen in black, and 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">Affiche la pression partielle d'<strong>oxygène</strong> durant la plongée. Ceci est
|
||
affiché sous les graphiques de profondeur et de température de l’eau.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/N2.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Affiche la pression partielle d'<strong>azote</strong> durant la plongée.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/He.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Affiche la pression partielle d'<strong>hélium</strong> durant la plongée. Ceci n’est
|
||
important que pour les plongeurs qui utilisent du Trimix, du Triox
|
||
(Helitrox) ou d’autres mélanges gazeux similaires.</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. Like the depth graph, the slope of the tank pressure provides
|
||
information about the momentary SAC rate (Surface Air Consumption) when
|
||
using an air integrated dive computer. Here the color coding is not
|
||
relative to some absolute values but relative to the mean normalized air
|
||
consumption during the dive. So areas in 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="paragraph"><p>When in planner mode, the SAC is set to be constant during the bottom part
|
||
of the dive as well during decompression. Therefore, when planning a dive,
|
||
the color is a representation of the breathing gas density.</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/Heartbutton.png" alt="Note" />
|
||
</td>
|
||
<td class="content">Cliquer sur le bouton Communter le rythme cardique permet d’afficher
|
||
l’information de rythme cardiaque pendant la plongée si l’ordinateur de
|
||
plongée est jumelé avec un détecteur de rythme cardique.</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 the 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 easily
|
||
recognizable; something free divers 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 you
|
||
wish 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">Les photos qui ont été ajoutées à une plongée peuvent être affichées sur le
|
||
profil en sélectionnant le bouton <strong>Communer l’affichage des images</strong>. La
|
||
position d’une photo sur le profil indique le moment exact où la photo a été
|
||
prise. Si le bouton n’est pas actif, les photos sont masquées.</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 occur 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 none of the Suunto dive computers make
|
||
these 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’s 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’s 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 because <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 a specific deco stop. This feature lets dive
|
||
computers 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">Si l’ordinateur de plongée calcule une palier et le rend disponible à
|
||
<em>Subsurface</em> durant le chargement des plongées, il peut être affiché sous la
|
||
forme d’une zone rouge en cochant le bouton "Commuter le plafond rapporté
|
||
par l’ordinateur de plongée" dans le panneau Profil.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling1.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Si le bouton <strong>Communter le plafond calculé</strong> du panneau Profil est cliqué, un
|
||
plafond, calculé par <em>Subsurface</em> est affiché en vert s’il existe pour une
|
||
plongée donnée (<strong>A</strong> dans l’image ci-dessous). Ceci peut être modifié de deux
|
||
façons:</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling2.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Si, en outre, le bouton <strong>Commuter l’affichage de tous les tissus</strong> est
|
||
cliqué, le plafond est affiché pour les compartiments de tissus selon le
|
||
modèle Bühlmann (<strong>B</strong> dans l’image ci-dessous).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/ceiling3.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">
|
||
<div class="paragraph"><p>Si, en plus le bouton <strong>Commuter le plafond calculé avec des incréments de
|
||
3m</strong> est cliqué, le plafond est affiché avec des incréments de 3m (<strong>C</strong> dans
|
||
l’image ci-dessous).</p></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="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="#GradientFactors_Ref">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. N.B.: The indicated gradient
|
||
factors are NOT the gradient factors in use by the dive computer, but those
|
||
used by Subsurface 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>
|
||
</td>
|
||
</tr></table>
|
||
</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 colored bar at the bottom of the <strong>Dive Profile</strong>. In general
|
||
oxygen is represented by a green bar, nitrogen a yellow bar and helium 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/icons/heatmap.png" alt="Note" />
|
||
</td>
|
||
<td class="content">
|
||
<div class="paragraph"><p>Display the tissue heat-map. The heat map summarises, for the duration of
|
||
the dive, the inert gas tissue pressures for each of the 16 tissue
|
||
compartments of the Bühlmann model. Blue colors mean low gas pressures in a
|
||
tissue compartment and thus on-gassing, green to red means excess gas in the
|
||
tissue and thus off-gassing. Fast to slow tissues are indicated from top to
|
||
bottom. The figure below explains in greater detail how the heat map can be
|
||
interpreted.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Heatmap.jpg" alt="Figure: Inert gas tissue pressure heat-map" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Image <strong>A</strong> on the left shows the <a href="#S_gas_pressure_graph">Gas Pressure
|
||
Graph</a> in the <strong>Information box</strong>, representing a snapshot of inert gas
|
||
pressures at a particular point in time during the dive. The inert gas
|
||
pressures of 16 tissue compartments are shown as dark green vertical bars
|
||
with the quick tissue compartments on the left and the slow tissue
|
||
compartments on the right. Refer to the section on the
|
||
<a href="#S_gas_pressure_graph">Gas Pressure Graph</a> for more details on the
|
||
different elements of this graph.</p></div>
|
||
<div class="paragraph"><p>Image <strong>B</strong> shows a gradient of unique colors, spanning the whole range of
|
||
inert gas pressures. It is possible to map the height of each of the dark
|
||
green vertical bars of <strong>A</strong> to a color in <strong>B</strong>. For instance, the fastest
|
||
(leftmost) dark green vertical bar in <strong>A</strong> has a height corresponding to the
|
||
medium green part of <strong>B</strong>. The height of this bar can therefore be summarised
|
||
using a medium green color. Similarly, the highest dark green bar in <strong>A</strong> is
|
||
as high as the yellow part of <strong>B</strong>. The 14 remaining tissue pressure bars in
|
||
<strong>A</strong> can also be translated to colors. The colors represent three ranges of
|
||
tissue inert gas pressure:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The bottom range in <strong>B</strong> (marked <em>On-gassing</em>) includes colors from light
|
||
blue to black, representing tissue gas pressures below the equilibrium
|
||
pressure of inert gas (bottom horizontal line in <strong>A</strong>). The measurement unit
|
||
is the % of inert gas pressure, relative to the equilibrium inert gas
|
||
pressure. In this range on-gassing of inert gas takes place because the
|
||
inert gas pressure in the tissue compartment is lower than in the
|
||
surrounding environment. Black areas in the heat map indicate that a tissue
|
||
compartment has reached the equilibrium inert gas pressure, i.e. the inert
|
||
gas pressure in the tissue compartment equals that of the water in which the
|
||
diver is. The equilibrium pressure changes according to depth.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The central range in <strong>B</strong> includes the colors from black to light green, when
|
||
the inert gas pressure of a tissue compartment is higher than the
|
||
equilibrium pressure but less than the ambient pressure. In this zone
|
||
decompression is not very efficient because the gradient of inert gas
|
||
pressure from tissue to the environment is relatively small and indicated by
|
||
dark green areas of the heat map.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The top range in <strong>B</strong> (marked <em>Off-gassing</em>) includes colors from light green
|
||
to red and white, repesenting tissue gas pressures above that of the total
|
||
ambient pressure (top of light green area of <strong>A</strong>). The measurement unit is
|
||
the % of inert gas pressure above ambient pressure, relative to the Bühlmann
|
||
M-value gradient (bottom of red area in <strong>A</strong>). These tissue pressures are
|
||
normally reached while ascending to a shallower depth. Below a value of
|
||
100%, this range indicates efficient off-gassing of inert gas from the
|
||
tissue compartment into the environment. Usually, efficient off-gassing is
|
||
indicated by light green, yellow or orange colors. Above 100% (red to white
|
||
in <strong>B</strong>) the M-value gradient is exceeded and the probability of
|
||
decompression sickness increases markedly.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Image <strong>C</strong> shows the color mapping of each of the vertical bars in <strong>A</strong>, the
|
||
fast tissues (on the left in <strong>A</strong>) depicted at the top and the slow tissue
|
||
compartments at the bottom of <strong>C</strong>. The highest vertical bar in <strong>A</strong> (vertical
|
||
bar 3rd from the left) is presented as the yellow rectangle 3rd from the top
|
||
in <strong>C</strong>. The 16 vertical bars in <strong>A</strong> are now presented as a vertical column
|
||
of 16 colored rectangles, representing a snapshot of tissue compartment gas
|
||
pressures at a particular instant during the dive.</p></div>
|
||
<div class="paragraph"><p>Image <strong>D</strong> is a compilation of similar color mappings of 16 tissue
|
||
compartments during a 10-minute period of a dive, the colors representing
|
||
the inert gas loading of a tissue compartment at a point in time during the
|
||
dive. Faster tissues are shown at the top and slower tissues at the bottom,
|
||
with time forming the horizontal axis of the graph. The column of rectangles
|
||
in <strong>C</strong> can be found on the horizontal axis between 9 and 10 minutes.</p></div>
|
||
<div class="paragraph"><p>The colors of the heat map are not affected by the gradient factor
|
||
settings. This is because the heat map indicates tissue pressures relative
|
||
to the Bühlmann M-value gradient, and not relative to any specific gradient
|
||
factor. For more information external to this manual see:</p></div>
|
||
<div class="paragraph"><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></div>
|
||
<div class="paragraph"><p>Since the colors of the heat map are not affected by the gradient factor(s),
|
||
the heat map is also applicable when using the VPM-B decompression model.</p></div>
|
||
<div class="paragraph"><p>The image below compares the profiles and heat maps for two planned
|
||
decompression dives to 60m: the first using the Bühlmann decompression
|
||
model, the second using the VPM-B decompression model. Both profiles have
|
||
the same total decompression time, but the VPM-B model requires deeper stops
|
||
early in the acent phase.</p></div>
|
||
<div class="paragraph"><p>In both profiles, the inert gas pressures in the faster tissues rise much
|
||
more rapidly than the slower tissues during the descent and bottom phase,
|
||
with the colors transitioning from light blue through blue and purple to
|
||
black. Similarly, the inert gas pressure in the fast tissues reduces more
|
||
rapidly than the slow tissues at each decompression stop, with colors
|
||
transitioning from red, orange and yellow to green and black.</p></div>
|
||
<div class="paragraph"><p>The comparison of the two profiles and heatmaps shows that by including deep
|
||
stops, the oversaturation gradient in the faster tissues early in ascent
|
||
phase is reduced. However, on-gassing of slower tissues continues during
|
||
the deep stops, which leads to greater oversaturation gradient in slower
|
||
tissues at the end of the dive.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/tissueHeatmap.jpg" alt="Figure: Inert gas tissue pressure heat-map" />
|
||
</div>
|
||
</div>
|
||
</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_le_menu_contextuel_du_profil_de_plongée">6.5.4. Le menu contextuel du Profil de plongée</h4>
|
||
<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 creating
|
||
Bookmarks, 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, with the time of the event
|
||
determined by the mouse cursor when the right mouse button was clicked to
|
||
bring up the menu. Gas Change events involve a selection of which gas is
|
||
being switched TO. The list of choices is based on the available gases
|
||
defined in the <strong>Equipment</strong> Tab. Setpoint change events open a dialog letting
|
||
you choose the next setpoint value. As in the planner, a setpoint value of
|
||
zero shows the diver is breathing from an open circuit system while any
|
||
non-zero value shows 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>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_organiser_le_carnet_de_plongée_manipuler_des_groupes_de_plongées">7. Organiser le carnet de plongée (manipuler des groupes de plongées)</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_DiveListContextMenu">7.1. Le menu contextuel de la Liste des plongées</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. It is 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>Le menu contextuel est utilisé pour de nombreuses fonctions décrites
|
||
ci-dessous.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="S_Divelist_columns">7.1.1. Personnaliser les colonnes affichées dans le panneau <strong>Liste des plongées</strong></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>, bringing up a list of columns that can be shown in
|
||
the dive list (see above). Check an items to be included in the <strong>Dive
|
||
List</strong>. 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 class="paragraph" id="S_Photos_divelist"><p>By selecting the <em>Photos</em> checkbox in the dropdown list, an icon is shown
|
||
indicating whether any photos are associated with a particular dive. There
|
||
are three icons:</p></div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/duringPhoto.png" alt="Note" />
|
||
</td>
|
||
<td class="content">Cette plongée contient des photos prises durant la plongée, généralement
|
||
prises avec un appareil ou caméra submersible.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/outsidePhoto.png" alt="Note" />
|
||
</td>
|
||
<td class="content">This dive has photographs taken immediately before or immediately after the
|
||
dive. This is useful for finding photos of dive teams or boats just
|
||
before/after the dive, whales or other surface animals seen just before or
|
||
after the dive, or of landscapes as seen from the boat.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/inAndOutPhoto.png" alt="Note" />
|
||
</td>
|
||
<td class="content">Cette plongée contient à la fois des photos prises pendant la plongée, et
|
||
juste avant ou juste après la plongée.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Renumber">7.2. Renuméroter les plongées</h3>
|
||
<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low
|
||
sequence numbers) to recent dives (higher sequence numbers). Numbering of
|
||
dives is not always consistent. For instance, when non-recent dives are
|
||
added, correct 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. This requires renumbering the dives. Do this by selecting
|
||
(from the Main Menu) <em>Log → Renumber</em>. Provide the lowest sequence number
|
||
to be used. This results in new sequence numbers (based on date/time) for
|
||
all the dives in the <strong>Dive List</strong> panel.</p></div>
|
||
<div class="paragraph"><p>Renumber a few selected dives in the dive list by selecting only 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 letting
|
||
the user specify the starting number for the process.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Group">7.3. Grouper des plongées en voyages et manipuler les voyages</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 does this by grouping dives that have
|
||
date/times not separated by more than two days and 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 of
|
||
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. To group the dives in a dive list,
|
||
(from the Main Menu) select <em>Log → Auto group</em>. The <strong>Dive List</strong> panel now
|
||
shows only the titles for the trips.</p></div>
|
||
<div class="sect3">
|
||
<h4 id="_éditer_le_titre_et_l_8217_information_associée_à_un_voyage_déterminé">7.3.1. Éditer le titre et l’information associée à un voyage déterminé</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 bar from the <strong>Dive List</strong>. This shows a <strong>Trip Notes</strong> tab in the <strong>Notes</strong>
|
||
panel. Here you 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 used, 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="_visualiser_les_plongées_d_8217_un_voyage_déterminé">7.3.2. Visualiser les plongées d’un voyage déterminé</h4>
|
||
<div class="paragraph"><p>Once the dives have been grouped into trips, you can expand one or more
|
||
trips by clicking the expansion button [+/-] on the left of each trip
|
||
title. This expands the selected trip, revealing individual dives during the
|
||
trip.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_fusionner_des_plongées_venant_des_voyages_différents_en_un_seul_voyage">7.3.3. Fusionner des plongées venant des voyages différents en un seul voyage</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="_diviser_un_voyage_en_plusieurs_voyages">7.3.4. Diviser un voyage en plusieurs voyages</h4>
|
||
<div class="paragraph"><p>If a trip includes, for example, ten dives, you can split this trip into two
|
||
trips (trip 1: top four dives; trip 2: bottom six dives) by selecting and
|
||
right-clicking the top four dives. The resulting context menu lets the user
|
||
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 show 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="_manipuler_des_plongées_uniques">7.4. Manipuler des plongées uniques</h3>
|
||
<div class="sect3">
|
||
<h4 id="_effacer_une_plongée_du_carnet_de_plongée">7.4.1. Effacer une plongée du carnet de plongée</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, 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>You can unlink dives from the trip to which they belong. 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="_décaler_l_8217_heure_de_début_d_8217_une_ou_plusieurs_plongées">7.4.4. Décaler l’heure de début d’une ou plusieurs plongées</h4>
|
||
<div class="paragraph"><p>Sometimes it’s necessary to adjust the start time of a dive. This may apply
|
||
to situations where dives are done in different time zones or when the dive
|
||
computer has a wrong time. To do this, select and right-click the dive(s) to
|
||
be adjusted. This brings up the context menu on which the <strong>Shift times</strong>
|
||
option should be selected. You must then specify the time (in hours and
|
||
minutes) by which the dives should be adjusted and click on the option of
|
||
whether the time adjustment should be earlier or later.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_fusionner_plusieurs_plongées_en_une_seule">7.4.5. Fusionner plusieurs plongées en une seule</h4>
|
||
<div class="paragraph"><p>Sometimes a dive is briefly interrupted, for example, 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. 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="_diviser_les_plongées_sélectionnées">7.4.6. Diviser les plongées sélectionnées</h4>
|
||
<div class="paragraph"><p>On some occasions, a diver reaches the surface and immediately dives
|
||
again. However, it may happen that the dive computer does not register a new
|
||
dive, but continues the previous dive due to the brief surface interval. In
|
||
this case it is possible to split a dive so that the two dives are shown as
|
||
independent dives on the <strong>Dive List</strong>. If this operation is performed,
|
||
<em>Subsurface</em> scans the selected dive(s) and splits the dive at points during
|
||
the dive where the depth is less than a metre.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_load_image_s_from_file_s">7.4.7. Load image(s) from file(s)</h4>
|
||
<div class="paragraph"><p>This topic is discussed in the section: <a href="#S_LoadImage">Adding photographs
|
||
to dives</a>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_load_image_from_web">7.4.8. Load image from web</h4>
|
||
<div class="paragraph"><p>This topic is discussed in the section: <a href="#S_LoadImage">Adding photographs
|
||
to dives</a>.</p></div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_annuler_les_manipuations_sur_les_plongées">7.4.9. Annuler les manipuations sur les plongées</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>split selected
|
||
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. Filtrer la liste des plongées</h3>
|
||
<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, selecting only some of
|
||
the dives based on their attributes, e.g. dive tags, dive site, divemaster,
|
||
buddy or protective clothing. For instance, filtering lets you 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 minimized by
|
||
selecting the <strong>green up-arrow</strong>. When minimized, only these three icons are
|
||
shown. The panel can be maximized by clicking the same icon that minimized
|
||
it. The filter may also be reset and closed by selecting the <strong>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 / divemaster), dive site and dive suit. Each of these 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 attributes within that check
|
||
list. For instance, typing "<em>ca</em>" in the filter text box above the tags
|
||
check list, results in the list being reduced to "<em>cave</em>" and
|
||
"<em>cavern</em>". Filtering the check list helps to rapidly find 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. Export le carnet de plongée ou des parties de celui-ci</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Il y a deux façons d’exporter des informations de plongée depuis Subsurface:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Exporter les informations de plongée vers <em>Facebook</em>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Export_other">Exporter des informations de plongée vers d’autres
|
||
destinations ou formats</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect2">
|
||
<h3 id="S_Facebook">8.1. Export des informations de plongée vers <em>Facebook</em></h3>
|
||
<div class="paragraph"><p>L’export des plongées vers <em>Facebook</em> est géré différemment des autres types
|
||
d’export car une connexion vers <em>Facebook</em> est nécessaire, nécessitant un
|
||
identifiant et un mot de passe. À partir du menu principal, sélectionnez
|
||
<em>Partager sur → Connecter à → Facebook</em> (image <strong>A</strong> ci-dessous). Un écran
|
||
de connexion s’affiche (image <strong>B</strong> ci dessous). Entrez l’identifiant et le
|
||
mot de passe <em>Facebook</em>. Depuis la fenêtre <em>Subsurface</em>, il est facile de
|
||
vérifier si <em>Subsurface</em> a une connection valide vers <em>Facebook</em> : Depuis le
|
||
"Menu principal", sélectionnez <em>Partager sur</em> (image <strong>A</strong>
|
||
ci-dessous). Normalement, l’option <em>Facebook</em> est grisée. Mais si une
|
||
connection vers <em>Facebook</em> existe, cette option est active (c’est à dire
|
||
écrit en noir et sélectionnable).</p></div>
|
||
<div class="paragraph"><p>Once logged into to <em>Facebook</em> , a panel is shown with a message: "<em>To
|
||
disconnect Subsurface from your Facebook account, use the <em>Share on</em> menu
|
||
entry</em>." Close this message panel.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/facebook1.jpg" alt="Figure: Facebook login" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Une fois qu’une connexion à <em>Facebook</em> est établie, transférer un profil de
|
||
plongée vers <em>Facebook</em> est facile. Dans le panneau <strong>Liste des plongées</strong> de
|
||
<em>Subsurface</em>, sélectionnez la plongée à transférer. Ensuite, à partir du
|
||
<strong>menu principal</strong>, sélectionnez <em>Partager sur → Facebook</em>. Une fenêtre
|
||
s’affiche, pour déterminer quelles informations seront transférées avec le
|
||
profil de plongée (image <strong>A</strong> ci-dessous). Pour transférer un profil de
|
||
plongée vers <em>Facebook</em>, le nom d’un album <em>Facebook</em> doit être fourni. Les
|
||
cases à cocher sur la partie gauche permettent de sélectionner des
|
||
informations supplémentaires à transférer avec le profil de plongée. Ces
|
||
informations sont affichées dans le champs de texte sur la partie droite du
|
||
panneau. (image <strong>A</strong> ci dessous). Personnalisez le message qui sera envoyé
|
||
avec le profil de plongée en modifiant les informations. Une fois les
|
||
informations supplémentaires ajoutées et vérifiées, sélectionner le bouton
|
||
<em>OK</em> qui effectue le transfert vers <em>Facebook</em>. Après le transfert, une
|
||
fenêtre de confirmation apparait ,indiquant le succès du transfert.</p></div>
|
||
<div class="paragraph"><p>À la fois l’album créé et la publication sur votre ligne temporelle seront
|
||
marquées comme privés. Pour que vos amis puissent la voir, connectez-vous à
|
||
<em>Facebook</em> depuis un navigateur ou l’application Facebook et modifiez les
|
||
permissions.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/facebook2.jpg" alt="Figure: Facebook data submission" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>If required, then close the <em>Facebook</em> connection by selecting, from the
|
||
<strong>Main Menu</strong>, <em>Share on → Disconnect from → Facebook</em> (image <strong>B</strong> above).</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Export_other">8.2. Exporter des informations de plongée vers d’autres destinations ou formats</h3>
|
||
<div class="paragraph"><p>For non-<em>Facebook exports</em>, the export function can be found 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>Un carnet de plongée ou une partie de celui-ci peut être enregistré dans
|
||
différents formats:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Format <em>Subsurface XML</em>. C’est le format utilisé nativement par
|
||
<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>, you need 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 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
|
||
recreational dives. To upload dives, you need a user 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. dive ceiling,
|
||
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 your dives to a smartphone or a tablet where it
|
||
would serve as a portable record of dives, useful for dive companies wishing
|
||
to verify the dive history of a diver, and doing away with the need to carry
|
||
an original logbook 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 you
|
||
select 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>TeX</em> format, a file for printing using the TeX typesetting software. Choose
|
||
a filename with a <em>.tex</em> extension. You will also need a template file, that
|
||
can be obtained from
|
||
<a href="http://www.atdotde.de/%7erobert/subsurfacetemplate/">http://www.atdotde.de/~robert/subsurfacetemplate/</a>
|
||
in the same directory as the <em>.tex</em> file. The file can then be processed
|
||
with plain TeX (not LaTeX), for example by running <em>pdftex filename.tex</em> on
|
||
the command line.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/texexample.png" alt="Figure: Export to TeX" />
|
||
</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 underwater where of each of those photos was
|
||
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 done 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 your pleasure, but it’s important
|
||
information required for admission to training courses or sometimes even
|
||
diving sites. The security of the dive log is critical. 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 you can access your dive log from anywhere in the world. 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 you 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 initialized, 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 let you load and save data to the <em>Subsurface
|
||
cloud storage</em> server.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the <em>Defaults Preferences</em> tab, you can select to use the <em>Subsurface cloud
|
||
storage</em> data as the default data file by checking the box marked <em>Cloud storage default file</em>.
|
||
This means the data from
|
||
the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts and saved there when <em>Subsurface</em> closes.
|
||
</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 synchronizes the
|
||
data with the cloud server the next time the 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
|
||
you can also access your 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 <em>Subsurface cloud storage</em>. The dive
|
||
information 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 you prefer not to use the integrated cloud storage of dive logs (and
|
||
don’t need the web access), it’s simple to store dive logs in the cloud
|
||
using several of the existing facilities on the Internet. For instance
|
||
<a href="https://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 a 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 your 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>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_user_space">10. Several <em>Subsurface</em> users on one desktop computer</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>A frequent need is for two or more persons to use <em>Subsurface</em> on the same
|
||
desktop computer. For instance members of a household may use the same
|
||
computer or one family member may perform dive uploads for other family
|
||
members/friends. There are two approaches for doing this.</p></div>
|
||
<div class="paragraph"><p><strong>A)</strong> If the different users of a desktop computer do not log onto the desktop/laptop under different user names
|
||
then the simplest way is for each person to use her/his own divelog file within Subsurface. In this case John
|
||
would work with the <em>Subsurface</em> file <em>johns-divelog</em> and Joan would use <em>joans-divelog</em>. Select
|
||
the appropriate dive log by selecting, from the <strong>Main Menu</strong>, <em>File → Open logbook</em> and then select your own
|
||
dive log file from the list of files lower down in the menu. However, a problem arises if the users
|
||
prefer different settings for <em>Subsurface</em>. For instance, one diver may prefer to see the dive ceiling in the
|
||
<strong>Profile Panel</strong> and photos icons in the <strong>Dive List</strong>, while the other may not have these preferences. In addition,
|
||
the cloud connection is normally unique for each <em>Subsurface</em> installation and if more than one user wishes to save
|
||
dive data on the cloud, it is inconvenient to open the <strong>Preferences</strong> and change the user-ID data every time
|
||
the cloud is accessed. To solve these problems, launch <em>Subsurface</em> with a <em>--user=<user name></em> command-line option.
|
||
John can then activate <em>Subsurface</em> with this command-line instruction:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>subsurface --user=John</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>while Joan can launch <em>Subsurface</em> using:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>subsurface --user=Joan</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>In this case, each user’s preferences, settings and cloud access information are stored separately, allowing
|
||
each diver to interact with <em>Subsurface</em> in her/his preferred way and with individual cloud access. The above
|
||
process can be made user-friendly by creating a link/shortcut with a desktop icon that executes the above
|
||
command-line instruction. Use of the <em>--user=</em> option therefore enables each user to create, maintain and
|
||
backup a separate dive log within a personalised user interface. This way, when each diver launches <em>Subsurface</em>,
|
||
it opens with the correct dive log as well as the appropriate display and backup preferences, and each diver
|
||
can access their own divelog on a mobile device using <a href="https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual"><em>Subsurface-Mobile</em></a>.</p></div>
|
||
<div class="paragraph"><p><strong>B)</strong> On the other hand, if the users log onto the same computer using different userIDs and passwords (i.e. users each
|
||
have a separate user space), <em>Subsurface</em> is available independently to each user and every diver automatically has a separate
|
||
user profile and settings, including unique cloud and <em>Subsurface-Mobile</em> access.</p></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_PrintDivelog">11. Imprimer un carnet de plongée</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible way 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>Certains choix doivent être fait avant l’impression:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Should the whole dive log be printed or only part of it? If only part is
|
||
required, select the required dives from the <strong>Dive List</strong> panel.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
If the dive profiles are printed, 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 dialogue below (image
|
||
<strong>A</strong>) appears. Three specifications are needed to get 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 before 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 color, done by checking the box with <em>Print in color</em>. If this
|
||
check box is not checked, printing is in black and white.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ol></div>
|
||
<div class="paragraph"><p>Under <em>Template</em> select a template to be used as the page layout. There are
|
||
several choices. (see image <strong>B</strong>, above).</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Table</em>: This prints a summary table of all dives selected (see below).
|
||
</p>
|
||
</li>
|
||
</ul></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>You 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, you
|
||
can change the options in the print dialogue, so the layout 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 operating
|
||
system, letting you choose a printer and 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="_créer_un_modèle_d_8217_impression_personnalisé_avancé">11.1. Créer un modèle d’impression personnalisé (avancé)</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. You 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">12. Configurer un ordinateur de plongée</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> vous permet de configurer un ordinateur de
|
||
plongée. Actuellement, les familles d’ordinateurs supportés sont
|
||
Heinrichs-Weikamp (OSTC 2/2N/2C, OSTC 3, Sport) et Suunto Vyper (Stinger,
|
||
Mosquito, D3, Vyper, Vytec, Cobra, Gekko et Zoop). De nombreux paramètres de
|
||
ces ordinateurs de plongée peuvent être lues et modifiées. Pour commencer,
|
||
assurez vous que les pilotes pour votre ordinateur de plongée sont installés
|
||
(également nécessaire pour télécharger les plongées) et que le nom de
|
||
périphérique de l’ordinateur de plongée est connu. Voir
|
||
<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">ANNEXE A</a> pour plus d’informations sur la manière de procéder.</p></div>
|
||
<div class="paragraph"><p>Une fois que l’ordinateur de plongée est connecté à <em>Subsurface</em>,
|
||
sélectionner <em>Fichier → Configurer l’ordinateur de plongée</em>, à partir du
|
||
menu principal. Sélectionner le nom du périphérique (ou le point de montage)
|
||
dans la liste déroulante, en haut du panneau de configuration et
|
||
sélectionner le bon modèle d’ordinateur de plongée à partir du panneau à
|
||
gauche (voir l’image ci-dessous).</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>En utilisant les boutons appropriés du panneau de configuration, les actions
|
||
suivantes peuvent être effectuées :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Récupérer les détails disponibles</strong>. Cela charge la configuration existante à partir de l’ordinateur de plongée
|
||
dans <em>Subsurface</em>, en l’affichant dans le panneau de configuration.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Enregistrer les modifications sur le périphérique</strong>. Cela change la configuration de l’ordinateur
|
||
de plongée pour correspondre aux informations affichées dans le panneau de configuration.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Sauvegarder</strong>. Cela enregistre la configuration dans un fichier. <em>Subsurface</em> demande
|
||
l’emplacement et le nom du fichier pour enregistrer les informations.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Restaurer une sauvegarde</strong>. Cela charge les informations à partir d’un fichier de sauvegarde et l’affiche
|
||
dans le panneau de configuration.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Mettre à jour le firmware</strong>. Si un nouveau firmware est disponible pour l’ordinateur de plongée,
|
||
il sera chargé dans l’ordinateur de plongée.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_Preferences">13. 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>, mostly affecting the way in which
|
||
<em>Subsurface</em> shows dive information to the user. The settings are in six
|
||
panels: <em>General</em>, <em>Units</em>, <em>Profile</em>, <em>Language</em>, <em>Network</em>, and
|
||
<em>Georeference</em>, all of which operate on the same principles: specified
|
||
settings can be applied to the display of the dive log by selecting
|
||
<em>Apply</em>. At this stage, any new settings only apply to the present session
|
||
and are not saved. In order to apply new settings permanently, select the
|
||
<em>Save</em> button. If you do not wish to apply the new preferences, select
|
||
<em>Cancel</em>.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_general">13.1. General</h3>
|
||
<div class="paragraph"><p>There are several headings in the <strong>General</strong> panel:</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref1_f23.jpg" alt="FIGURE: Preferences general page" />
|
||
</div>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Lists and tables</strong>: Specify the font type and font size of the
|
||
<strong>Dive Table</strong> panel: decreasing the font size allows one to see more dives on a screen.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Dives</strong>: For the <em>Default Dive Log File</em> specify the directory and
|
||
file name of your
|
||
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.
|
||
</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 initialized 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>: From the dropdown list, select the default cylinder to be used 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">13.2. Units</h3>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref2_f23.jpg" alt="FIGURE: Preferences Units page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Choose between metric and imperial units of depth, pressure, volume,
|
||
temperature and mass. By selecting the Metric or Imperial radio button at
|
||
the top, you can specify that all units are in the chosen measurement
|
||
system. Alternatively, if you select the <strong>Personalize</strong> radio button, units
|
||
can be selected independently, with some in the metric system and others in
|
||
imperial.</p></div>
|
||
<div class="paragraph"><p>Regardless 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="_profil">13.3. Profil</h3>
|
||
<div class="paragraph"><p>Ce panneau comporte trois sections:</p></div>
|
||
<div class="imageblock" id="S_CCR_options" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref4_f23.jpg" alt="FIGURE: Preferences Graph page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph" id="S_GradientFactors"><p><strong>Gas pressure display setup</strong>. Even though nitrogen and helium pressures are also included here, these items mainly pertain to oxygen management:
|
||
<strong> <em>Thresholds</em>: <em>Subsurface</em> can display graphs of the nitrogen, oxygen and the helium
|
||
partial pressures during
|
||
the dive, activated using the toolbar on the left of the <strong>Dive Profile</strong>
|
||
panel. For each of these graphs, specify a threshold value. If any of the graphs go
|
||
above the specified threshold, the graph is
|
||
highlighted in red, indicating the particular partial pressure threshold has been exceeded.
|
||
The pO<sub>2</sub> threshold is probably the most important one and a value of 1.6 is commonly used.
|
||
</strong> <em>pO<sub>2</sub> in calculating MOD</em> is used for calculating the maximum operative depth for a particular
|
||
nitrox or trimix gas mixture. A value of 1.4 is commonly used.</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
CCR Options: These options determine oxygen management for CCR dives:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Dive planner default setpoint</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>CCR: Show setpoints when viewing pO<sub>2</sub>:</em> With this checkbox activated, the pO<sub>2</sub>
|
||
graph on the dive profile has an overlay in red which indicates 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>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Ceiling display setup</strong>. These settings mostly deal with nitrogen and helium management
|
||
by determining how the decompression ceiling (ascent ceiling) is calculated and displayed:
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Draw dive computer reported ceiling red</em>: This checkbox does 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 a
|
||
dive computer calculates ceilings during a dive.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Algorithm for calculating ceiling</em>. Choose between the Bühlmann Z1H-L16
|
||
decompression model and the VPM-B model:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>VPM-B</em>: Provide a conservatism level for calculating the VPM-B ceiling. Values between 0
|
||
(least conservative) and 4 (most conservative) are valid.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Bühlmann: Set the <em>gradient factors</em> (GFLow and GFHigh) for calculcating the deco ceiling following
|
||
the ZH-L16 algorithm. GF_Low is the gradient factor at depth and GF_High is used at the surface.
|
||
At intermediate depths gradient factors between GF_Low and GF_High are used.
|
||
Gradient factors add conservatism to nitrogen and helium 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 inert gas loading and the deeper the ceilings are. Gradient
|
||
factors of 20/60 are considered conservative and values of 70/90 are considered
|
||
harsh.
|
||
For more information see:
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>pSCR options</em>. These preferences determine how passive semi-closed circuit (pSCR) dives
|
||
are planned and how the pSCR deco ceiling is calculated:
|
||
</p>
|
||
<div class="ulist" id="GradientFactors_Ref"><ul>
|
||
<li>
|
||
<p>
|
||
<em>Metabolic rate:</em> 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> The dilution ratio (or dump ratio) is the ratio of gas released to the
|
||
environment to that of the gas recirculated to the diver. A 1:10 ratio is commonly used.
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>Misc</strong>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
</ul></div>
|
||
</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>. 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 mean depth</em>: If this box is checked, the <strong>Dive Profile</strong> panel contains a grey line that shows
|
||
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
|
||
ascent.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_langue">13.4. Langue</h3>
|
||
<div class="paragraph"><p>Choisissez une langue que <em>Subsurface</em> utilisera.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref3_f23.jpg" alt="FIGURE: Preferences Language page" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Check the <em>System Default</em> language i.e. the language of the underlying
|
||
operating system if this is appropriate. This is the default setting in
|
||
<em>Subsurface</em>. To change it, uncheck this checkbox and pick a language /
|
||
country combination from the list of locations. The <em>Filter</em> text box 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 class="paragraph"><p>Dans cette section, spécifiez également les formats de date et d’heure pour
|
||
l’affiche des détails de plongée.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_réseau">13.5. Réseau</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 web services such as Cloud storage, the
|
||
<a href="#S_Companion"><em>Subsurface Companion app</em></a> or when you want to communicate
|
||
through a proxy.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Pref5_f23.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</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 your ISP.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Subsurface cloud storage</em>: To store your dive log in the cloud, a valid email address
|
||
and password are required. This lets <em>Subsurface</em> email security information
|
||
regarding cloud storage to you, and to set up 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 you do other things 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 you subscribe 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>, you ensure a local copy of that userID is saved.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_géoréférencement">13.6. Géoréférencement</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 search on the Internet is done to find the
|
||
name of the closest known location. 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_f23.jpg" alt="FIGURE: Georeference panel" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="S_DivePlanner">14. Le planificateur de plongée de <em>Subsurface</em></h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessed by selecting
|
||
<em>Log → Plan Dive</em> from the main menu. It allows calculation of inert gas
|
||
load during a dive by using the Bühlmann ZH-L16 algorithm with the addition
|
||
of gradient factors as implemented by Erik Baker, or using the VPM-B model.</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">Le planificateur de plongée de <em>Subsurface</em> EST EN PHASE EXPÉRIMENTALE et
|
||
suppose que l’utilisateur est déjà familier avec l’interface utilisateur de
|
||
<em>Subsurface</em>. Il est utilisé explicitement aux conditions suivantes :</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
L’utilisateur est bien informé au sujet de la planification de plongée et a
|
||
la formation nécessaire pour faire une planification de plongée.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
L’utilisateur planifie des plongées dans les limites de sa certification.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
La planification de plongée se base sur les caractéristiques d’une <em>personne
|
||
normale</em> et ne peut compenser les caractéristiques physiologiques, l'état de
|
||
santé, l’historique personnel et les caractéristiques du mode de vie.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
La sécurité d’une planification de plongée dépend en grande partie de la
|
||
façon dont le planificateur est utilisé.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
L’utilisateur est familier avec l’interface de <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Un utilisateur qui n’est pas absolument certain d’un des prérequis ci-dessus
|
||
ne devrait pas utiliser cette fonction.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div></div>
|
||
<div class="sect2">
|
||
<h3 id="_l_écran_du_planificateur_de_plongée_em_subsurface_em">14.1. L'écran du planificateur de plongée <em>Subsurface</em></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 sections on the left hand and bottom side of the screen. They are:
|
||
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> on which the profile of the
|
||
dive can be manipulated directly by dragging and clicking as explained
|
||
below. This feature makes the <em>Subsurface</em> dive planner unique in ease of
|
||
use.</p></div>
|
||
<div class="paragraph"><p>At the bottom right is a text panel with a heading of <em>Dive Plan
|
||
Details</em>. This is where the details of the dive plan are provided in a way
|
||
that can easily be copied to other software. This is also where any warning
|
||
messages about the dive plan are printed.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/PlannerWindow1.jpg" alt="FIGURE: Dive planner startup window" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_plongées_en_circuit_ouvert">14.2. Plongées en circuit ouvert</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Towards the center 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>
|
||
Circuit ouvert (option par défaut)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
CCR
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
pSCR
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Choisissez l’option Circuit ouvert.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the top left-hand area of the planning screen, be sure 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 meters,
|
||
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="#cylinder_definitions">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 start pressure of this cylinder. By leaving the
|
||
oxygen concentration (O<sub>2</sub>%) field 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>
|
||
Le tableau <em>Gaz disponibles</em> inclut trois champs de profondeur de gaz,
|
||
nommés:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Deco switch at: the switch depth for deco gases. Unless overridden by the user, this will be
|
||
automatically calculated based on the Deco pO<sub>2</sub> preference (default 1.6 bar)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Bot. MOD: the gas Maximum Operating Depth (MOD) if it is used as a bottom mix. Automatically
|
||
calculated based on the Bottom pO<sub>2</sub> preference (default 1.4 bar). Editing this field will modify the
|
||
O<sub>2</sub>% according to the depth set. Set to <em>'*</em>' to calculate the best O<sub>2</sub>% for the dive maximum depth.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
MND: the gas Maximum Narcotic Depth (MND). Automatically calculated based on the Best Mix END
|
||
preference (default 30m / 98 ft). Editing this field will modify the He% according to the depth set.
|
||
Set to <em>'*</em>' to calculate the best He% for the dive maximum depth.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Le profil d’une plongée planifiée peut être créé de deux façons:
|
||
</p>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Drag the waypoints (the small white circles) on the existing dive profile 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
|
||
setpoint</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="_plongées_loisir">14.2.1. Plongées loisir</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 maximum time a diver can stay at the current depth without needing 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. But few dives are
|
||
done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means
|
||
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 load, for not remaining at maximum depth during
|
||
previous dives, so a longer subsequent dive can be planned.
|
||
For the planner to work it’s crucial to upload all previous dives
|
||
onto <em>Subsurface</em> before doing dive planning.
|
||
To plan a dive, the appropriate settings need to be defined.</p></div>
|
||
<div class="paragraph"><p>Ensure the date and time is set to that of the intended dive. This allows
|
||
calculation of the nitrogen load incurred during previous dives.</p></div>
|
||
<div class="ulist"><ul>
|
||
<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
|
||
working 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 accurate,
|
||
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 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 to bring a
|
||
buddy to the surface using gas sharing. How much gas is used in sharing
|
||
depends on the depth of the ascent. This can be difficult 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’s supposed to be for the additional gas used
|
||
when there’s a problem and your pulse rate goes up when you start 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 described 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>
|
||
La vitesse de remontée peut être modifiée. Les vitesses de remontée par
|
||
défaut sont celles qui sont considérées comme sûres pour les plongées
|
||
loisir.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The dive profile in the planner shows 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
|
||
meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the
|
||
dive is limited by the amount of air in the cylinder.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Planner_OC_rec.jpg" alt="FIGURE: A recreational dive plan: setup" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect3">
|
||
<h4 id="_plongées_en_circuit_ouvert_non_loisir_incluant_une_décompression">14.2.2. Plongées en circuit ouvert non loisir, incluant une décompression</h4>
|
||
<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or
|
||
using multiple breathing gases. These dives are planned in three stages:</p></div>
|
||
<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is done 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 (GFHigh and GFLow
|
||
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 on decompression stops early 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, albeit
|
||
at the cost of higher tissue compartment pressures in the slow tissues.
|
||
When selecting one of these models, keep in mind they are NOT exact
|
||
physiological models but only mathematical models that appear to work in
|
||
practice.</p></div>
|
||
<div class="paragraph"><p>Please note as well that there is an intrinsic assumption of the VPM-B model
|
||
that off-gassing only happens during the ascent phase of the dive (which is
|
||
the part controlled by the planner). Thus it is possible to get misleading
|
||
results if you manually enter waypoints well in the decompression phase of
|
||
your dive. This is particularly relevant when editing a dive read from disk
|
||
in the planner since that will have waypoints up to the surface. Thus for
|
||
those dives, first delete all waypoints during the ascent phase. This is
|
||
most easily done by holding the Ctrl- or Command-key while clicking on the
|
||
trash can icon next to the first ascent waypoint in the table on the left
|
||
hand side.</p></div>
|
||
<div class="paragraph"><p>Pour plus d’information en dehors de ce manuel, voir:</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>
|
||
<a href="https://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. Un excellent livre non technique qui traite à la fois des
|
||
modèles de décompression Bühlmann et VPM-B.
|
||
</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, using the mean depth as a
|
||
yardstick. The mean depth of the dive plan is shown 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, 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>).
|
||
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. The depth at which switching to a gas
|
||
takes place can be edited in the
|
||
<em>Available Gases</em> dialog. Normally, the planner decides on switching to a new gas when, during
|
||
ascent, the partial pressure of the new gas has decreased to 1.6 bar.</p></div>
|
||
<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary
|
||
consideration. Divers need 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
|
||
liters/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 guess
|
||
is not sufficient and you needs to
|
||
monitor 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 you exceeds the total amount of gas available. Good practice demands that divers 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.
|
||
In addition to calculating the total gas consumption for every cylinder the planner provides one way
|
||
of calculating the recommended volume of bottom gas which is needed for safe ascent to the
|
||
first deco gas change depth or the surface. This procedure is called the "minimum gas" or "rock bottom"
|
||
consideration and it is used by various (but not all)
|
||
technical diving organisations. See the text below for a detailed explanation.</p></div>
|
||
<div class="paragraph"><p>Now you can start the detailed time-depth planning of the dive. <em>Subsurface</em>
|
||
offers an unique graphical interface for doing planning. The mechanics are
|
||
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
|
||
20 min is offered in the blue design surface in the top right hand part of
|
||
the planner window. 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 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
|
||
existing settings. If any of the management limits (for nitrogen, oxygen or
|
||
gas) are 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 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). In most cases <em>Subsurface</em> computes additional
|
||
way points in order to fulfill decompression requirements for that dive. A
|
||
waypoint can also be moved by selecting it 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 get a precise presentation of the dive plan. In fact, it is
|
||
sometimes more easy to create the whole dive profile by editing the <em>Dive
|
||
Planner Points</em> dialog.</p></div>
|
||
<div class="paragraph"><p>Show 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 planned during the ascent to the surface.</p></div>
|
||
<div class="paragraph"><p>Cylinders used for the plan need to be entered in the table of <em>Available
|
||
gases</em>. In the column <em>Type</em> select the appropriate cylinder size by using
|
||
the dropdown list that appears when double-clicking a cell in this
|
||
column. By default, a large number of sizes are listed, and a new cylinder
|
||
size can be created by typing this into the text box. The cylinder size,
|
||
start pressure and default switch depths are initialised
|
||
automatically. Specify the gas composition (e.g. helium and oxygen
|
||
content). A non-zero value in the "CC setpoint" 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 and the planner only
|
||
considers gas changes in OC mode.</p></div>
|
||
<div class="paragraph"><p>Enter dive profile segments in the <em>Dive planner points</em> table by providing
|
||
a time duration for a segment as well as its final depth. If more than one
|
||
cylinder is used during the dive, ensure that the appropriate cylinder is
|
||
selected for each segment of the dive plan by double-clicking the cell and
|
||
selecting the appropriate cylinder from the dropdown list in the <em>Used gas</em>
|
||
column. If required, insert a row in the <em>Dive planner points</em> table by
|
||
adding a new line and then setting the <em>Run time</em> value appropriately. In
|
||
image A below, a segment (using an EAN50 cylinder) has been added and you
|
||
wish to use this gas during the very start of the dive (the other gas is not
|
||
breathable at the surface). Upon pressing Enter on the keyboard, that
|
||
segment is moved to the top of that table and the plan is adjusted
|
||
automatically to take into account this new segment of the dive plan (image
|
||
B below).</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/planner1.jpg" alt="FIGURE: Planning a dive: segments" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Ci-dessous, vous trouverez un exemple d’une planification de plongée
|
||
utilisant du Tx20/30 et l’algorithme Bühlmann, suivie d’une remontée
|
||
utilisant du EAN50 et utilisant les réglages décrits ci-dessous.</p></div>
|
||
<div class="imageblock" style="text-align:center;">
|
||
<div class="content">
|
||
<img src="images/Planner_OC_deco.jpg" alt="FIGURE: Planning a dive: setup" />
|
||
</div>
|
||
</div>
|
||
<div class="paragraph"><p>Once the above steps have been completed, save 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>Les détails du plan de plongée</strong></p></div>
|
||
<div class="paragraph"><p>On the bottom right of the dive planner, under <em>Dive Plan Details</em>, the
|
||
details of the dive plan are provided. These 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 class="paragraph"><p>The planner has a check box <em>Display plan variations</em>. By checking this box,
|
||
the planner provides information about a dive that is a little deeper or
|
||
slightly longer than the planned dive. This is found near the top of the
|
||
<em>Dive plan details</em> where the dive duration is indicated. The information is
|
||
intended to be used if it is necessary to modify the ascent "on the fly" in
|
||
the case of unexpected deviations from the dive plan during the dive.
|
||
Checking this option creates a lot of additional computation, to such a
|
||
degree that the planner is slower than otherwise. The information is
|
||
typically given as:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Runtime: 53min + 0:52/m + 4:21/min</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>This indicates:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Calculated dive duration is 53 min.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
For each extra meter in depth during the bottom phase of the dive, the
|
||
ascent duration increases by 52 seconds.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
For each extra minute of bottom time, the duration increases by 4 min 21
|
||
sec. Thus, if the bottom time is two minutes longer than planned, ascent
|
||
duration duration will be (2 * 4min 21 sec) = 8 minutes 42 sec longer and
|
||
would probably require that each deco stop is 8:42/53:00 = around 16% longer
|
||
than planned. These calculations are only applicable for small deviations
|
||
from the dive plan, not for larger deviations.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p><strong>Minimum gas requirements</strong></p></div>
|
||
<div class="paragraph"><p>The planner also estimates the <strong>minimum gas</strong> pressure required for safe
|
||
ascent after an event that causes the dive to be aborted. The calculation
|
||
assumes that in worst case an out of gas (OoG) situation occurs at the end
|
||
of the planned bottom time at maximum depth. This OoG event forces the buddy
|
||
team the share the gas of one diver and that they require an additional
|
||
period of time at maximum depth to solve the problem at hand. In addition
|
||
the combined SAC of both divers is increased by an estimated factor compared
|
||
to the SAC factor of a single diver under normal conditions. The result of
|
||
the minimum gas calculation for the bottom gas is printed to the planner
|
||
output. No automatic checks are performed based on this result. The feature
|
||
only gives valid results for simple, rectangular shaped single level dive
|
||
profiles. For multi level dives one would need to check every leg of the
|
||
profile independently.</p></div>
|
||
<div class="paragraph"><p>There are two selector boxes on the left of the <em>Dive plan details</em>:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<strong>SAC factor</strong>. This is an estimate of the degree to which your SAC increases if a critical problem arises underwater,
|
||
e.g. gas sharing or entanglement. Realistic values range from 2 to 5, reflecting the gas use of two divers sharing
|
||
a single gas cylinder after an OoG situation.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<strong>Problem solving time</strong>. This is an estimate of how long you would take to solve the problem before starting the ascent
|
||
to terminate the dive. The default value is 2 minutes.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Using the above information, the planner then estimates what the minimum
|
||
bottom gas cylinder pressure needs to be for a safe ascent. This information
|
||
is given near the bottom of the <em>Dive plan details</em>, following the
|
||
calculation of bottom gas used during the dive if it exactly follows the
|
||
plan. the minimum gas is typically given as:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>Minimum gas (based on 2.0xSAC/+1min@81m): 2130 l/90bar/Δ:+80bar</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>This indicates:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Within parentheses, the <strong>SAC factor</strong> and <strong>Problem solving time</strong> specified.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The number of liters of back gas required for a safe ascent (2130 litres in
|
||
the example above)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The number of bars of back gas required for a safe ascent (90 bars in the
|
||
example above).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
The delta-value: number of bars of back gas available at the end of the
|
||
bottom section of the dive, <em>over and above</em> the minimum gas requirement (80
|
||
bars in the above example). A positive delta reflects a safe plan; a
|
||
negative delta indicates insufficient gas for a safe ascent.
|
||
</p>
|
||
</li>
|
||
</ul></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 <strong>plan variations</strong> and <strong>minimum gas</strong> estimates are only guidelines for a
|
||
diver performing dive planning, intended to enhance the safety of executing
|
||
a particular dive plan. They are NOT precise and should NOT be relied upon
|
||
as the only safety features in dive planning. Interpret these estimates
|
||
within the framework of your formal training to perform dive planning.</td>
|
||
</tr></table>
|
||
</div>
|
||
</div></div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_planning_pscr_dives">14.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 → Profile</em>
|
||
from the main menu, where the gas consumption calculation takes into account the pSCR dump
|
||
ratio (default 1:10) as well as the metabolic rate. The calculation also takes the oxygen drop
|
||
across the mouthpiece of the rebreather into account. If the
|
||
pO<sub>2</sub> drops below what is considered safe, a warning appears in the <em>Dive plan
|
||
details</em>. A typical pSCR cylinder setup is very similar to an open circuit dive;
|
||
one or more drive cylinders, possibly with different bottom and decompression
|
||
gases, including gas switches during the dive like in open circuit diving.
|
||
Therefore, the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables
|
||
are very similar to that of a open circuit dive plan, described above. 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_pSCR.jpg" alt="FIGURE: Planning a pSCR dive: setup" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_planifier_des_plongées_ccr_recycleur">14.4. Planifier des plongées CCR (recycleur)</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 → Profile</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. 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
|
||
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_CCR.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 liters are the norm.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_Replan">14.5. Modifier une planification existante</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 no way to
|
||
change a saved dive plan. To change 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, - earlier dives are now taken into
|
||
account -) 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="_planifier_des_plongées_successives">14.6. Planifier des plongées successives</h3>
|
||
<div class="paragraph"><p>Repetitive dives can easily be planned if the dates and start times of the
|
||
repetitive dive set are specified appropriately in the top left-hand <em>Start
|
||
Time</em> field. <em>Subsurface</em> calculates the gas loading figures and the affect
|
||
of the first dive is evaluated on later dives.</p></div>
|
||
<div class="paragraph"><p>If you have just completed a long/deep dive and are planning another dive,
|
||
then highlight, in the <strong>Dive List</strong>, the dive that has just been logged then
|
||
activate the planner. Depending on the start time of the planned dive, the
|
||
planner takes into account the gas loading during the completed dive and
|
||
plans accordingly.</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 you
|
||
want to plan a dive using this configuration, 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="_imprimer_un_plan_de_plongée">14.7. Imprimer un plan de plongée</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. You can also cut and paste the <em>Dive Plan
|
||
Details</em> to include in a text file or word processing document.</p></div>
|
||
<div class="paragraph"><p>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> function 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 class="sect2">
|
||
<h3 id="S_MergeDivePlan">14.8. Enregistrer une plongée avec sa planification</h3>
|
||
<div class="paragraph"><p>In the section dealing with <a href="#S_MultipleDiveComputers">dives using more than one dive computer</a> we discussed the way in which multiple profiles for a
|
||
single dive can be viewed using the left-arrow and right-arrow keyboard
|
||
keys. A similar method can be used for saving a dive plan with the profile
|
||
of the actual dive, once this has been uploaded into <em>Subsurface</em>. In order
|
||
to do this:</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Do the dive planning and save the final plan in the <em>Dive List</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Après la plongée, télécharger les données depuis l’ordinateur de plongée.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Change the date and time of the <em>dive plan</em> to coincide with that of the
|
||
real-life dive from the <em>dive computer</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
In the <em>Dive List</em>, highlight the dive plan as well as the data for the real
|
||
dive and merge the two dives, making use of the Dive List Context Menu
|
||
(available by right-clicking a dive).
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>The text version of the dive plan is appended to the Notes in the <em>Notes
|
||
Tab</em>. With this merged dive highlighted in the <em>Dive List</em>, switch between
|
||
the planned profile and the real-life profile using the
|
||
right-arrow/left-arrow keyboard keys.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_lancer_em_subsurface_em_depuis_la_ligne_de_commande">15. Lancer <em>Subsurface</em> depuis la ligne de commande</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> can be launched from the command-line to set some specialised
|
||
settings or as part of an script-based automated process for manipulating a
|
||
dive log. The format for launching <em>Subsurface</em> from the command-line is:</p></div>
|
||
<div class="literalblock">
|
||
<div class="content">
|
||
<pre><code>subsurface [options] [logfile ...] [--import logfile ...]</code></pre>
|
||
</div></div>
|
||
<div class="paragraph"><p>Ces options incluent:</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>Command-line option</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">--help</p></td>
|
||
<td align="left" valign="top"><p class="table">Print a summary of the command-line options</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">-h</p></td>
|
||
<td align="left" valign="top"><p class="table">Print a summary of the command-line options</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--import logfile</p></td>
|
||
<td align="left" valign="top"><p class="table">A file name before this option is treated as an existing dive log, everything after is imported into the existing dive log</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--verbose</p></td>
|
||
<td align="left" valign="top"><p class="table">Print debug information while running <em>Subsurface</em></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">-v</p></td>
|
||
<td align="left" valign="top"><p class="table">Print debug information while running <em>Subsurface</em></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">-v -v</p></td>
|
||
<td align="left" valign="top"><p class="table">Print even more debug information while running <em>Subsurface</em></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--version</p></td>
|
||
<td align="left" valign="top"><p class="table">Prints the current version of <em>Subsurface</em></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--survey</p></td>
|
||
<td align="left" valign="top"><p class="table">Opens the <a href="#S_UserSurvey">user survey</a> immediately after starting <em>Subsurface</em></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--user=<username></p></td>
|
||
<td align="left" valign="top"><p class="table">Choose the <a href="#S_user_space">configuration space</a> of user <username></p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">--cloud-timeout=<duration></p></td>
|
||
<td align="left" valign="top"><p class="table">Set the timeout for cloud connection (0 < duration < 60). This enables longer timeouts for slow Internet connections</p></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_description_des_éléments_du_menu_principal_de_subsurface">16. Description des éléments du menu principal de Subsurface</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p>Cette section décrit les fonctions et les opérations des éléments du menu
|
||
principal de Subsurface. Plusieurs éléments ci-dessous sont des liens vers
|
||
des sections de ce manuel traitant des opérations relatives.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_fichier">16.1. Fichier</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_NewLogbook"><em>Nouveau carnet de plongée</em></a> - Fermer le carnet de plongée
|
||
actuellement ouvert et supprime toutes les informations de plongées.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Ouvrir un carnet de plongée</em> - Ouvre une fenêtre pour sélectionner le
|
||
carnet de plongée à ouvrir.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Sauvegarder</em> - Enregistrer le carnet de plongée actuellement ouvert.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Enregsitrer sous</em> - Enregistrer le carnet actuel sous un nom différent.
|
||
</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 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>Take cloud storage online</em> -
|
||
<strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong><strong><strong></strong></strong>
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Fermer</em> - Fermer le carnet de plongée actuellement ouvert.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ExportLog"><em>Exporter</em></a> - Exporter le carnet de plongée actuellement
|
||
ouvert (ou les plongées sélectionnées dans le carnet) vers un des nombreux
|
||
formats.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_PrintDivelog"><em>Imprimer</em></a> - Imprimer le carnet de plongée actuellement
|
||
ouvert.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Preferences"><em>Préférences</em></a> - Définir les préférences de <em>Subsurface</em>.
|
||
</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>Configurer l’ordinateur de plongée</em></a> - Modifier la
|
||
configuration d’un ordinateur de plongée.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Quitter</em> - Quitter <em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_édition">16.2. Édition</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
The Edit option allows one to undo or redo an action, e.g. deleting dives.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importer">16.3. Importer</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ImportDiveComputer"><em>Importer depuis un l’ordinateur de plongée</em></a> -
|
||
Importer des informations de plongées à partir de l’ordinateur de plongée.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#Unified_import"><em>Importer des fichiers de log</em></a> - Importer des
|
||
informations de plongées à partir d’un fichier d’un format compatible avec
|
||
<em>Subsurface</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Companion"><em>Importer les données GPS depis le service web Subsurface</em></a> -
|
||
Charge les coordonnées GPS à partir de l’application mobile <em>Subsurface</em>
|
||
(téléphones et tablettes).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ImportingDivelogsDe"><em>Importer depuis Divelogs.de</em></a> - Importer des
|
||
informations de plongées à partir de <em>www.Divelogs.de</em>.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_journal_log">16.4. Journal (log)</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_EnterData"><em>Ajouter une plongée</em></a> - Ajouter manuellement une nouvelle
|
||
plongée au panneau de la <strong>liste des plongées</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Edit dive</em> - Edit a dive where the profile was entered by hand and not from
|
||
a dive computer.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_DivePlanner"><em>Planifier une plongée</em></a> - Planifier des plongées.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Replan"><em>Modifier la plongée dans le planificateur</em></a> - Modifier une
|
||
plongée planifiée qui a été enregistrée dans la <strong>liste des plongées</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_CopyComponents"><em>Copier les composants de la plongée</em></a> - Copier les
|
||
informations de plusieurs champs d’un journal de plongée vers le
|
||
presse-papier.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Coller les composants de la plongée</em> - Colle, dans les plongées
|
||
sélectionnées dans la <strong>liste des plongées</strong>, les informations copiées au
|
||
préalable avec l’option <em>Copier les composants de la plongée</em>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Renumber"><em>Renuméroter</em></a> - Renuméroter les plongées sélectionnées dans
|
||
le panneau de la <strong>liste des plongées</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Group"><em>Grouper automatiquement</em></a> - Grouper les plongées du panneau de
|
||
<strong>liste des plongées</strong> dans des voyages de plongées.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_DeviceNames"><em>Editer les noms des ordinateurs de plongée</em></a> - Modifier
|
||
les noms des ordinateurs de plongée pour coordonner vos journaux (logs).
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Filter"><em>Filtrer la liste des plongées</em></a> - Sélectionner seulement
|
||
certaines plongées, à partir de tags ou de critères de plongées.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_vue">16.5. Vue</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Tout</em></a> - Affiche les quatre panneaux principaux de
|
||
<em>Subsurface</em> simultanément.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Liste des plongées</em></a> - Affiche uniquement le panneau de la
|
||
<strong>liste des plongées</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Profil</em></a> - Affiche uniquement le panneau du <strong>profil de la
|
||
plongée</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Info</em></a> - Affiche uniquement le panneau des <strong>notes</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_ViewPanels"><em>Globe</em></a> - Affiche uniquement le panneau de la <strong>carte
|
||
mondiale</strong>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Statistiques annuelles</em> - Affiche par année le résumé des statistiques des
|
||
plongées effectuées.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Prev DC</em> - Switch to data from previous dive computer, if a single dive was
|
||
logged from more than one. See the sections on
|
||
<a href="#S_MultipleDiveComputers">using multiple dive computers for the same dive</a>
|
||
and <a href="#S_MergeDivePlan">Saving an uploaded dive with its dive plan</a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Ordinateur suivant</em> - Passer à l’ordinateur de plongée suivant.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Plein écran</em> - Passer en mode plein écran.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_share_on">16.6. Share on</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<a href="#S_Facebook"><em>Facebook</em></a> - Partager la plongée sélectionnée sur votre
|
||
Facebook.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_aide">16.7. Aide</h3>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
<em>À propos de Subsurface</em> - Affiche un panneau avec le numéro de version de
|
||
<em>Subsurface</em> ainsi que les informations de licence.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Vérifier les mises à jour</em> - Vérifier si une nouvelle version de
|
||
Subsurface est disponible sur le <a href="https://subsurface-divelog.org/">site web de
|
||
<em>Subsurface</em> </a>.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<a href="#S_UserSurvey"><em>Sondge utilisateur</em></a> - Aider à rendre <em>Subsurface</em> encore
|
||
meilleur en répondant à notre sondage utilisateur ou en répondant à un autre
|
||
sondage, si vos habitudes de plongées ont changées.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Manuel utilisateur</em> - Ouvre une fenêtre affichant ce manuel utilisateur.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_annexe_a_informations_spécifiques_au_système_d_8217_exploitation_utilisé_pour_importer_les_informations_de_plongées_depuis_un_ordinateur_de_plongée">17. ANNEXE A : informations spécifiques au système d’exploitation utilisé pour importer les informations de plongées depuis un ordinateur de plongée.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="_assurez_vous_que_les_pilotes_drivers_nécessaires_sont_installés">17.1. Assurez-vous que les pilotes (drivers) nécessaires sont installés</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/drivers.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Le système d’exploitation de l’ordinateur nécessite les bons pilotes pour
|
||
communiquer avec l’ordinateur de plongée de la façon utilisée par
|
||
l’ordinateur de plongée (Bluetooth, USB, infra-rouge).</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Sous Linux, les utilisateurs doivent avoir le bon module noyau de chargé. La
|
||
plupart des distributions Linux le font automatiquement, de telle sorte que
|
||
l’utilisateur n’ait rien à faire de particulier. Cependant, certains
|
||
protocoles de communication nécessitent des pilotes additionnels, plus
|
||
particulièrement pour certaines technologies telles que l’infra-rouge.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Sous Windows, le bon pilote devrait être téléchargé automatiquement la
|
||
première fois que l’utilisateur branche son ordinateur de plongée sur le
|
||
port USB de son ordinateur de bureau.
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Sous Mac, les utilisateurs peuvent parfois avoir besoin d’installer
|
||
manuellement le bon pilote. Par exemple, pour le Mares Puck ou n’importe
|
||
quel autre ordinateur de plongée utilisant une interface USB-série basé sur
|
||
le composant Silicon Labs CP2101 ou similaire, le bon pilote est disponible
|
||
sous <em>Mac_OSX_VCP_Driver.zip</em> sur le
|
||
<a href="https://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">dépôt
|
||
de documents et logiciels Silicon Labs</a>.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_HowFindDeviceName">17.2. Comment trouver le nom du périphérique branché sur USB et paramétrer les permissions en écriture</h3>
|
||
<div class="admonitionblock">
|
||
<table><tr>
|
||
<td class="icon">
|
||
<img src="images/icons/usb.jpg" alt="Note" />
|
||
</td>
|
||
<td class="content">Lors de la connexion d’un ordinateur de plongée en utilisant l’USB,
|
||
<em>Subsurface</em> proposera généralement soit une liste déroulante avec le bon
|
||
nom (ou le point de montage pour un Uemis Zurich) ou la liste sera
|
||
désactivée si aucun nom de périphérique n’est nécessaire. Dans les rares cas
|
||
où cela ne fonctionnerait pas, voici quelques méthodes pour trouver le nom
|
||
de votre périphérique ;</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><div class="title">Sur Windows :</div><p>Essayez simplement COM1, COM2, etc. La liste déroulante devrait contenir
|
||
tous les périphériques COM connectés.</p></div>
|
||
<div class="paragraph"><div class="title">Sur MacOS :</div><p>La liste déroulante devrait contenir tous les ordinateurs de plongée
|
||
connectés.</p></div>
|
||
<div class="paragraph"><div class="title">Sur Linux :</div><p>Il existe un moyen sûr de trouver le port :</p></div>
|
||
<div class="ulist"><ul>
|
||
<li>
|
||
<p>
|
||
Déconnecter le cable USB de l’ordinateur de plongée
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Ouvrir un terminal
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Connecter le cable USB de l’ordinateur de plongée
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="paragraph"><p>Un message similaire à celui-ci devrait apparaitre :</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>La troisième ligne en partant du bas montre que l’adaptateur FTDI USB est
|
||
détecté et connecté sur <code>ttyUSB3</code>. Cette information peut à présent être
|
||
utilisée pour les paramètres d’importation en tant que <code>/dev/ttyUSB3</code> pour
|
||
que Subsurface utilise le bon port USB.</p></div>
|
||
<div class="paragraph"><p>S’assurer que l’utilisateur possède les droits d'écriture sur le port série
|
||
USB :</p></div>
|
||
<div class="paragraph"><p>Sur les systèmes similaires à Unix, les ports USB ne peuvent être accédés
|
||
que par des utilisateurs membres d’un groupe spécial qui peut être <code>dialout</code>
|
||
ou <code>uucp</code>. Cela peut être vérifié en listant les permissions associées au
|
||
périphérique, par exemple via <code>ls - l /dev/ttyUSB0</code>. Notez que le numéro
|
||
dans le nom de fichier dépend du nombre de périphériques USB que vous avez
|
||
branchés et peut être ajusté au besoin.Si vous n'êtes pas root, vous n'êtes
|
||
peut-être pas membre de ce groupe et ne pouvez donc pas utiliser le port
|
||
USB. Admettons que votre nom d’utilisateur soit <em>johnB</em>.</p></div>
|
||
<div class="paragraph"><p>En tant que root, tapez : usermod -a -G dialout johnB+ (utilisateurs
|
||
d’Ubuntu : <code>sudo usermod -a -G dialout johnB</code>) Cela ajoute johnB au groupe
|
||
<code>dialout</code>.
|
||
Tapez : <code>id johnB</code> Cela liste tous les groupes auquel johnB appartient et
|
||
vérifiez que
|
||
l’appartenance au groupe est bien effectif. Le groupe <code>dialout</code> devrait
|
||
être listé
|
||
parmi les différents IDs.
|
||
Sous certaines circonstances, les modifications ne prennent effet qu’après une déconnexion
|
||
puis reconnexion sur l’ordinateur (sous Ubuntu, par exemple).</p></div>
|
||
<div class="paragraph"><p>Avec le bon nom de périphérique (par exemple <code>dev/ttyUSB3</code>) et avec un accès
|
||
en écriture au port USB, l’ordinateur de plongée devrait se connecter et
|
||
vous devriez pouvoir importer vos plongées.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_HowFindBluetoothDeviceName">17.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, Petrel and Nerd there is a
|
||
different procedure to get the device’s 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, be sure 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/Nerd, 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>Jumeler l’ordinateur utilisant <em>Subsurface</em> avec l’ordinateur de plongée.</strong>
|
||
</p>
|
||
</li>
|
||
</ul></div>
|
||
<div class="sect3">
|
||
<h4 id="_sur_windows_2">17.3.1. Sur 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="_sur_macos">17.3.2. Sur 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 complete, 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="_sur_linux">17.3.3. Sur Linux</h4>
|
||
<div class="paragraph"><p>Be sure 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
|
||
straightforward. 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>
|
||
Activez le contrôleur Bluetooth et jumelez votre ordinateur de plongée
|
||
</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>,
|
||
<em>Petrel 2</em> and <em>Nerd</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 doesn’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 <em><code>UP</code></em>, <em><code>RUNNING</code></em> AND <em><code>AUTH</code></em>.</p></div>
|
||
<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to turn 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, you 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 the dive computer is paired, 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 you omit 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 1</em>: channel 1
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Shearwater Petrel 2</em>: channel 5
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
<em>Shearwater Nerd</em>: channel 5
|
||
</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">18. APPENDIX B: Dive Computer specific information for importing dive data.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_ImportUemis">18.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
|
||
you don’t 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 you
|
||
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 you download
|
||
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
|
||
straightforward. 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. You 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">18.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 recognize 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, with drivers located on the download page for the
|
||
ScubaPro SmartTrak software.</p></div>
|
||
<div class="paragraph"><p>Pour les ordinateurs Apple Mac, la connexion IrDA via l’interface MCS7780
|
||
n’est plus disponible depuis OSX 10.6 ou supérieur.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="S_ImportingDR5">18.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>Profile 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">18.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>Profile 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_nerd_using_bluetooth">18.5. Importing from Shearwater Predator/Petrel/Nerd 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">18.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 utilizes the
|
||
IrDA infra-red protocol. Only data for one dive can be downloaded at a time,
|
||
in 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 get dive log
|
||
information.</p></div>
|
||
</div>
|
||
<div class="sect2">
|
||
<h3 id="_importing_from_apd_inspiration_evolution_ccr">18.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 (labeled
|
||
<em>Filter:</em>), select "APD log viewer".
|
||
On the list of file names select the <em>.apd</em> file created. An import
|
||
dialogue opens showing the default settings for the data in the
|
||
<em>.apd</em> file. If 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 lets you 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 provided 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">19. 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">19.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 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 you need to locate the DM4/DM5 database where the
|
||
dives are stored. You 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>
|
||
Ouvrir l’explorateur Windows
|
||
</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">19.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 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">19.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 Organizer 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 Organizer-registered divers on the particular
|
||
computer and all Mares dive computers used. The safest way to get a copy of
|
||
the dive database is to export the information to another compatible format
|
||
which can then be imported into <em>Subsurface</em>.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Within Dive Organizer, select <em>Database → Backup</em> from the main menu and
|
||
back up the database to the desk top. This creates a zipped file
|
||
DiveOrganizerxxxxx.dbf.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a
|
||
file <em>DiveOrganizer.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">19.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 would lack, for example, gas switches and information of
|
||
what units are used. With database import, all this information is included
|
||
and readily available.</td>
|
||
</tr></table>
|
||
</div>
|
||
<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface:</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 Subsurface’s own format. Last step to
|
||
do is save the log file in Subsurface.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div class="sect1">
|
||
<h2 id="_annexe_d_exporter_un_tableur_vers_le_format_csv">20. ANNEXE D : Exporter un tableur vers le format CSV</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph" id="S_Appendix_D"><p>De nombreux plongeurs conservent un carnet de plongée sous forme de fichier
|
||
numérique, souvent un tableur avec différents champs et informations. Ces
|
||
données peuvent facilement être importées dans <em>Subsurface</em> après que le
|
||
tableur a été converti en fichier CSV. Cette section explique la procedure
|
||
pour convertir un carnet de plongée enregistrée sous forme de tableur vers
|
||
un fichier CSV qui pourra ensuite être importé dans <em>Subsurface</em>. Créer un
|
||
fichier CSV est simple malgré que la procédure soit différente selon le
|
||
tableur utilisé.</p></div>
|
||
<div class="paragraph"><p>Organiser les données de plongées dans le tableur pour que la première ligne
|
||
contienne le nom (ou le titre) de chaque colonne et que les informations de
|
||
chaque plongée soient contenues sur une seule ligne. <em>Subsurface</em> supporte
|
||
de nombreux éléments (Dive #, Date, Time, Duration, Location, GPS,
|
||
Max. Depth, Mean Depth, Buddy, Notes, Weight et Tags). Organiser les
|
||
données de plongées selon quelques règles simples :</p></div>
|
||
<div class="olist arabic"><ol class="arabic">
|
||
<li>
|
||
<p>
|
||
Date : utiliser un des formats suivants : aaaa-mm-jj, jj.mm.aaaa, mm/jj/aaaa
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Durée : le format est minutes:secondes.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Système d’unité : un seul système d’unité doit être utilisé (pas de mélange
|
||
entre les unités impériales et métriques)
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Étiquettes et équipiers : les valeurs doivent être séparées par des
|
||
virgules.
|
||
</p>
|
||
</li>
|
||
<li>
|
||
<p>
|
||
Position GPS : utilisez les degrés décimaux, par exemple : 30.22496
|
||
30.821798
|
||
</p>
|
||
</li>
|
||
</ol></div>
|
||
<div class="sect2">
|
||
<h3 id="_em_libreoffice_calc_em_et_em_openoffice_calc_em">20.1. <em>LibreOffice Calc</em> et <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>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">20.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 uses the new character as a separator. You 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, 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 the following: ** In Windows 7, click the <em>Formats</em> tab, and then click
|
||
<em>Customize this format</em>.
|
||
</p>
|
||
</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>. Be sure 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. You can double check the .CSV file by opening it with a
|
||
text editor, 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">21. ANNEXE E : Créer un modèle d’impression personnalisé</h2>
|
||
<div class="sectionbody">
|
||
<div class="paragraph"><p><em>Subsurface</em> has a way to create or modify templates for printing dive logs
|
||
to produce customized printouts of them. 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 lets you <em>Edit</em>, <em>Delete</em>,
|
||
<em>Import</em> and <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 has 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 color
|
||
template used for printing the dive log. The style attributes are
|
||
editable. Choose one of the four color palettes used for color printing.</p></div>
|
||
<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colors used for
|
||
printing the dive log. The colors are highly customizable: the <em>Edit</em>
|
||
buttons in the <em>Colors</em> tab allows choosing arbitrary colors 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 can 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 information printed needs to be specified and
|
||
formatted in the template by replacing the section marked with: "<!--
|
||
Template must be filled -→". Writing HTML code with Grantlee instructions
|
||
allows unlimited freedom in determining what is printed and 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>You 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 the
|
||
template will be correctly handled and rendered.</p></div>
|
||
<div class="sect2">
|
||
<h3 id="_main_dive_loop">21.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> back
|
||
end. It is possible to iterate over the list as follows:
|
||
.template.html</p></div>
|
||
<div class="literalblock">
|
||
<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">21.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>) date 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 for the dive</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 for the dive</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 the 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 the 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 which 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 for the dive</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>) list of dive tags for the dive</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>) list of gases used in the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">suit</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) the suit used for the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">cylinders</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used cylinders</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">cylinder0-7</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific cylinder</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">weights</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used weight systems</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">weight0-5</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific weight system</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">maxcns</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) maxCNS value for the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">otu</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) OTU value for the dive</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">sumWeight</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) the summed weight of all used weight systems</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">startPressure</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) the start pressure</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">endPressure</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) the end pressure</p></td>
|
||
</tr>
|
||
<tr>
|
||
<td align="left" valign="top"><p class="table">firstGas</p></td>
|
||
<td align="left" valign="top"><p class="table">(<strong>string</strong>) first used gas</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">21.3. Defined CSS selectors</h3>
|
||
<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses special
|
||
<em>CSS</em> selectors to search 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 dive 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 dive with this class from being 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">21.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 many 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="_annexe_f_faqs">22. ANNEXE F: FAQs.</h2>
|
||
<div class="sectionbody">
|
||
<div class="sect2">
|
||
<h3 id="S_APPENDIX_F">22.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">22.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">22.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? <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 a limited amount of memory to do so. The exact
|
||
amount of dive profiles that can be stored on the device depends 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 good chance that Subsurface can import
|
||
these. However, if the logs are only on your dive computer, they cannot be
|
||
salvaged after being overwritten by new dives.</p></div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div id="footnotes"><hr /></div>
|
||
<div id="footer">
|
||
<div id="footer-text">
|
||
Last updated
|
||
2017-11-28 08:54:18 CET
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html>
|