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

Adding a new output format #14

Open
karel-brinda opened this issue May 1, 2018 · 4 comments
Open

Adding a new output format #14

karel-brinda opened this issue May 1, 2018 · 4 comments
Assignees

Comments

@karel-brinda
Copy link
Member

karel-brinda commented May 1, 2018

Description

Adding support for an additional output format with bitmasks.

CLI

-f INT     output format [0]
           0: Kraken
           1: bit-mask format

Bit-mask format spec

Tab delimited text file with the following columns

  1. read name
  2. ref k-mer set name
  3. read length
  4. number of k-mer matches
  5. coverage
  6. k-mer hit bit-mask

Example

Read ACCCAC, k=3

read1	ref1	6	3	6	1011
read1	ref2	6	1	3	1000
@karel-brinda karel-brinda changed the title Add option for a new output format Adding a new output format May 1, 2018
@salikhov-kamil
Copy link
Member

@karel-brinda what is "ref k-mer set name" here?

@salikhov-kamil
Copy link
Member

and one more suggestion: let's remove old output format? (it is needed for tests only I guess)

@karel-brinda
Copy link
Member Author

karel-brinda commented May 2, 2018

what is "ref k-mer set name" here?

name of the k-mer set (before @)

let's remove old output format

We need the old format, too. It's much more appropriate for long reads (image, e.g., 1 Mbp long read that has some matches with all reference k-mer sets; the bit-mask format may occupy even several GB per a single read).

@simonepignotti
Copy link
Member

simonepignotti commented May 2, 2018

I suggest adding the read length as well (redundant, but useful).

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

3 participants