Similar to the issue in Tfit, FStitch is not capable of handling 0 coverage values in bedGraphs (as is formatted in deepTools output). It would be nice to just pre-filter those out (although this seems to have potentially generated another bug in Tfit).
If we do not or cannot effectively filter out these values, we need to be clear in the documentation for bedGraph format.
changed title from FStitch still choking on 0 coverage values in bedGraph to FStitch still choking on 0 coverage values in bedGraph{+ in segment (but not train)+}
In GitLab by @magr0763 on Sep 28, 2018, 09:33
Similar to the issue in Tfit, FStitch is not capable of handling 0 coverage values in bedGraphs (as is formatted in deepTools output). It would be nice to just pre-filter those out (although this seems to have potentially generated another bug in Tfit).
If we do not or cannot effectively filter out these values, we need to be clear in the documentation for bedGraph format.