bump version to 0.6.0

Author: hasindu2008

README.md

@@ -18,7 +18,7 @@ SLOW5 specification: https://hasindu2008.github.io/slow5specs<br/>
 
 If you are a Linux user on x86_64 architecture and want to quickly try slow5tools out, download the compiled binaries from the [latest release](https://github.com/hasindu2008/slow5tools/releases). For example:
 ```sh
-VERSION=v0.5.1
+VERSION=v0.6.0
 wget "https://github.com/hasindu2008/slow5tools/releases/download/$VERSION/slow5tools-$VERSION-x86_64-linux-binaries.tar.gz" && tar xvf slow5tools-$VERSION-x86_64-linux-binaries.tar.gz && cd slow5tools-$VERSION/
 ./slow5tools
 ```
@@ -36,7 +36,7 @@ Quick example for Ubuntu :
 
 ```sh
 sudo apt-get install libhdf5-dev zlib1g-dev   #install HDF5 and zlib development libraries
-VERSION=v0.5.1
+VERSION=v0.6.0
 wget "https://github.com/hasindu2008/slow5tools/releases/download/$VERSION/slow5tools-$VERSION-release.tar.gz" && tar xvf slow5tools-$VERSION-release.tar.gz && cd slow5tools-$VERSION/
 ./configure
 make

docs/faq.md

@@ -36,10 +36,10 @@ The direct link to the complete PromethION dataset (~9M reads) is [here](https:/
 
 If your SLOW5 to FAST5 conversion takes ages, it is likely that you called `slow5tools s2f` on a single SLOW5 file which will only use one processor. For parallelising the conversion, first split the SLOW5 file into multiple files using `slow5tools split -r` (you may have to use `slow5tools split -g` first if you BLOW5 file has multiple read groups). Then call `slow5tools s2f` with `-p <num_processes>` so that multiple CPU processors can be used for parallel conversion.
 
-**Q5:** When I convert from FAST5 to BLOW5 and then reconvert to FAST5, why are the new FAST5 files are different in size to original FAST5 files?
+**Q6:** When I convert from FAST5 to BLOW5 and then reconvert to FAST5, why are the new FAST5 files are different in size to original FAST5 files?
 
 This is normal behaviour and be assured that difference in sizes does not mean that data has been lost. Please see the issues [#70](https://github.com/hasindu2008/slow5tools/issues/70), [#76](https://github.com/hasindu2008/slow5tools/issues/76) and [#58](https://github.com/hasindu2008/slow5tools/issues/58).
 
-**Q6** Can I upload my BLOW5 files to public archives like SRA?
+**Q7** Can I upload my BLOW5 files to public archives like SRA?
 
 Yes you can. Follow the same method you use to upload unbasecalled FAST5 files. Simply create a tar ball containing your BLOW5 file/files (optionally .blow5.idx files as well), select ONT_NATIVE under the SRA submission format and upload as you would usually do. When the loading fails (happens for unbasecalled FAST5 as well - and now ONT does not store basecalls on FAST5 anyway), email the SRA helpdesk and they will complete your submission.

docs/getting_started.md

@@ -13,7 +13,7 @@ SLOW5 specification: https://hasindu2008.github.io/slow5specs<br/>
 
 If you are a Linux user on x86_64 architecture and want to quickly try slow5tools out, download the compiled binaries from the [latest release](https://github.com/hasindu2008/slow5tools/releases). For example:
 ```sh
-VERSION=v0.5.1
+VERSION=v0.6.0
 wget "https://github.com/hasindu2008/slow5tools/releases/download/$VERSION/slow5tools-$VERSION-x86_64-linux-binaries.tar.gz" && tar xvf slow5tools-$VERSION-x86_64-linux-binaries.tar.gz && cd slow5tools-$VERSION/
 ./slow5tools
 ```
@@ -32,7 +32,7 @@ Quick example for Ubuntu:
 
 ```sh
 sudo apt-get install libhdf5-dev zlib1g-dev   #install HDF5 and zlib development libraries
-VERSION=v0.5.1
+VERSION=v0.6.0
 wget "https://github.com/hasindu2008/slow5tools/releases/download/$VERSION/slow5tools-$VERSION-release.tar.gz" && tar xvf slow5tools-$VERSION-release.tar.gz && cd slow5tools-$VERSION/
 ./configure
 make

slow5lib

@@ -1,7 +1,7 @@
 #ifndef CMD_H
 #define CMD_H
 
-#define SLOW5TOOLS_VERSION "0.5.1-dirty"
+#define SLOW5TOOLS_VERSION "0.6.0"
 
 #define DEFAULT_NUM_THREADS 8
 #define DEFAULT_NUM_PROCESSES 8