Skip to content

Commit 93cfcb3

Browse files
committed
updated documentation with 0.58 changes
1 parent 94a9557 commit 93cfcb3

File tree

9 files changed

+50
-3
lines changed

9 files changed

+50
-3
lines changed

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -263,6 +263,13 @@ https://github.com/idptools/metapredict/issues
263263
### Recent changes
264264
This section is a log of recent changes with metapredict. My hope is that as I change things, this section can help you figure out why a change was made and if it will break any of your current work flows. The first major changes were made for the 0.56 release, so tracking will start there. Reasons are not provided for bug fixes for because the reason can assumed to be fixing the bug...
265265

266+
#### V0.58
267+
Change:
268+
Updated the network with a newly trained network (using the same dataset as the original) that is slightly more accurate.
269+
270+
Reason:
271+
I am always trying to find ways to make metapredict more accurate. When I manage to make the predictor better, I will update it.
272+
266273
#### V0.57
267274
Change:
268275
Bug fix that could result in prediction values to six decimal places in some scenarios

docs/_build/doctrees/changes.doctree

974 Bytes
Binary file not shown.
382 Bytes
Binary file not shown.

docs/_build/html/_sources/changes.rst.txt

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,14 @@ About
55
------
66
This section is a log of recent changes with metapredict. My hope is that as I change things, this section can help you figure out why a change was made and if it will break any of your current work flows. The first major changes were made for the 0.56 release, so tracking will start there.
77

8+
V0.58
9+
------
10+
11+
Change:
12+
Updated the network with a newly trained network (using the same dataset as the original) that is slightly more accurate.
13+
14+
Reason:
15+
I am always trying to find ways to make metapredict more accurate. When I manage to make the predictor better, I will update it.
816

917
V0.57
1018
-------

docs/_build/html/api.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,7 @@
9494
</li>
9595
<li class="toctree-l1"><a class="reference internal" href="usage/acknowledgements.html">Acknowledgements</a></li>
9696
<li class="toctree-l1"><a class="reference internal" href="usage/troubleshooting.html">Metapredict isn’t working!</a></li>
97+
<li class="toctree-l1"><a class="reference internal" href="changes.html">Recent changes</a></li>
9798
</ul>
9899

99100

docs/_build/html/changes.html

Lines changed: 24 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,8 @@
3434
<link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
3535
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
3636
<link rel="index" title="Index" href="genindex.html" />
37-
<link rel="search" title="Search" href="search.html" />
37+
<link rel="search" title="Search" href="search.html" />
38+
<link rel="prev" title="Metapredict isn’t working!" href="usage/troubleshooting.html" />
3839
</head>
3940

4041
<body class="wy-body-for-nav">
@@ -79,13 +80,20 @@
7980

8081

8182
<p class="caption"><span class="caption-text">Contents:</span></p>
82-
<ul>
83+
<ul class="current">
8384
<li class="toctree-l1"><a class="reference internal" href="getting_started.html">Getting Started with metapredict</a></li>
8485
<li class="toctree-l1"><a class="reference internal" href="usage/command-line.html">metapredict from the command-line</a></li>
8586
<li class="toctree-l1"><a class="reference internal" href="usage/using-in-python.html">metapredict in Python</a></li>
8687
<li class="toctree-l1"><a class="reference internal" href="api.html">Module Documentation</a></li>
8788
<li class="toctree-l1"><a class="reference internal" href="usage/acknowledgements.html">Acknowledgements</a></li>
8889
<li class="toctree-l1"><a class="reference internal" href="usage/troubleshooting.html">Metapredict isn’t working!</a></li>
90+
<li class="toctree-l1 current"><a class="current reference internal" href="#">Recent changes</a><ul>
91+
<li class="toctree-l2"><a class="reference internal" href="#about">About</a></li>
92+
<li class="toctree-l2"><a class="reference internal" href="#v0-58">V0.58</a></li>
93+
<li class="toctree-l2"><a class="reference internal" href="#v0-57">V0.57</a></li>
94+
<li class="toctree-l2"><a class="reference internal" href="#v0-56">V0.56</a></li>
95+
</ul>
96+
</li>
8997
</ul>
9098

9199

@@ -156,6 +164,13 @@ <h1>Recent changes<a class="headerlink" href="#recent-changes" title="Permalink
156164
<h2>About<a class="headerlink" href="#about" title="Permalink to this headline"></a></h2>
157165
<p>This section is a log of recent changes with metapredict. My hope is that as I change things, this section can help you figure out why a change was made and if it will break any of your current work flows. The first major changes were made for the 0.56 release, so tracking will start there.</p>
158166
</div>
167+
<div class="section" id="v0-58">
168+
<h2>V0.58<a class="headerlink" href="#v0-58" title="Permalink to this headline"></a></h2>
169+
<p>Change:
170+
Updated the network with a newly trained network (using the same dataset as the original) that is slightly more accurate.</p>
171+
<p>Reason:
172+
I am always trying to find ways to make metapredict more accurate. When I manage to make the predictor better, I will update it.</p>
173+
</div>
159174
<div class="section" id="v0-57">
160175
<h2>V0.57<a class="headerlink" href="#v0-57" title="Permalink to this headline"></a></h2>
161176
<p>Change:
@@ -198,6 +213,13 @@ <h2>V0.56<a class="headerlink" href="#v0-56" title="Permalink to this headline">
198213
</div>
199214
<footer>
200215

216+
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
217+
218+
219+
<a href="usage/troubleshooting.html" class="btn btn-neutral float-left" title="Metapredict isn’t working!" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left"></span> Previous</a>
220+
221+
</div>
222+
201223

202224
<hr/>
203225

docs/_build/html/index.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -194,6 +194,7 @@ <h1>Welcome to metapredict’s documentation!<a class="headerlink" href="#welcom
194194
</li>
195195
<li class="toctree-l1"><a class="reference internal" href="changes.html">Recent changes</a><ul>
196196
<li class="toctree-l2"><a class="reference internal" href="changes.html#about">About</a></li>
197+
<li class="toctree-l2"><a class="reference internal" href="changes.html#v0-58">V0.58</a></li>
197198
<li class="toctree-l2"><a class="reference internal" href="changes.html#v0-57">V0.57</a></li>
198199
<li class="toctree-l2"><a class="reference internal" href="changes.html#v0-56">V0.56</a></li>
199200
</ul>

docs/_build/html/searchindex.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

docs/changes.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,14 @@ About
55
------
66
This section is a log of recent changes with metapredict. My hope is that as I change things, this section can help you figure out why a change was made and if it will break any of your current work flows. The first major changes were made for the 0.56 release, so tracking will start there.
77

8+
V0.58
9+
------
10+
11+
Change:
12+
Updated the network with a newly trained network (using the same dataset as the original) that is slightly more accurate.
13+
14+
Reason:
15+
I am always trying to find ways to make metapredict more accurate. When I manage to make the predictor better, I will update it.
816

917
V0.57
1018
-------

0 commit comments

Comments
 (0)