-
Notifications
You must be signed in to change notification settings - Fork 112
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
Problems with cactus-update-prepare #1595
Comments
Thanks. For For the multifurcations, that is indeed trickier. The current version of cactus is not as robust to them, and it's best to avoid them. What step exactly does it want to make a mulitifurcation for? It seems like it shouldn't be necessary when replacing a genome. |
Hi Glenn,
Thank you, Murillo |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In following the instructions described in https://github.com/ComparativeGenomicsToolkit/cactus/blob/master/doc/cactus-update-prepare.md#replacing-a-genome, I ran into some issues:
cactus-blast
andcactus-align
complained about the--realTimeLogging
flag, which (for these two commands) needs a--realTimeLogging True
(but note thatcactus-preprocess
doesn't need the boolean).cactus-align
complained about multi-furcations. So I copied the XML fromcactus/src/cactus/cactus_progressive_config.xml
Line 470 in fe99fe1
allow_multifurcations="1"
.I would be happy to contribute a PR modifying the python script
cactus-update-prepare
to add the boolean after--realTimeLogging
for the two commands that need it.The multifurcations issue is a bit trickier to deal with. Do we require that
cactus-update-prepare
be passed a custom XML config (to be used bycactus-blast
andcactus-align
?The text was updated successfully, but these errors were encountered: