Closed GoogleCodeExporter closed 8 years ago
From reading other posts i'm guessing the problem is due to including multiple
haplotypes which means the 1st column names cause problems. I'll remove the
extra haplotypes, readjust nay dodgy names and hopefully it will work then.
Original comment by Mresc...@googlemail.com
on 2 Jun 2012 at 10:25
I remapped with stampy using a reference genome without haplotypes, converted
the sam files to bam files with samtools, sorted the bam files and retried,
using the same .2bit file. However, i still get the same error. Also I noticed
that in the output on screen the last chromosome is always duplicated. See
above the chr18_gl000207_random is duplicated. Whichever chromosome is last
appears to be duplicated. Not sure if this makes a difference. I might try
remapping with bowtie and see if that makes a difference but otherwise i am
stumped.
Original comment by Mresc...@googlemail.com
on 6 Jun 2012 at 9:58
(bam files converted standard bed format using bamtobed)
Original comment by Mresc...@googlemail.com
on 6 Jun 2012 at 9:59
It seems as though the issue is occurring where the chromosome 1 results are
being printed to file. Is an empty file even created upon segfault, or nothing
at all?
Original comment by homer...@gmail.com
on 6 Jun 2012 at 11:42
thanks.
No output file is created. I've checked all the permissions on that directory
and i've tried it with and without an actual empty file of the name specified.
Original comment by Mresc...@googlemail.com
on 7 Jun 2012 at 12:30
Just wondering if there was any update on what you thought might be wrong?
The actual zinba function works fine with the data so its nearly there but it
would be so wonderful to be able to use the refinepeaks function too.
Original comment by Mresc...@googlemail.com
on 11 Jun 2012 at 7:54
I can't seem to pinpoint what the error could be, so if you could send me a
subset of your mapped reads (from chr1 or a random sample of all reads) then
I'll give it a run on my setup to see if I can reproduce the error. You can
send a compressed file to homeriq5@gmail.com and I will work on this
Original comment by homer...@gmail.com
on 11 Jun 2012 at 8:01
we are currently incorporating these issues into a new zinba version, check
back soon for a comprehensive update
Original comment by homer...@gmail.com
on 20 Nov 2012 at 8:54
Original issue reported on code.google.com by
Mresc...@googlemail.com
on 28 May 2012 at 10:41