Details
-
Type:
Bug
-
Status: Open
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: 2.12.0, 2.11.5.1
-
Component/s: data retrieval services, Structures
-
Labels:None
Description
Alphafold Multimer entries are not properly supported in either Jalview 2.11.5.1 or Jalview 2.12 - but with different behaviours.
Both:
- The alphafoldDB ID format has changed, so Jalview fails to recognise the mulitimer entries in the 3d-beacons lookup as also having an associated PAE json file.
2.11.5 (and mostly 2.12)
- importing the downloaded mmCIF yields a structure where just one chain is mapped to the seuqence, when in fact all copies should be mapped (JAL-3489,JAL-2691, JAL-2694, JAL-3489 related)
2.12. Importing a downloaded mmCIF yields NO DATA when trying to import into Jalview 2.12. It looks like there's a bug in the version of Jmol used for 2.12 which means the atom names in mmCIF files are not properly resolved.
Both:
- The alphafoldDB ID format has changed, so Jalview fails to recognise the mulitimer entries in the 3d-beacons lookup as also having an associated PAE json file.
2.11.5 (and mostly 2.12)
- importing the downloaded mmCIF yields a structure where just one chain is mapped to the seuqence, when in fact all copies should be mapped (JAL-3489,
2.12. Importing a downloaded mmCIF yields NO DATA when trying to import into Jalview 2.12. It looks like there's a bug in the version of Jmol used for 2.12 which means the atom names in mmCIF files are not properly resolved.