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
It would be convenient if the output structure files from a modelling run had the supplied pLDDT values (in .npy form) contained within the PDB files. This would be consistent with how AlphaFold PDB files are expected (e.g. when downloading from the AF database).
Happy to work on this and submit a PR.
The text was updated successfully, but these errors were encountered:
I cobbled together the code below to add plddt to the bfactor column. This works for roughly 2/3 of my PDBs, but for the rest there is a mismatch between the number of residues and the plddt vector length, that I cannot explain. I've seen up to 10 residues difference and in all cases it's fewer residues in the pdb than the npy vector.
@phbradley would you have a hint as to how we can fix this? Thanks!
It would be convenient if the output structure files from a modelling run had the supplied pLDDT values (in
.npy
form) contained within the PDB files. This would be consistent with how AlphaFold PDB files are expected (e.g. when downloading from the AF database).Happy to work on this and submit a PR.
The text was updated successfully, but these errors were encountered: