Thanks Devon. Unfortunately, I'm still getting the same error :(
balter@server:~$ conda install -c bioconda -c r macs2
Fetching package metadata ...........
Solving package specifications: ..........
Package plan for installation in environment <server path>/users/balter/miniconda2:
The following NEW packages will be INSTALLED:
macs2: 2.1.1.20160309-r3.2.2_0 bioconda
Proceed ([y]/n)? y
Linking packages ...
[ COMPLETE ]|############################################################################################################################################################################| 100%
balter@server:~$ which macs2
<server path>/users/balter/miniconda2/bin/macs2
balter@server:~$ macs2 --version
Traceback (most recent call last):
File "<server path>/users/balter/miniconda2/bin/macs2", line 4, in <module>
__import__('pkg_resources').run_script('MACS2==2.1.1.20160309', 'macs2')
File "<server path>/users/balter/miniconda2/lib/python2.7/site-packages/setuptools-23.0.0-py2.7.egg/pkg_resources/__init__.py", line 719, in run_script
File "<server path>/users/balter/miniconda2/lib/python2.7/site-packages/setuptools-23.0.0-py2.7.egg/pkg_resources/__init__.py", line 1496, in run_script
pkg_resources.ResolutionError: No script named 'macs2'
• 0 views
•
link