-
Notifications
You must be signed in to change notification settings - Fork 27
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
Required argument error with hal2mafMP.py #60
Comments
Hi, Ok, so seems that HAL API have changed at some point.. Could you share a link to the exact version that you have installed? Thanks, |
I installed the release-V2.1 version, i.e. downloaded it with: If it helps, things seem to work if I run
The scaffolds look good by a very cursory examination (dotplot and BUSCO). |
Ok, I'm glad that it worked this time. I'm following up with the HAL developers on how to better resolve this. |
So the initial issue with the required arguments seems to be fixed; however running This issue isn't Ragout-specific. It occurs with I'll do more testing to see if I can reproduce this for a completely different alignment. |
@bernard-kim are you using hal2maf version from after this fix: ComparativeGenomicsToolkit/hal#117? If so, could you please post the full |
Hi @fenderglass, hal2mafMP.py commandline thanks, |
@stsmall thanks for the feedback. Yes, I think both of your suggestions are valid, I can't think about other alternatives right now. In fact, it might make sense to switch to single-threaded hal2maf for now. But I also hope that the HAL developers should be able to fix this in the near future. Mikhail |
Hi Mikhail,
I'm trying to get Ragout (2.3) running, however, it seems that HAL tools (2.1) are expecting a required argument that never gets passed to it.
Specifically, at the start of the "Converting HAL to MAF" stage
hal2mafMP.py
returns:RuntimeError: --splitBySequence, --refTargets or --refSequence required
The HAL2MAF command line in
Ragout/ragout/synteny_backend/hal.py
doesn't seem to contain this argument.The text was updated successfully, but these errors were encountered: