You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I experienced a problem where the pipeline fails first with PRESEQ_LCEXTRAP and then with NFCORE_CUTANDRUN:CUTANDRUN:MACS2_CALLPEAK_NOIGG or PREPARE_PEAKCALLING:UCSC_BEDGRAPHTOBIGWIG depending on configuration.
This was caused by empty bam files after blacklist filtering which in turn was caused by an empty output from PREPARE_GENOME:BLACKLIST_BEDTOOLS_INTERSECT due to my genome fasta and blacklist bed having different chromosome labels (e.g. Chr1 vs. 1).
My issue was fixed by changing to a fasta that matches the format of the blacklist, but could a test be introduced to identify this issue more intuitively? This may be an initial test of the formatting of the input files, or a test that the output from bedtools intersect is not empty?
The text was updated successfully, but these errors were encountered:
Description of feature
I experienced a problem where the pipeline fails first with PRESEQ_LCEXTRAP and then with NFCORE_CUTANDRUN:CUTANDRUN:MACS2_CALLPEAK_NOIGG or PREPARE_PEAKCALLING:UCSC_BEDGRAPHTOBIGWIG depending on configuration.
This was caused by empty bam files after blacklist filtering which in turn was caused by an empty output from PREPARE_GENOME:BLACKLIST_BEDTOOLS_INTERSECT due to my genome fasta and blacklist bed having different chromosome labels (e.g. Chr1 vs. 1).
My issue was fixed by changing to a fasta that matches the format of the blacklist, but could a test be introduced to identify this issue more intuitively? This may be an initial test of the formatting of the input files, or a test that the output from bedtools intersect is not empty?
The text was updated successfully, but these errors were encountered: