CHIP-SEQ Peak Caller MACS index out of range resolution

When using MACS1.4 for peak calling, a strange problem was found:

Some of my files cannot be MACS1.4 for peak calling, and the following information appears:

Traceback (most recent): File"/USR/LOCAL/BIN/MACS14", Line 5,inch<module>Pkg_resources.run_script ('macs==1.4.2','MACS14') File"/library/python/2.7/site-packages/distribute-0.6.34-py2.7.egg/pkg_resources.py", line 505,inchrun_script Self.require (Requires) [0].run_script (Script_name, NS) File"/library/python/2.7/site-packages/distribute-0.6.34-py2.7.egg/pkg_resources.py", line 1252,inchRun_scriptexecScript_codeinchnamespace, namespace File"/LIBRARY/PYTHON/2.7/SITE-PACKAGES/MACS-1.4.2-PY2.7.EGG/EGG-INFO/SCRIPTS/MACS14", Line 366,inch<module>File"/LIBRARY/PYTHON/2.7/SITE-PACKAGES/MACS-1.4.2-PY2.7.EGG/EGG-INFO/SCRIPTS/MACS14", line 124,inchMain File"build/bdist.macosx-10.7-intel/egg/macs14/peakmodel.py", line 76,inch __init__File"build/bdist.macosx-10.7-intel/egg/macs14/peakmodel.py", line 112,inchBuild File"build/bdist.macosx-10.7-intel/egg/macs14/peakmodel.py", line 172,inch __paired_peak_modelIndexerror:list Index out of range

There is no good solution on the Internet. When you finally try it yourself, you find that this could be an error in the program building model. Macs Peak Calling mode can be changed to "--nomodel" to get peak, the effect is not bad.

Macs14-t chip-seq_experiment-c chip-seq_input--nomodel ...

CHIP-SEQ Peak Caller MACS index out of range resolution