Closed tomsitter closed 7 years ago
I found this command in the biobox cli
>biobox verify short_read_assembler bioboxes/megahit
Error "bioboxes/megahit" is not a valid short_read_assembler biobox.
Should create a contigs file when given a valid biobox.yml and FASTQ data.
Hi Tom,
could you try to run the following steps:
mkdir input output
wget -O input/reads.fq.gz \
--quiet \
'https://www.dropbox.com/s/j1z91gr9ovboekm/genome_reads.fq.gz?dl=1'
cat << EOF > input/biobox.yaml
version: 0.9.0
arguments:
- fastq:
- id: fastq
type: paired
value: /fastq/input.fq.gz
EOF
docker run -v "${PWD}/input/biobox.yaml:/bbx/input/biobox.yaml:ro" -v "${PWD}/input/reads.fq.gz:/fastq/input.fq.gz:ro" -v "${PWD}/output:/bbx/mnt/output:rw" bioboxes/megahit default
I just want to make sure that it is not a bug in the biobox.
Hi, the box looks like it ran successfully using this code but I have no files in output/.
mkdir input output
wget -O input/reads.fq.gz \
--quiet \
'https://www.dropbox.com/s/j1z91gr9ovboekm/genome_reads.fq.gz?dl=1'
cat << EOF > input/biobox.yaml
version: 0.9.0
arguments:
- fastq:
- id: fastq
type: paired
value: /fastq/input.fq.gz
EOF
docker run -v "${PWD}/input/biobox.yaml:/bbx/input/biobox.yaml:ro" -v "${PWD}/input/reads.fq.gz:/fastq/input.fq.gz:ro" -v "${PWD}/output:/bbx/mnt/output:rw" bioboxes/megahit default
MEGAHIT v0.2.1
[Thu Jan 21 17:52:10 2016] Start assembly. Number of CPU threads 2.
[Thu Jan 21 17:52:10 2016] Extracting solid (k+1)-mers for k = 21
[Thu Jan 21 17:52:14 2016] Building graph for k = 21
[Thu Jan 21 17:52:21 2016] Assembling contigs from SdBG for k = 21
[Thu Jan 21 17:52:29 2016] Extracting iterative edges from k = 21 to 31
[Thu Jan 21 17:52:31 2016] Building graph for k = 31
[Thu Jan 21 17:52:33 2016] Assembling contigs from SdBG for k = 31
[Thu Jan 21 17:52:35 2016] Extracting iterative edges from k = 31 to 41
[Thu Jan 21 17:52:35 2016] Building graph for k = 41
[Thu Jan 21 17:52:37 2016] Assembling contigs from SdBG for k = 41
[Thu Jan 21 17:52:38 2016] Extracting iterative edges from k = 41 to 51
[Thu Jan 21 17:52:38 2016] Building graph for k = 51
[Thu Jan 21 17:52:39 2016] Assembling contigs from SdBG for k = 51
[Thu Jan 21 17:52:40 2016] Extracting iterative edges from k = 51 to 61
[Thu Jan 21 17:52:40 2016] Building graph for k = 61
[Thu Jan 21 17:52:40 2016] Assembling contigs from SdBG for k = 61
[Thu Jan 21 17:52:41 2016] Extracting iterative edges from k = 61 to 71
[Thu Jan 21 17:52:41 2016] Building graph for k = 71
[Thu Jan 21 17:52:41 2016] Assembling contigs from SdBG for k = 71
[Thu Jan 21 17:52:42 2016] Extracting iterative edges from k = 71 to 81
[Thu Jan 21 17:52:42 2016] Building graph for k = 81
[Thu Jan 21 17:52:42 2016] Assembling contigs from SdBG for k = 81
[Thu Jan 21 17:52:42 2016] Extracting iterative edges from k = 81 to 91
[Thu Jan 21 17:52:42 2016] Building graph for k = 91
[Thu Jan 21 17:52:43 2016] Assembling contigs from SdBG for k = 91
[Thu Jan 21 17:52:43 2016] Extracting iterative edges from k = 91 to 99
[Thu Jan 21 17:52:43 2016] Building graph for k = 99
[Thu Jan 21 17:52:43 2016] Assembling contigs from SdBG for k = 99
[Thu Jan 21 17:52:44 2016] Merging to output final contigs.
[Thu Jan 21 17:52:44 2016] ALL DONE.
One point to note -- I was using a test instance with only 1 CPU so megahit wouldn't run even with this workaround until I resized my instance (I instead got a message saying Number of CPU threads should be at least 2!
)
It may be useful to use a different box in the tutorial because I suspect other users may be using a similar low-powered test setup.
Any update on this? I didn't receive any output despite the biobox running. Thanks!
Using the 0.3.0 release.
Number of CPU threads should be at least 2!)
I got the same error message. I'm using a macbook air using a "1.6 GHz Intel
Core i5" which I believe has two cores. I think this error is could be due to
boot2docker
creating a virtual machine which may have less than the required
number of cores. Either way including bioboxes/megahit in the tutorial might
not be appropriate if this error might commonly occur. This is also likely the
reason the verify command failed as this also fails for me too.
@tomsitter please try changing:
"${PWD}/output:/bbx/mnt/output:rw"
To the following:
"${PWD}/output:/bbx/output:rw"
And see if this works.
@tomsitter did you have a chance to rerun this with the command above?
@pbelmann I'm going to change the name of this issue so that it is more specific to problem that Tom appears to be describing.
@michaelbarton I was testing this for a short contract last year. No longer have the same environment set up for testing
@michaelbarton , @tomsitter I tried to reproduce the error but it did not appear. However since then there have been updates in megahit and the bioboxes commandline interface. I will close this issue. Please reopen it if you encounter it again.
@pbelmann when you tried to reproduce the issue, were you using a single CPU?
I think I used the biobox cli --cpuset parameter. I will check that and report.
Thanks Peter
I can confirm that it produces a fasta file with --cpuset="1" parameter.
Thanks Peter, we can revisit this issue if it appears again.
I'm following the tutorial and successfully ran the biobox/velvet example with the test dataset. When I try to follow the last step (switch to biobox/megahit) I encountered this error.
Below are my installation and test commands (that were all successful)
On fresh Debian GNU/Linux 8 (jessie) OS, Kernel version 3.16.0-4-amd64 (from DigitalOcean)
Install Docker
Test Docker
Install Biobox
Test Biobox