Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with --keep-dup #163

Open
paulicm-UCD opened this issue Nov 29, 2016 · 3 comments
Open

Error with --keep-dup #163

paulicm-UCD opened this issue Nov 29, 2016 · 3 comments

Comments

@paulicm-UCD
Copy link

Dear Tao,

I tried to use --keep-dup all and got this error:

INFO @ Sat, 12 Nov 2016 12:10:38: #3 Call peaks...
Traceback (most recent call last):
File "/usr/bin/macs2", line 370, in
main()
File "/usr/bin/macs2", line 193, in main
if t1 > c1:
UnboundLocalError: local variable 't1' referenced before assignment

My script was:
module load macs2/2.1.0.20140616
macs2 callpeak -t x.bam -c input.bam -f BAM -g hs -n x_vs_input -B --keep-dup all -q 0.01

When using --keep-all auto, I had no errors. Could you please advice re: usage for -keep-dup all?
Thanks in advance,
Pauli

@taoliu
Copy link
Contributor

taoliu commented Dec 8, 2016

Hi Pauli,

Could you upgrade MACS2 to the recent version to see if the problem is still there?

Best,
Tao

@paulicm-UCD
Copy link
Author

Hi Tao,
I just had tried macs2/2.1.1.20160309 and got the same error:

INFO @ Thu, 08 Dec 2016 13:15:27: #3 Call peaks...
Traceback (most recent call last):
File "/usr/bin/macs2", line 370, in
main()
File "/usr/bin/macs2", line 193, in main
if t1 > c1:
UnboundLocalError: local variable 't1' referenced before assignment

Thanks,

Pauli

@taoliu
Copy link
Contributor

taoliu commented Mar 22, 2017

Hi @paulicm-UCD, sorry for a very late followup. It seems like you were keeping running a 'macs2' script from system folder '/usr/bin/macs2' which you may not have permission to update. I suspect that that script was from an unknown older installation because currently there is no 't1>c1' in macs2 script at line 193. And you new updates were at different location so you need to set linux environment correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants