-
Notifications
You must be signed in to change notification settings - Fork 68
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
BUSTED error: tree_id_0 is not a supported object type in call to SetParameter #1710
Comments
Dear @00-kelvin, This is most likely due to a sequence name with "odd" characters. Would you please share the input alignment and tree so I can check? Also, please confirm your Best, |
Alignment and tree attached as a zip file. Let me know if you can't open them for whatever reason. Many thanks for your quick reply! |
Dear @00-kelvin, Yes, a sequence name issue. I wrote a little utility script to help with this, and also to allow you to map slighlty non-matching IDs in the alignment / tree files (in your case you have The resulting
The "error-absorption" component allows you to filter out local alignment issue (use https://observablehq.com/@spond/busted to load the JSON and look around). Many automated alignment procedures leave things like the folllowing in place (amino-acids 1000-1050 in your example file), which would "light up" as selection, but are more likely misalignments/misannotation. Best, |
Many thanks, Sergei! I will definitely use the error-sink flag in the future, that seems very useful. Thank you for sorting this out for me. The clean-names tool will come in handy too, I'm sure. |
Hi Sergei! Sorry to bother you again -- I could not find where you attached the .json file. Would you be able to re-send? I was able to re-run the analysis with the error sink and get results, but I just wanted to check that they matched your results. Thank you! |
Dear @00-kelvin, I forgot to attach it before, oops. Best, |
Hi there!
I am testing out BUSTED on an alignment and I got an error which I cannot find anyone else running into online. This same error happened for 2 different alignments I tried to run. I think it may be related to the gene names that I have in my alignment and tree files (they are very long -- I'm planning to change them in the future) but I am not sure how/why. As far as I can tell, the gene names in the tree and the alignment files match one another. Do you know why I might be getting this error?
Here is the errors.log:
and if it helps, here is the rest of the system output from the attempt:
Thank you so much in advance for your help!
Calvin
The text was updated successfully, but these errors were encountered: