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

EPIC stops if treatment and control are both input files #36

Closed
c-guzman opened this issue Aug 11, 2016 · 5 comments
Closed

EPIC stops if treatment and control are both input files #36

c-guzman opened this issue Aug 11, 2016 · 5 comments

Comments

@c-guzman
Copy link

Because the way my pipeline is set up, it will typically run Input bed vs Input bed ... in MACS2 this is fine ... no peaks are called. But EPIC gets a command exit status 1:

Here is the output:

Command executed:

  epic --treatment Input_treatment.bed --control Input_control.bed --number-cores 3 --genome hg19 --fragment-size 150 > Input_epic.bed

Command exit status:
  1

Command output:
  (empty)

Command error:
      710 
      711     rizer = klass(max(len(lk), len(rk)))
      712 
  --> 713     llab = rizer.factorize(lk)
      714     rlab = rizer.factorize(rk)
      715 
      716     count = rizer.get_count()
      717 

  ...........................................................................
  /usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in pandas.hashtable.Int64Factorizer.factorize (pandas/hashtable.c:15715)()
      854 
      855 
      856 
      857 
      858 
  --> 859 
      860 
      861 
      862 
      863 

  ...........................................................................
  /usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in View.MemoryView.memoryview_cwrapper (pandas/hashtable.c:29784)()
      639 
      640 
      641 
      642 
      643 
  --> 644 
      645 
      646 
      647 
      648 

  ...........................................................................
  /usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in View.MemoryView.memoryview.__cinit__ (pandas/hashtable.c:26059)()
      340 
      341 
      342 
      343 
      344 
  --> 345 
      346 
      347 
      348 
      349 

  ValueError: buffer source array is read-only
  ___________________________________________________________________________

@endrebak
Copy link
Member

This is because of a bug in pandas. Try it without multiple cores :)

On Thu, Aug 11, 2016 at 8:57 PM, Carlos Guzman notifications@github.com
wrote:

Because the way my pipeline is set up, it will typically run Input bed vs
Input bed ... in MACS2 this is fine ... no peaks are called. But EPIC gets
a command exit status 1:

Here is the output:

Command executed:

epic --treatment Input_treatment.bed --control Input_control.bed --number-cores 3 --genome hg19 --fragment-size 150 > Input_epic.bed

Command exit status:
1

Command output:
(empty)

Command error:
710
711 rizer = klass(max(len(lk), len(rk)))
712
--> 713 llab = rizer.factorize(lk)
714 rlab = rizer.factorize(rk)
715
716 count = rizer.get_count()
717

...........................................................................
/usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in pandas.hashtable.Int64Factorizer.factorize (pandas/hashtable.c:15715)()
854
855
856
857
858
--> 859
860
861
862
863

...........................................................................
/usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in View.MemoryView.memoryview_cwrapper (pandas/hashtable.c:29784)()
639
640
641
642
643
--> 644
645
646
647
648

...........................................................................
/usr/local/anaconda2/lib/python2.7/site-packages/pandas/hashtable.so in View.MemoryView.memoryview.cinit (pandas/hashtable.c:26059)()
340
341
342
343
344
--> 345
346
347
348
349

ValueError: buffer source array is read-only



You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#36, or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0hZamm-zmcuSCcPjWPlRbdyvT0Wuks5qe3CwgaJpZM4Jib94
.

@endrebak
Copy link
Member

endrebak commented Aug 12, 2016

Did you get more or a longer error message than the one you posted? Did it work with one core?

@endrebak
Copy link
Member

endrebak commented Aug 15, 2016

Version 0.1.12 should fix this. Thanks for reporting.

pip install bioepic==0.1.12

@c-guzman
Copy link
Author

Just wanted to update this and say that the no cores option did fix the issues. Thanks!

@endrebak
Copy link
Member

Okay, super. If you also tried version 0.1.12 and it did not work, please tell me :)

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