This page will be used to track changes in STRNaming nomenclature. While our top priority is to keep the nomenclature as stable as possible, STRNaming is a new and (internally) sophisticated nomenclature system, and therefore it is to be expected that some bug fixes and improvements based on user feedback may lead to slight changes in the generated allele names.
STRNaming version numbering
The Python implmentation of STRNaming uses a three-part semantic versioning system. For example, the version number '1.2.3' corresponds to major version 1, minor version 2, patch version 3. For STRNaming, these are defined as follows:
- The major version number is changed only if the algorithm is significantly modified and nomenclature of many loci is changed as a result. No plans for an 'STRNaming 2.0' currently exist, though.
- A change in the minor version number indicates that the reference structures of some forensic STR loci have changed in a significant way, such as a change in the genomic start and end position of the reference structure. We expect updates like this to quickly become much more rare over time, as the use of STRNaming gains traction.
- A change in the patch version number indicates that changes are limited to code improvements which may cause only a minor change in a small number of alleles, if any.
A full description of the technical changes in each version is available in the package's CHANGELOG.
Overview of STRNaming releases
The table below lists all known changes in allele naming between different versions of STRNaming. Example allele names are displayed using UAS Flanking Region Report ranges; some contextual reference sequence is given in lowercase letters.
|Version||Release Date||Example Allele Names||Changed Loci||Reference|
|v1.1.0||2021-07-15||Click here||Structure: FGA, DYS385a-b, DYS19, DYS437, DYS448, DYF387S1
Patches only: PentaD, DYS612, D21S11
|v1.0.0||2020-12-21||Click here||Not applicable||doi.org/10.1016/j.fsigen.2021.102473|