-
Notifications
You must be signed in to change notification settings - Fork 14
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
Pileup_core and negative length vector #19
Comments
hey Armand, sorry for the slow reply I somehow missed your email. My first guess is that there is something wrong with your regions, can you print it out or send it to me? |
The regions file I use is the following :
|
are you sure the string '1' matches the way chromosome 1 is called in the bam file? if you do samtools view -H how is chromosome 1 called? usually its something like 'chr1'. |
I get
The .bam file I use comes from ENSEMBL rather than UCSC, I think that the chromosomes names don't start with 'chr'. |
The problem seems unrelated to epicseg but rather to its dependent package 'bamsignals'. How big are your BAM files and how many @sq header lines do they have? |
Is /homes/lacombe/nbu/data/kidney_a8w_DNase1_ENCODE86_bwa_samse_BR2TR1.bam a publicly available file? It may also be that the file is somehow corrupted, can you try to download it again? What if you try to get the count matrix only with the other BAM file, does that work? If the issue with that BAM file persist, it should be possible to reproduce it with the R code:
Warning, I haven't run that code so you may need to fix some small things. |
let me know if there is an issue with bamsignals, I am one of the maintainers and we should be able to fix that relatively quickly. |
The .bam file I'm using weights 129 MB. I'm not sure what is a @sq header line, but when I run the command samtools view -H I get 96 lines beginning with @sq. I don't think that my file is corrupted since it comes directly from ENSEMBL and I have no problem using it on other segmentation algorithms. However, the manual usage example works without any issue. I also ran the code you gave me and got :
|
Hey Armand, can you send me this BAM fie or point me to it? I'll have a look. |
Here it is : https://we.tl/SzP05vCmYi . Thank you very much ! |
I just ran:
Couldn't find any issues with that... I'll try with epicseg directly now. |
I cant reproduce your problems, I just ran:
And everything worked fine. What system are you using? R version? Bioconductor version? OS? G++ version? |
Can you print the output of 'session_info()' and 'sessionInfo()' at the interactive R console ? |
'session_info()' doesn't work but 'sessionInfo()' gets
I'm using Bioconductor version 3.6 (BiocInstaller 1.28.0) and gcc version 7.2.0 (crosstool-NG fa8859cb). I'll try to uninstall and reinstall the R packages. |
Hi,
Despite the fact that the example given in the manual works well, I can't manage to use getcounts with my own files. My command is :
./epicseg.R getcounts --mark DNase1:/homes/kidney_a8w_DNase1_ENCODE86_bwa_samse_BR2TR1.bam --mark H3K27ac:/homes/kidney_a8w_H3K27ac_ENCODE86_bwa_samse_BR2TR1.bam --regions /homes/contigs.bed --binsize 200 --target /homes/counts.txt
where contigs is a bed file I wrote imitating the example file. The error message I get is :
loading epicseg
getting counts
Processing /homes/lacombe/nbu/data/kidney_a8w_DNase1_ENCODE86_bwa_samse_BR2TR1.bam: tHe lEgEnD said, hE cOuLd PiLe uP fAsTeR thAn LiGht
Error in pileup_core(bampath, gr, tlenFilter(tlenFilter, pe), mapqual, : negative length vectors are not allowed
Calls: <Anonymous> ... bamProfile -> bamProfile -> .local -> pileup_core -> .Call
Execution halted
I get figure out what doesn't work since every vectors seems to be ok. I guess it might have something to do with bamsignals yet I can't fix it.
Do you have an idea ? Thanks a lot !
Armand
EDIT : lamortenera wrote something concerning a similar issue a few years ago there https://github.com/lamortenera/epicseg/issues/7 so I tried to follow the same steps ut it didn't worked. On top of that my data aren't that heavy, since I have only two tracks and about ~10000 bp only are selected by the contigs file.
The text was updated successfully, but these errors were encountered: