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

IQTREE Error #10

Open
njdowdy opened this issue May 7, 2024 · 2 comments
Open

IQTREE Error #10

njdowdy opened this issue May 7, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@njdowdy
Copy link

njdowdy commented May 7, 2024

Description of the bug

Running the test dataset on initial install yields the IQTREE error:

ERROR: It makes no sense to perform bootstrap with less than 4 sequences.

This is expected behavior for IQTREE (see issue: Cibiv/IQ-TREE#155), however this causes PipeSnake to exit, failing to complete the remainder of the pipeline.

I fixed this by appending the -keep-ident option to the IQTREE command on Line 38 in modules/local/iqtree.nf (see IQTREE General Options for more info on -keep-ident). However, it would be better if PipeSnake handled the issue in a better manner, as using -keep-ident may increase the run time of the analysis per Heiko Schmidt here and I think making the user explicitly aware of this issue would be better.

Command used and terminal output

nextflow run ausarg/pipesnake -profile test --outdir ./test -with-conda true

Relevant files

No response

System information

Nextflow version 23.10.1 build 5891
Hardware: HPC
Executor: local
Container engine: Conda in Docker
OS: Debian 12
Version of ausarg/pipesnake 1.1

@njdowdy njdowdy added the bug Something isn't working label May 7, 2024
@IanGBrennan
Copy link
Contributor

Hey there, thanks for giving pipesnake a run.

In retrospect, choosing four samples of the same species for the example data was probably not my cleverest move. I'll try and swap those example data out so that this issue doesn't happen to folks in the future, thanks for bringing it to our attention. Will close this once I've replaced those samples.

Cheers.

@njdowdy
Copy link
Author

njdowdy commented May 7, 2024

I think it would be useful to make the PipeSnake workflow log and then throw out any loci that are invariant for all taxa, even if it is in the set of targets. I can imagine cases where we may not know a priori whether all the targets are going to be well-behaved or not.

I'm looking forward to digging into PipeSnake more!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants