Closed jdmontenegro closed 5 years ago
hmm never seen this error before. @JustinChu : any idea?
Some things you can try:
Running ./writeBloom_rolling.pl -f contigs_ge500.fasta -k 15 -p 0.0001 Does this work? If it does, try passing the resulting bloom filter (.bloom) to LINKS via the -r option
***Keep in mind that the Bloom filter functionality is NOT necessary for running LINKS with either ARCS or ARKS. You can turn off the Bloom filter with -x 1
Also, all the checks will be skipped if a checkpoint for your run exists in your directory:
-b contigs_ge500.fasta.scaff_s98_c5_l0_d0_e15000_r0.05_original
(Only specify the base name, not the full checkpoint file, LINKS will look for the extension it needs)
I'm not sure. This issue is perl basically saying we trying to free an object twice or something to that effect. Worst case it is some memory corruption in the c++ Bloom Filter code. I'd probably need a way to reproduce the error locally in order to fix it, however.
Note that -p is set to 0.0001 in the test, but it seems LINKS is doing -p 0.001 by default.
Test both
./writeBloom_rolling.pl -f contigs_ge500.fasta -k 15 -p 0.0001
./writeBloom_rolling.pl -f contigs_ge500.fasta -k 15 -p 0.001
Interestingly enough, increasing memory available in the scheduler did the trick. I am using 150Gb now and it seems to be working correctly. It just did not produce any scaffolds. I think that is because I was using the incorrect extension of the checkpoint file:
${base}_original.tigpair_checkpoint
instead of
${base}_original.tigpair_checkpoint.tsv
I am running it again and check out the results.
Cheers,
Hi guys,
I am really interested in using this tool for scaffolding with 10X chromium reads. I have cloned this git and installed the bloom filter with swig/3.0.12 with no problem. There are a few differences between the actual directory structure and the one assumed in the instructions. But anyway, inside the LINKS directory there is a bin directory with LINK in it. I created a lib directory inside and cloned the bloomfilter module in it. The test run correctly:
but when running the real case I get the following error:
So it seems something is broken. I have no idea what could be going wrong here. Could you help me sort this out?
Kind regards,