Releases: salilab/modbase_utils
Releases · salilab/modbase_utils
modbase_utils 1.1 release
- Multiple directories can now be given to search for template mmCIF files with the
--repo
or-r
option. This is used in ModBase itself to also search for obsolete templates. - If template information cannot be extracted (e.g. if the template PDB code is invalid, or the scheme table is missing or incorrect) provide an output file with "unknown" mmCIF values for template entity, asym, and seqids.
modbase_utils 1.0 release
- Information about the database sequence for the model (e.g. in UniProt) is now provided both in the ModelCIF-specific
ma_target_ref_db_details
table and in the more generalstruct_ref
table.
modbase_utils 0.5 release
- New ModBase models containing multiline TITLE records and new-style EXPDTA records (where Modeller version information has been moved to a REMARK) are now handled correctly.
modbase_utils 0.4 release
- Author names are now PDB style ("Lastname, A.B.") rather than PubMed style ("Lastname AB").
- Old ModBase models containing UNK residues are now handled correctly.
modbase_utils 0.3 release
- The ModPipe databases (PDB95, UniProt90, profiles) are now linked from the modeling protocol in the output mmCIF file.
modbase_utils 0.2 release
- Sequence information for templates is now only written to template-specific categories in the mmCIF/BinaryCIF, not to the entity, entity_poly etc. tables, to properly comply with the ModelCIF dictionary.
modbase_utils 0.1 release
- First stable release. ModBase PDB files, together with the modeling alignments, can be converted to mmCIF compliant with the latest version (1.3.6) of the ModelCIF dictionary.