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 am trying to recreate Fig 4 from Dominissi et al (https://www.nature.com/articles/nature11112) using meripseqpipe, and keep getting the same error in the PeakMerge process:
***** ERROR: Requested column 4, but database file - only has fields 1 - 0.
There is no peaks in one of the merged peaks files`
Merge Peaks by macs2 may not be suitable for your data.`
I have checked all of the .bed files used in this process, and all have 5 columns of data. By breaking up the mergebedByBedtools() function I've deduced this line results in an empty tmp._others_allPeaks.bed file.
When, for example, macs2 is used, only macs2*normalized.bed are available so grep -v returns nothing and mergeBed terminates with the error ***** ERROR: Requested column 4, but database file - only has fields 1 - 0. (See screenshots).
You can see my temp3.bed file is producing the error from mergeBed, since its empty.
What is the purpose of tmp._others_allPeaks.bed?
Can I simply comment out the offending line?
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to recreate Fig 4 from Dominissi et al (https://www.nature.com/articles/nature11112) using meripseqpipe, and keep getting the same error in the PeakMerge process:
I have checked all of the .bed files used in this process, and all have 5 columns of data. By breaking up the
mergebedByBedtools()
function I've deduced this line results in an emptytmp._others_allPeaks.bed
file.When, for example, macs2 is used, only
macs2*normalized.bed
are available sogrep -v
returns nothing andmergeBed
terminates with the error***** ERROR: Requested column 4, but database file - only has fields 1 - 0.
(See screenshots).You can see my
temp3.bed
file is producing the error from mergeBed, since its empty.tmp._others_allPeaks.bed
?The text was updated successfully, but these errors were encountered: