Closed sami-chaaban closed 1 year ago
Strange! No, the feature names are determined by the chains, but the name of the folder (within the output folder) is named after the fasta file. This is a relict from the original Uni-Fold pipeline, I should probably change this to directly use the output folder, makes more sense.
What does your chains.txt look like?
What does your chains.txt look like?
A B C D
I think I see what the issue is. Uni-Fold expects zero or one underscores in the sequence identifier and uses the part after the first underscore as the chain id. I am not sure I have the time to fix it today. A quick solution should be to rename the chains in the FASTA file. Easiest would be just A B C D. My guess is your feature files were overwritten unless it's a homomer you would need to re-run the MSA pipeline. Sorry for the trouble
No worries! I'll give this a shot and report back.
Hm, works actually fine in my small test. Could you attach the FASTA?
So it looks like it's not the chain naming, but the naming of the FASTA file. Shouldn't include underscores unless it is a divider for the chain.
Ok sounds good. Thanks again for testing this. I'll try it when I have access to the files in a bit
I pushed a fix. Let me know if it solves your issue.
Fixed, thanks!
My run seems to fail due to the feature pkl file not existing, see error below. It is looking for
A.feature.pkl.gz
intest-hex7/XI_VIEW_SY_XL_5_DSSO_XL_redo_sequences
but the only such file that I can find istest-hex7/XI/VIEW.feature.pkl.gz
. Does the filename for the fasta file dictate the feature filename?