-
Notifications
You must be signed in to change notification settings - Fork 90
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
MuscleApp takes extremely long/does not finish #273
Comments
Thank you, I will have a look into this. |
I made some investigations and have an idea what happens here: Compared to Clustal Omega, MUSCLE by default prints its progress to stderr in an extremely verbose manner. I suspect that the amount is so large, that the stderr fills up and MUSCLE waits for the stderr to be read (and hence emptied) by the other end of the pipe. In case of the terminal this is not a problem, as the terminal directly prints all characters it receives from the stderr. However, Biotite reads the stderr/stdout only after the program terminates. This leads to a deadlock with MUSCLE waiting for the stderr to be read and Python wating for MUSCLE to finish. I will create a PR with two measures to fix this issue:
|
I am trying to align 99 sequences with an avg sequence length of 865 via muscle, but the process seems to be either locked or blocked in some way (muscle is visible in htop but no CPU is used).
Example code, mainly copy-pasta from the biotite gallery/tutorial:
Interestingly, when I run the command from
app.get_command()
manually, this produces the expected output file within ~15 sec, while the biotite script still didn't finish after 15 minutes. Finally, switching fromMuscleApp
toClustalOmegaApp
in the script works and produces an alignment. Therefore, this issue seems to be related toMuscleApp
only.Hopefully, this issue is reproducible on other machines at all! ;)
The text was updated successfully, but these errors were encountered: