Closed jolespin closed 4 years ago
I am not sure why this would be occuring, are you saying it is truncating the name in the output coverage file or in the featurecounts output? What is the initial name of the file and how is it changing that name?
It could be related to featureCounts (I am currently running v1.5.3) and have never had issues with truncated bam file names, but there may be another issue at play here.
I'm using
Binsanity v0.2.8
Apologies for all of the activity on here lately. I've been trying to integrate Binsanity into some of the pipelines at my institute. Thought it would to log some of the issues and questions instead of just forgetting about them.