|
| 1 | +HEAD |
| 2 | +==== |
| 3 | + - The new :class:`modelcif.CustomTemplate` class allows for custom templates |
| 4 | + (that have not been deposited in a database such as PDB) to be referenced, |
| 5 | + together with their atomic coordinates (#1). |
| 6 | + - Model quality scores can now be defined that act on single features or |
| 7 | + pairs of features using the :class:`modelcif.qa_metric.Feature` and |
| 8 | + :class:`modelcif.qa_metric.FeaturePairwise` classes, respectively. |
| 9 | + Features can be defined as groups of atoms, residues, or asyms (#38). |
| 10 | + - The :class:`modelcif.associated.QAMetricsFile` class should now be used |
| 11 | + to reference files that contain model quality scores. The old name |
| 12 | + (LocalPairwiseQAScoresFile) is deprecated. This allows for all types of |
| 13 | + QA scores, not just local pairwise scores, to be stored in a separate file. |
| 14 | + - Sanity checks when writing out a file can now be disabled if desired, |
| 15 | + using the new ``check`` argument to :func:`modelcif.dumper.write`. |
| 16 | + - :class:`modelcif.reference.TargetReference` now takes an ``is_primary`` |
| 17 | + argument which can be used to denote the most pertinent sequence |
| 18 | + database reference. |
| 19 | + - Information on model groups (:class:`modelcif.model.ModelGroup`) is now |
| 20 | + written to the new ``ma_model_group`` and ``ma_model_group_link`` mmCIF |
| 21 | + tables, instead of ``ma_model_list``, to match the latest ModelCIF |
| 22 | + dictionary. Old-style information in ``ma_model_list`` will still be |
| 23 | + used when reading a file if these new tables are missing. |
| 24 | + |
1 | 25 | 1.2 - 2024-10-23 |
2 | 26 | ================ |
3 | 27 | - Data that have been split over multiple mmCIF or BinaryCIF files can now |
|
0 commit comments