-
Notifications
You must be signed in to change notification settings - Fork 20
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
SeqChunker error #47
Comments
Hi, you are probably right with the readlink problem. I am not that familiar with MacOS, I assigned the issue to my colleague Frank - he fixed the Mac related issue last time. Cheers |
I am sorry, not to response earlier. Indeed it is a problem with |
The new version 0.4 of SeqChunker is supporting MacOSX, therefore this should resolve that issue. @thackl needs to approve the pull request, afterwards version 2.12.13 of proovread should work on Macs. @cmorganl are you able to run a test on your sequence data after the merge into our master branch? Just make sure you are using at least version 2.12.13 of proovread. Let me know, if that solves your problem. Best, |
Hi @greatfireball, I'm still experiencing an issue running Mac 10.6.8. The initial error has been fixed but another has cropped up. Here is the stdout:
SakinawLake_120mMay2011_allD/bwa-sr-1/SakinawLake_120mMay2011_allD_bwa.log contains the two lines:
Let me know if you need futher information. |
hiii |
Try to call SeqChunker with its complete path |
No...!! Showing like FILE should be located at '/home/Documents/Tools_NGS/proovread/bin/../util/SeqChunker/bin/SeqChunker' |
Does the SeqChunker file exist at the location it says above? |
yes. It is there. but the folder shows a lock image. When i try to call with its complete path, showing like "FILE should be located at '/home/Documents/Tools_NGS/proovread/bin/../util/SeqChunker/bin/SeqChunker' |
Hm, no idea what the lock means. The "File should ..." message itself is not an error, just a log message. Here is how things look like when I run SeqChunker
Have you tried it with a fasta/fastq file? |
I tried with fastq file about size of 1.7 gb(mitochondrial sequence). Then i skipped the seqchunker step and run proovread directly.
Command used is given below.. **> /home/Documents/Tools_NGS/proovread/bin/proovread -l pacbio.fa -s /media/TOSHIBAEXT/illumina/R1.fastq -s /media/TOSHIBAEXT/illumina/R2.fastq -t 20 --overwrite -p pacbio_corrected
|
OK, this won't work because proovread also uses SeqChunker internally. However, I don't think that the error you got from bam2cns is even related to this. To really be able to help you I need some more information. How did you install proovread in the first place, did you just copy and paste from the install instructions? Did you move the folder with the files afterwards? And could you attach the complete log output of the crashed run? And lastly, have you tried to run proovreads example dataset |
I've installed from the root by using 'sudo' command and didn't move any files from the proovread folder.Also used 'make sample' command.but,it ran smoothly without showing any error messages.Please find the attached log file.Thank you.
R1.fastq R2.fastq [Tue Apr 2 15:02:29 2019] Checking required binaries [ok] samtools-1.7 /usr/local/bin [Tue Apr 2 15:02:29 2019] Running mode: sr #------------------------------------------------------------------------------# [Tue Apr 2 22:21:53 2019] Running task bwa-sr-1 [Tue Apr 2 23:22:52 2019] Sorting BAM
|
Ah, ok, that helps. Your actual problem is not coming from proovread. Have a look at the last command in the log to The 2GB are currently hard coded, you could change them by opening the |
my system has 16 gb of ram size,but still facing the same issue. |
OK, that is odd. Can you try and just run that samtools line directly?
|
Hm, thinking about it, it probably means that other things on your system (including proovread) are taking up most of the RAM. Can you monitor the RAM consumption while running proovread? |
Hi @thackl,
I'm encountering an issue very similar to #5 where proovread is unable to locate SeqChunker-perl.
However, after recreating the symlink as well as using the quick and dirty workaround of directly copying SeqChunker-perl to proovread/bin/ it still isn't able to locate it and I don't know what working directory its attempting to call it from. Maybe this stems from the readlink command instead? Here's the repeated error message:
Finally resulting in:
This is a different computer than what I was running in a previous issue, running Mac10.6.8 and perl version 5.18. Let me know if you need any more information.
Thanks for your help.
The text was updated successfully, but these errors were encountered: