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

kseq parser #6

Open
1 of 5 tasks
harishankarv opened this issue Mar 14, 2020 · 3 comments
Open
1 of 5 tasks

kseq parser #6

harishankarv opened this issue Mar 14, 2020 · 3 comments

Comments

@harishankarv
Copy link

harishankarv commented Mar 14, 2020

  • clean up kseqparser, add comments on issues below in code itself
  • what happens when individual sequences greater than 4096
  • when to encode, along with parsing?
  • encoding needs to handle N character
  • sliding window logic: character N logic
@harishankarv
Copy link
Author

harishankarv commented Mar 19, 2020

  • kseq.h expects a whole file (offset = beginning of file), but we are giving it offsets into middle of the file. So when one thread starts parsing from the middle of the file, kseq.h skips characters until it encounters the next "record" (the next ">" character). Need to handle this.

@utsavjainb
Copy link

utsavjainb commented Mar 23, 2020

  • clean up kseqparser, add comments on issues below in code itself
  • what happens when individual sequences greater than 4096
    kseq_read is able to read into buffer sequences long
  • when to encode, along with parsing?
    As of now, each individual sequence in read into kseq buffer, and then fully encoded into DnaBitset object (3 bit encoding).
  • encoding needs to handle N character
  • sliding window logic: character N logic
    Enqueues kmers of length k, if N character (encoded as 100) is found, pointer is shifted.

@utsavjainb
Copy link

  • kseq.h expects a whole file (offset = beginning of file), but we are giving it offsets into middle of the file. So when one thread starts parsing from the middle of the file, kseq.h skips characters until it encounters the next "record" (the next ">" character). Need to handle this.

Kseq_read handles this

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

No branches or pull requests

2 participants