Skip to content

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

@vineetbansal

Description

@vineetbansal

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions