-
Notifications
You must be signed in to change notification settings - Fork 52
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added new feature to filter seq tool so that it handles paired end input. NOTE that this has required a change in the interface. Updated documentation Tweaked the makefiles to remove some redundancy in the compiler flags.
- Loading branch information
Showing
17 changed files
with
378 additions
and
301 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
|
||
.. _faq: | ||
|
||
Frequently Asked Questions | ||
========================== | ||
|
||
Can KAT handle gzipped sequence files? | ||
-------------------------------------- | ||
|
||
Yes, but only via named pipes. For example, say we wanted to run ``kat hist`` using | ||
gzipped paired end dataset, we can use a named pipe to do this as follows:: | ||
|
||
mkfifo pe_dataset.fq && gunzip -c pe_dataset_?.fq.gz > pe_dataset.fq & | ||
kat hist -o pe_dataset.hist pe_dataset.fq | ||
|
||
Where ``pe_dataset_?.fq.gz``, represents ``pe_dataset_1.fq.gz`` and ``pe_dataset_2.fq.gz``. | ||
|
||
For those unfamiliar with named pipes, the first line will create an empty file | ||
in your working directory called pe_dataset.fq and then specifies that anything | ||
consuming from the named pipe will take data that has been gunzipped first. To be | ||
clear this means you do not have to decompress the gzipped files to disk, this happens | ||
on the fly as consumed by KAT. | ||
|
||
Thanks to John Davey for suggesting this. | ||
|
||
|
||
Why is jellyfish bundled with KAT? | ||
---------------------------------- | ||
|
||
We require a stable interface to the k-mer hash arrays produced by jellyfish hence, | ||
we are reliant on a particular version of jellyfish to guarantee that KAT works | ||
correctly. Instead of potentially requiring the user to install multiple jellyfish instances | ||
on their machine, we bundle our own version, with all jellyfish binaries prefixed | ||
with `kat_` in order to avoid any naming clashes with official jellyfish releases. | ||
|
||
|
||
I downloaded a release from github but it doesn't contain the configure script. What gives? | ||
-------------------------------------------------------------------------------------------- | ||
|
||
Github offers a feature which allows you to download source code bundles for all | ||
releases. However, these bundles do not contain the distributable form of KAT, i.e. | ||
they are not produced by calling ``make dist``. Although they come from the same | ||
place you can distinguish between the github bundles and the proper distributable form | ||
of KAT because it will have the name: ``kat-x.x.x.tar.gz``. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,6 +25,7 @@ The K-mer counting itself, a critical element for all KAT tools, is accomplished | |
using | ||
kmer | ||
walkthrough | ||
faq | ||
|
||
.. _system: | ||
|
||
|
@@ -46,7 +47,9 @@ Citing | |
The KAT paper is currently in submission. In the meantime, if you use our software | ||
and wish to cite us please use our bioRxiv preprint: | ||
|
||
`Daniel Mapleson et al. 2016. KAT: A K-mer Analysis Toolkit to quality control NGS datasets and genome assemblies. bioRxiv doi: 10.1101/064733 <http://biorxiv.org/content/early/2016/07/19/064733>`_ | ||
Daniel Mapleson, Gonzalo Garcia Accinelli, George Kettleborough, Jonathan Wright, and Bernardo J. Clavijo. | ||
**KAT: A K-mer Analysis Toolkit to quality control NGS datasets and genome assemblies.** | ||
Bioinformatics, 2016. `doi: 10.1093/bioinformatics/btw663 <http://bioinformatics.oxfordjournals.org/content/early/2016/10/20/bioinformatics.btw663.abstract>`_ | ||
|
||
|
||
|
||
|
@@ -55,8 +58,11 @@ and wish to cite us please use our bioRxiv preprint: | |
Issues | ||
====== | ||
|
||
Should you discover any issues with spectre, or wish to request a new feature please raise a `ticket here <https://github.com/TGAC/KAT/issues>`_. | ||
Alternatively, contact Daniel Mapleson at: [email protected]; or Bernardo Clavijo at: [email protected] | ||
Should you discover any issues with KAT, or wish to request a new feature please raise a `ticket here <https://github.com/TGAC/KAT/issues>`_. | ||
Alternatively, contact Daniel Mapleson at: [email protected]; or Bernardo Clavijo at: [email protected]. | ||
However, please consult the `Frequently Asked Questions <faq>`_ page first in case your | ||
question is already answered there. | ||
|
||
|
||
|
||
.. _availability: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.