You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 1.5.2 the name of the first sequence was the same as the name of sequence in the input fasta
Current Behavior
in 1.5.5 the first sequence is alwas named 101
Steps to Reproduce (for bugs)
Please make sure to reproduce the issue after a "Factory Reset" in Colab.
If running locally ypdate you local installation colabfold_batch to the newest version.
Please provide your input if you can share it.
This behavior is expected, but the resultant a3m file name (0.a3m) is not expected and difficult to handle. I've pushed a commit to use each header sequence name for the resultant file. Please update your ColabFold and try again.
Hello, related to this issue, I'm running colabfold through singularity using the latest Docker image (colabfold_1.5.5-cuda12.2.2.sif).
The output a3m files are numeric (e.g. 0.a3m) instead of the header sequence name, I guess because the latest Docker image was released before you fixed this issue. Could you update it, please?
Thanks in advance.
Expected Behavior
In 1.5.2 the name of the first sequence was the same as the name of sequence in the input fasta
Current Behavior
in 1.5.5 the first sequence is alwas named
101
Steps to Reproduce (for bugs)
Please make sure to reproduce the issue after a "Factory Reset" in Colab.
If running locally ypdate you local installation
colabfold_batch
to the newest version.Please provide your input if you can share it.
test.fa.gz
ColabFold Output (for bugs)
Please make sure to also post the complete ColabFold output. You can use gist.github.com for large output.
colabfold_search.log.gz
Context
Providing context helps us come up with a solution and improve our documentation for the future.
Your Environment
The text was updated successfully, but these errors were encountered: