-
Notifications
You must be signed in to change notification settings - Fork 47
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
convert.sh does not produce a .hic file in the appropriate format for juicebox #154
Comments
I met the same problem. How to deal with it. |
I mean, the answer from the Juicebox team seems to be "Don't use SALSA if you want to edit your assembly in Juicebox". Or alternately to run the final assembly from SALSA through the entire Juicer workflow to try to get to something compatible with Juicebox. But the Juicer workflow is a nightmare to get running. |
juicebox V 2.X can open the .hic generated by SALSA. |
Juicebox itself can open the .hic file and visualize it, but the parts of Juicebox for editing the assembly (aka "Juicebox assembly tools" or JBAT) require an "assembly" .hic file, which the file produced by SALSA is not. Here are some quotes from the Juicebox developer, from the issues I linked in the OP:
|
Okay, Thank you very much. |
I have created a tool to edit a contact map by directly reading SALSA output files (scaffolds_FINAL.agp, alignment_iteration_1.bed and assembly.cleaned.fasta). It only displays at the window size of the first specified resolution (default is 100 Kbp), but it seems to work faster. At least it worked well enough for me. |
Has anyone solved this problem? |
This is causing various downstream issues, as the next logical step after running SALSA is to manually edit the assembly, and juicebox seems to be the only tool to do that.
See:
aidenlab/Juicebox#958
aidenlab/Juicebox#975
and most likely:
aidenlab/Juicebox#972
The text was updated successfully, but these errors were encountered: