Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paired-end reads #17

Open
simonepignotti opened this issue May 8, 2018 · 0 comments
Open

Paired-end reads #17

simonepignotti opened this issue May 8, 2018 · 0 comments

Comments

@simonepignotti
Copy link
Member

simonepignotti commented May 8, 2018

Add support for paired-end reads to the query command.

Updated specification

Usage:   prophex query [options] <index_prefix> <in1.fq> [in2.fq]
...

Behavior

Each pair should be concatenated and separated by a N character.
The k-mers overlapping that position should have a specific marker in the output, e.g. C (concatenation).

Example

k=4

in1.fq:

@read1/1
ACGT
+
!!!!
...

in2.fq:

@read1/2
TGCA
+
!!!!
...

Extended Kraken format

output:

U    read1    0    8    ref1:1 C:4 ref1:1

Bitmask output format (#14 )

The hit and coverage masks should not contain the concatenation k-mers, but the two reads should be separated by a pipe (|).

read1	ref1	8	2	8	1|1

Alternative solutions

If there is a cleaner way to obtain the same result without concatenating reads with N, we should consider it (e.g. query the two parts indipendently).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant