Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathcontributing.html
More file actions
Latest commit
377 lines (339 loc) · 23.2 KB
/
Copy pathcontributing.html
File metadata and controls
377 lines (339 loc) · 23.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
<!DOCTYPE html>
<htmlclass="writer-html5" lang="en" data-content_root="./">
<head>
<metacharset="utf-8" /><metaname="viewport" content="width=device-width, initial-scale=1" />
<metaname="viewport" content="width=device-width, initial-scale=1.0" />
<title>Contributing to POT — POT Python Optimal Transport 0.9.7 documentation</title>
<linkrel="stylesheet" type="text/css" href="_static/pygments.css?v=b86133f3" />
<linkrel="stylesheet" type="text/css" href="_static/css/theme.css?v=9edc463e" />
<linkrel="stylesheet" type="text/css" href="_static/sg_gallery.css?v=fd6457a4" />
<linkrel="stylesheet" type="text/css" href="_static/sg_gallery-binder.css?v=f4aeca0c" />
<linkrel="stylesheet" type="text/css" href="_static/sg_gallery-dataframe.css?v=2082cf3c" />
<linkrel="stylesheet" type="text/css" href="_static/sg_gallery-rendered-html.css?v=1277b6f3" />
<scriptsrc="_static/jquery.js?v=5d32c60e"></script>
<scriptsrc="_static/_sphinx_javascript_frameworks_compat.js?v=2cd50e6c"></script>
<scriptsrc="_static/documentation_options.js?v=f2328ca0"></script>
<scriptsrc="_static/doctools.js?v=fd6eb6e6"></script>
<scriptsrc="_static/sphinx_highlight.js?v=6ffebe34"></script>
<scriptsrc="_static/sg-tags.js?v=d80f6fa4"></script>
<scriptsrc="_static/js/theme.js"></script>
<linkrel="index" title="Index" href="genindex.html" />
<linkrel="search" title="Search" href="search.html" />
<linkrel="next" title="Code of conduct" href="code_of_conduct.html" />
<linkrel="prev" title="Contributors" href="contributors.html" />
</head>
<bodyclass="wy-body-for-nav">
<divclass="wy-grid-for-nav">
<navdata-toggle="wy-nav-shift" class="wy-nav-side">
<divclass="wy-side-scroll">
<divclass="wy-side-nav-search" >
<ahref="index.html" class="icon icon-home">
POT Python Optimal Transport
<imgsrc="_static/logo_dark.svg" class="logo" alt="Logo"/>
</a>
<divrole="search">
<formid="rtd-search-form" class="wy-form" action="search.html" method="get">
<inputtype="text" name="q" placeholder="Search docs" aria-label="Search docs" />
<inputtype="hidden" name="check_keywords" value="yes" />
<inputtype="hidden" name="area" value="default" />
</form>
</div>
</div><divclass="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
<ulclass="current">
<liclass="toctree-l1"><aclass="reference internal" href="index.html">POT: Python Optimal Transport</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="auto_examples/plot_quickstart_guide.html">Quickstart Guide</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="auto_examples/index.html">Examples gallery</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="user_guide.html">User guide</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="all.html">API and modules</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="releases.html">Releases</a></li>
<liclass="toctree-l1"><aclass="reference internal" href="contributors.html">Contributors</a></li>
<liclass="toctree-l1 current"><aclass="current reference internal" href="#">Contributing to POT</a><ul>
<liclass="toctree-l2"><aclass="reference internal" href="#how-to-contribute">How to contribute</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="#pull-request-checklist">Pull Request Checklist</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="#filing-bugs">Filing bugs</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="#new-contributor-tips">New contributor tips</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="#documentation">Documentation</a></li>
</ul>
</li>
<liclass="toctree-l1"><aclass="reference internal" href="code_of_conduct.html">Code of conduct</a></li>
</ul>
</div>
</div>
</nav>
<sectiondata-toggle="wy-nav-shift" class="wy-nav-content-wrap"><navclass="wy-nav-top" aria-label="Mobile navigation menu" >
<idata-toggle="wy-nav-top" class="fa fa-bars"></i>
<ahref="index.html">POT Python Optimal Transport</a>
</nav>
<divclass="wy-nav-content">
<divclass="rst-content">
<divrole="navigation" aria-label="Page navigation">
<ulclass="wy-breadcrumbs">
<li><ahref="index.html" class="icon icon-home" aria-label="Home"></a></li>
<liclass="breadcrumb-item active">Contributing to POT</li>
<liclass="wy-breadcrumbs-aside">
<ahref="_sources/contributing.rst.txt" rel="nofollow"> View page source</a>
</li>
</ul>
<hr/>
</div>
<divrole="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<divitemprop="articleBody">
<sectionid="contributing-to-pot">
<h1>Contributing to POT<aclass="headerlink" href="#contributing-to-pot" title="Link to this heading"></a></h1>
<p>First off, thank you for considering contributing to POT.</p>
<sectionid="how-to-contribute">
<h2>How to contribute<aclass="headerlink" href="#how-to-contribute" title="Link to this heading"></a></h2>
<p>The preferred workflow for contributing to POT is to fork the
<aclass="reference external" href="https://github.com/rflamary/POT">main repository</a> on
GitHub, clone, and develop on a branch. Steps:</p>
<olclass="arabic">
<li><p>Fork the <aclass="reference external" href="https://github.com/rflamary/POT">project repository</a>
by clicking on the ‘Fork’ button near the top right of the page. This creates
a copy of the code under your GitHub user account. For more details on
how to fork a repository see <aclass="reference external" href="https://help.github.com/articles/fork-a-repo/">this guide</a>.</p></li>
<li><p>Clone your fork of the POT repo from your GitHub account to your local disk:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>git<spanclass="w"></span>clone<spanclass="w"></span>git@github.com:YourLogin/POT.git
$<spanclass="w"></span><spanclass="nb">cd</span><spanclass="w"></span>POT
</pre></div>
</div>
</li>
<li><p>Install a recent version of Python. Using an isolated environment such as venv or conda allows you to install a specific version of POT.
For instance, for creating a conda environment with python 3.12 and for activating it:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>conda<spanclass="w"></span>create<spanclass="w"></span>-n<spanclass="w"></span>dev-pot-env<spanclass="w"></span><spanclass="nv">python</span><spanclass="o">=</span><spanclass="m">3</span>.12
$<spanclass="w"></span>conda<spanclass="w"></span>activate<spanclass="w"></span>dev-pot-env
</pre></div>
</div>
</li>
<li><p>Install pre-commit hooks to ensure that your code is properly formatted:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>pip<spanclass="w"></span>install<spanclass="w"></span>pre-commit
$<spanclass="w"></span>pre-commit<spanclass="w"></span>install
</pre></div>
</div>
<p>This will install the pre-commit hooks that will run on every commit. If the hooks fail, the commit will be aborted.</p>
</li>
<li><p>Create a <codeclass="docutils literal notranslate"><spanclass="pre">feature</span></code> branch to hold your development changes:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>git<spanclass="w"></span>checkout<spanclass="w"></span>-b<spanclass="w"></span>my-feature
</pre></div>
</div>
<p>Always use a <codeclass="docutils literal notranslate"><spanclass="pre">feature</span></code> branch. It’s good practice to never work on the <codeclass="docutils literal notranslate"><spanclass="pre">master</span></code> branch!</p>
</li>
<li><p>Install a compiler with OpenMP support for your platform (see details on the <aclass="reference external" href="https://scikit-learn.org/stable/developers/advanced_installation.html#platform-specific-instructions">scikit-learn contributing guide</a>).
For instance, with macOS, Apple clang does not support OpenMP. One can install the LLVM OpenMP library from homebrew:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>brew<spanclass="w"></span>install<spanclass="w"></span>libomp
</pre></div>
</div>
<p>and set environment variables:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span><spanclass="nb">export</span><spanclass="w"></span><spanclass="nv">CC</span><spanclass="o">=</span>/usr/local/opt/llvm/bin/clang
$<spanclass="w"></span><spanclass="nb">export</span><spanclass="w"></span><spanclass="nv">CXX</span><spanclass="o">=</span>/usr/local/opt/llvm/bin/clang++
</pre></div>
</div>
</li>
<li><p>Build the projet with pip:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>pip<spanclass="w"></span>install<spanclass="w"></span>-e<spanclass="w"></span>.
</pre></div>
</div>
<p>If you want to install all dependencies, you can use</p>
</li>
</ol>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span><spanclass="w"></span>pip<spanclass="w"></span>install<spanclass="w"></span>-e<spanclass="w"></span>.<spanclass="o">[</span>all<spanclass="o">]</span>
</pre></div>
</div>
<olclass="arabic" start="8">
<li><p>Develop the feature on your feature branch. Add changed files using <codeclass="docutils literal notranslate"><spanclass="pre">git</span><spanclass="pre">add</span></code> and then <codeclass="docutils literal notranslate"><spanclass="pre">git</span><spanclass="pre">commit</span></code> files:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>git<spanclass="w"></span>add<spanclass="w"></span>modified_files
$<spanclass="w"></span>git<spanclass="w"></span>commit
</pre></div>
</div>
<p>to record your changes in Git, then push the changes to your GitHub account with:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>git<spanclass="w"></span>push<spanclass="w"></span>-u<spanclass="w"></span>origin<spanclass="w"></span>my-feature
</pre></div>
</div>
</li>
<li><p>Follow <aclass="reference external" href="https://help.github.com/articles/creating-a-pull-request-from-a-fork">these instructions</a>
to create a pull request from your fork. This will send an email to the committers.</p></li>
</ol>
<p>(If any of the above seems like magic to you, please look up the
<aclass="reference external" href="https://git-scm.com/documentation">Git documentation</a> on the web, or ask a friend or another contributor for help.)</p>
</section>
<sectionid="pull-request-checklist">
<h2>Pull Request Checklist<aclass="headerlink" href="#pull-request-checklist" title="Link to this heading"></a></h2>
<p>We recommended that your contribution complies with the
following rules before you submit a pull request:</p>
<ulclass="simple">
<li><p>Follow the PEP8 Guidelines which should be handles automatically by pre-commit.</p></li>
<li><p>If your pull request addresses an issue, please use the pull request title
to describe the issue and mention the issue number in the pull request description. This will make sure a link back to the original issue is
created.</p></li>
<li><p>All public methods should have informative docstrings with sample
usage presented as doctests when appropriate.</p></li>
<li><p>Please prefix the title of your pull request with <codeclass="docutils literal notranslate"><spanclass="pre">[MRG]</span></code> (Ready for
Merge), if the contribution is complete and ready for a detailed review.
Two core developers will review your code and change the prefix of the pull
request to <codeclass="docutils literal notranslate"><spanclass="pre">[MRG</span><spanclass="pre">+</span><spanclass="pre">1]</span></code> and <codeclass="docutils literal notranslate"><spanclass="pre">[MRG</span><spanclass="pre">+</span><spanclass="pre">2]</span></code> on approval, making it eligible
for merging. An incomplete contribution – where you expect to do more work before
receiving a full review – should be prefixed <codeclass="docutils literal notranslate"><spanclass="pre">[WIP]</span></code> (to indicate a work
in progress) and changed to <codeclass="docutils literal notranslate"><spanclass="pre">[MRG]</span></code> when it matures. WIPs may be useful
to: indicate you are working on something to avoid duplicated work,
request broad review of functionality or API, or seek collaborators.
WIPs often benefit from the inclusion of a
<aclass="reference external" href="https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments">task list</a>
in the PR description.</p></li>
<li><p>When adding additional functionality, provide at least one
example script in the <codeclass="docutils literal notranslate"><spanclass="pre">examples/</span></code> folder. Have a look at other
examples for reference. Examples should demonstrate why the new
functionality is useful in practice and, if possible, compare it
to other methods available in POT.</p></li>
<li><p>Documentation and high-coverage tests are necessary for enhancements to be
accepted. Bug-fixes or new features should be provided with
<aclass="reference external" href="https://en.wikipedia.org/wiki/Non-regression_testing">non-regression tests</a>.
These tests verify the correct behavior of the fix or feature. In this
manner, further modifications on the code base are granted to be consistent
with the desired behavior.
For the Bug-fixes case, at the time of the PR, this tests should fail for
the code base in master and pass for the PR code.</p></li>
<li><p>At least one paragraph of narrative documentation with links to
references in the literature (with PDF links when possible) and
the example.</p></li>
</ul>
<p>You can also check for common programming errors with the following
tools:</p>
<ul>
<li><p>All lint checks pass. You can run the following command to check:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span>$<spanclass="w"></span>pre-commit<spanclass="w"></span>run<spanclass="w"></span>--all-files
</pre></div>
</div>
<p>This will run the pre-commit checks on all files in the repository.</p>
</li>
<li><p>All tests pass. You can run the following command to check:</p>
<divclass="highlight-bash notranslate"><divclass="highlight"><pre><span></span><spanclass="w"></span>$<spanclass="w"></span>pytest<spanclass="w"></span>--durations<spanclass="o">=</span><spanclass="m">20</span><spanclass="w"></span>-v<spanclass="w"></span>test/<spanclass="w"></span>--doctest-modules
</pre></div>
</div>
</li>
</ul>
<p>Bonus points for contributions that include a performance analysis with
a benchmark script and profiling output (please report on the mailing
list or on the GitHub issue).</p>
</section>
<sectionid="filing-bugs">
<h2>Filing bugs<aclass="headerlink" href="#filing-bugs" title="Link to this heading"></a></h2>
<p>We use Github issues to track all bugs and feature requests; feel free to
open an issue if you have found a bug or wish to see a feature implemented.</p>
<p>It is recommended to check that your issue complies with the
following rules before submitting:</p>
<ulclass="simple">
<li><p>Verify that your issue is not being currently addressed by other
<aclass="reference external" href="https://github.com/rflamary/POT/issues?q=">issues</a>
or <aclass="reference external" href="https://github.com/rflamary/POT/pulls?q=">pull requests</a>.</p></li>
<li><p>Please ensure all code snippets and error messages are formatted in
appropriate code blocks.
See <aclass="reference external" href="https://help.github.com/articles/creating-and-highlighting-code-blocks">Creating and highlighting code blocks</a>.</p></li>
<li><p>Please include your operating system type and version number, as well
as your Python, POT, numpy, and scipy versions. This information
can be found by running the following code snippet:</p></li>
</ul>
<divclass="highlight-python notranslate"><divclass="highlight"><pre><span></span><spanclass="kn">import</span><spanclass="w"></span><spanclass="nn">platform</span><spanclass="p">;</span><spanclass="nb">print</span><spanclass="p">(</span><spanclass="n">platform</span><spanclass="o">.</span><spanclass="n">platform</span><spanclass="p">())</span>
<spanclass="kn">import</span><spanclass="w"></span><spanclass="nn">sys</span><spanclass="p">;</span><spanclass="nb">print</span><spanclass="p">(</span><spanclass="s2">"Python"</span><spanclass="p">,</span><spanclass="n">sys</span><spanclass="o">.</span><spanclass="n">version</span><spanclass="p">)</span>
<spanclass="kn">import</span><spanclass="w"></span><spanclass="nn">numpy</span><spanclass="p">;</span><spanclass="nb">print</span><spanclass="p">(</span><spanclass="s2">"NumPy"</span><spanclass="p">,</span><spanclass="n">numpy</span><spanclass="o">.</span><spanclass="n">__version__</span><spanclass="p">)</span>
<spanclass="kn">import</span><spanclass="w"></span><spanclass="nn">scipy</span><spanclass="p">;</span><spanclass="nb">print</span><spanclass="p">(</span><spanclass="s2">"SciPy"</span><spanclass="p">,</span><spanclass="n">scipy</span><spanclass="o">.</span><spanclass="n">__version__</span><spanclass="p">)</span>
<spanclass="kn">import</span><spanclass="w"></span><spanclass="nn">ot</span><spanclass="p">;</span><spanclass="nb">print</span><spanclass="p">(</span><spanclass="s2">"POT"</span><spanclass="p">,</span><spanclass="n">ot</span><spanclass="o">.</span><spanclass="n">__version__</span><spanclass="p">)</span>
</pre></div>
</div>
<ulclass="simple">
<li><p>Please be specific about what estimators and/or functions are involved
and the shape of the data, as appropriate; please include a
<aclass="reference external" href="http://stackoverflow.com/help/mcve">reproducible</a> code snippet
or link to a <aclass="reference external" href="https://gist.github.com">gist</a>. If an exception is raised,
please provide the traceback.</p></li>
</ul>
</section>
<sectionid="new-contributor-tips">
<h2>New contributor tips<aclass="headerlink" href="#new-contributor-tips" title="Link to this heading"></a></h2>
<p>A great way to start contributing to POT is to pick an item
from the list of <aclass="reference external" href="https://github.com/rflamary/POT/issues?labels=Easy">Easy issues</a>
in the issue tracker. Resolving these issues allow you to start
contributing to the project without much prior knowledge. Your
assistance in this area will be greatly appreciated by the more
experienced developers as it helps free up their time to concentrate on
other issues.</p>
</section>
<sectionid="documentation">
<h2>Documentation<aclass="headerlink" href="#documentation" title="Link to this heading"></a></h2>
<p>We are glad to accept any sort of documentation: function docstrings,
reStructuredText documents (like this one), tutorials, etc.
reStructuredText documents live in the source code repository under the
doc/ directory.</p>
<p>You can edit the documentation using any text editor and then generate
the HTML output by typing <codeclass="docutils literal notranslate"><spanclass="pre">make</span><spanclass="pre">html</span></code> from the <codeclass="docutils literal notranslate"><spanclass="pre">docs/</span></code> directory.
Alternatively, <codeclass="docutils literal notranslate"><spanclass="pre">make</span></code> can be used to quickly generate the
documentation without the example gallery with <codeclass="docutils literal notranslate"><spanclass="pre">make</span><spanclass="pre">html-noplot</span></code>. The resulting HTML files will
be placed in <codeclass="docutils literal notranslate"><spanclass="pre">docs/build/html/</span></code> and are viewable in a web browser.</p>
<p>For building the documentation, you will need
<aclass="reference external" href="http://sphinx.pocoo.org/">sphinx</a>,
<aclass="reference external" href="http://matplotlib.org/">matplotlib</a>, and
<aclass="reference external" href="http://pillow.readthedocs.io/en/latest/">pillow</a>.</p>
<p>When you are writing documentation, it is important to keep a good
compromise between mathematical and algorithmic details, and give
intuition to the reader on what the algorithm does. It is best to always
start with a small paragraph with a hand-waving explanation of what the
method does to the data and a figure (coming from an example)
illustrating it.</p>
<p>This Contribution guide is strongly inspired by the one of the <aclass="reference external" href="https://github.com/scikit-learn/scikit-learn">scikit-learn</a> team.</p>
</section>
</section>
</div>
</div>
<footer><divclass="rst-footer-buttons" role="navigation" aria-label="Footer">
<ahref="contributors.html" class="btn btn-neutral float-left" title="Contributors" accesskey="p" rel="prev"><spanclass="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
<ahref="code_of_conduct.html" class="btn btn-neutral float-right" title="Code of conduct" accesskey="n" rel="next">Next <spanclass="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
</div>
<hr/>
<divrole="contentinfo">
<p>© Copyright 2016-2026, POT Contributors.</p>
</div>
Built with <ahref="https://www.sphinx-doc.org/">Sphinx</a> using a
<ahref="https://github.com/readthedocs/sphinx_rtd_theme">theme</a>
provided by <ahref="https://readthedocs.org">Read the Docs</a>.
</footer>
</div>
</div>
</section>
</div>
<divclass="rst-versions" data-toggle="rst-versions" role="note"
aria-label="versions">
<!-- add shift_up to the class for force viewing ,
data-toggle="rst-current-version" -->
<spanclass="rst-current-version" style="margin-bottom:1mm;">
<spanclass="fa fa-book"> Python Optimal Transport</span> 0.9.7
<hrstyle="margin-bottom:1.5mm;margin-top:5mm;">
<!-- versions
<span class="fa fa-caret-down"></span>-->
<spanclass="rst-current-version" style="display: inline-block;padding:
0px;color:#fcfcfcab;float:left;font-size: 100%;">
Versions:
<ahref="https://pythonot.github.io/"
style="padding: 3px;color:#fcfcfc;font-size: 100%;">Release</a>
<ahref="https://pythonot.github.io/master"
style="padding: 3px;color:#fcfcfc;font-size: 100%;">Development</a>
<ahref="https://github.com/PythonOT/POT"
style="padding: 3px;color:#fcfcfc;font-size: 100%;">Code</a>
</span>
</span>
<!--
<div class="rst-other-versions">
<div class="injected">
<dl>
<dt>Versions</dt>
<dd><a href="https://pythonot.github.io/">Release</a></dd>
<dd><a href="https://pythonot.github.io/master">Development</a></dd>
<dt><a href="https://github.com/PythonOT/POT">Code on Github</a></dt>
</dl>
<hr>
</div>
</div>-->
</div><script>
jQuery(function(){
SphinxRtdTheme.Navigation.enable(true);
});
</script>
</body>
</html>