Skip to content
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

Tracing issues with racon after running mini_assemble #23

Open
beasty1711 opened this issue Oct 3, 2018 · 6 comments
Open

Tracing issues with racon after running mini_assemble #23

beasty1711 opened this issue Oct 3, 2018 · 6 comments

Comments

@beasty1711
Copy link

Is there any way of tracking/ tracing issues with racon thats included in Pomoxis?

I'm getting "[racon::Polisher::initialize] error: empty target sequences set!" after running mini_assemble.

@cjw85
Copy link
Member

cjw85 commented Oct 3, 2018

Hi @beasty1711

Can you provide the full command you are running (mini_assemble has several modes of operation), and the full log of its output?

@beasty1711
Copy link
Author

Hi,

Thanks for getting back to me, the command is:

mini_assemble -i ~/data/filtered/combined_filtered.fq -o denovo -p barcode09_denovo -t 14 -c

Where about's would I find the full log? (I'm the IT guy helping the scientist so not fully aware of the program specifics)

@cjw85
Copy link
Member

cjw85 commented Oct 4, 2018

A lot of information is written to stderr and stdout of the programs which mini_assemble runs. Admittedly its a little daunting to trace back through that for the uninitiated. If you (or your user) can run the program again and redirect stdout and stderr to a file, we can take a look at that.

Your error would indicate that one stage of the pipeline has ended up filtering all the data, we should definitely catch that and report a more interpretable error, at the earliest opportunity. We can guess at a fix but can't guarantee that's going to resolve your particular issue.

@beasty1711
Copy link
Author

A lot of information is written to stderr and stdout of the programs which mini_assemble runs. Admittedly its a little daunting to trace back through that for the uninitiated. If you (or your user) can run the program again and redirect stdout and stderr to a file, we can take a look at that.

Your error would indicate that one stage of the pipeline has ended up filtering all the data, we should definitely catch that and report a more interpretable error, at the earliest opportunity. We can guess at a fix but can't guarantee that's going to resolve your particular issue.

Sorry for the long time in responding. The scientist has now gotten further, but receives the attached.
Is there any documentation for the tool-set for debugging issues such as this?
image

@cjw85
Copy link
Member

cjw85 commented Dec 7, 2018

We are currently updating the documentation, and will add an FAQ section.

We have seen this error when the third party racon program is given a sequence file in the fasta format with file extensions usually used for the fastq format (or vice versa). The programs run by mini_assemble before the racon step are not as strict in this regard.

Can you ask your user to check their input has the correct file extension given its format?

@JoannaTan
Copy link

Hi,

We are currently using Pomoxis to perform de novo assembly. However, we are also getting the following issue:

racon::createPolisher] error: file A_denovo_trimmed.fa.gz has unsupported format extension (valid extensions: .fasta, .fa, .fastq, .fq)!

This is the command that we used

mini_assemble -i A.fastq -o A_denovo -p A_denovo -t 16 -c

All our input files are in .fastq format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants