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

Output lines lost in guidescan enumerate for no matches/mismatches #21

Open
vineetbansal opened this issue Aug 9, 2023 · 1 comment
Assignees

Comments

@vineetbansal
Copy link
Collaborator

vineetbansal commented Aug 9, 2023

In the case of 0 matches and 0 mismatches, guidescan enumerate --format csv fails to produce any output line corresponding to the kmer. guidescan enumerate --format sam produces a line, but it is truncated and does not have all expected columns.

For example, the kmer file:

id,sequence,pam,chromosome,position,sense
GCTAACCCAACGTAGCGACT_1,GCTAACCCAACGTAGCGACT,NGG,unknown,0,+

processed against hg38.index produces the sam line:

GCTAACCCAACGTAGCGACT_1	0	unknown	0	100	23M	*	0	0	GCTAACCCAACGTAGCGACTNGG	*

This is the case regardless of --mode succinct or --mode complete.

The desired behavior is to still produce the output line with the appropriate values so it is not simply "lost" in processing.
This was tested in guidescan v2.1.6

@vineetbansal vineetbansal self-assigned this Aug 9, 2023
@vineetbansal
Copy link
Collaborator Author

What should be the specificity value in this case?

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