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

Some types of ambiguous reads lacking further taxon codes #108

Open
bkohrn opened this issue Feb 27, 2023 · 3 comments
Open

Some types of ambiguous reads lacking further taxon codes #108

bkohrn opened this issue Feb 27, 2023 · 3 comments

Comments

@bkohrn
Copy link
Collaborator

bkohrn commented Feb 27, 2023

Reads with a t0 = -1 (indicating between species ties) lack any further information indicating which species the code refers to a tie between. Ideally, these should be indicated.

@bkohrn
Copy link
Collaborator Author

bkohrn commented Feb 27, 2023

(e.g. in t1, t2, etc.)

@bkohrn
Copy link
Collaborator Author

bkohrn commented Feb 27, 2023

Seems to be happening in PostBlastProcessing2 (in postBlastFilter.py); not sure why; as far as I can tell, it shouldn't be doing that. I'll do some debugging in the sample I noticed this in.

@bkohrn
Copy link
Collaborator Author

bkohrn commented Feb 27, 2023

OK; figured out at least when it happens; this seems to happen when the two reads each have a singular best BLAST result, but don't agree on what that BLAST result is. Since the labeling of alternate species / blast results is based on a single-read basis, I need to come up with a way to recode this so both species are indicated in this event.

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

1 participant