Description
Order simple star alleles numerically while preserving suballele spellings.
Pharmacogenomic records distinguish allele labels, copy counts, reference-sequence versions, coordinate systems, and evidence about chromosome phase. A balanced count or matching token can check a record without establishing the underlying genotype. Supplied activity values and interpretation rules remain separate from a current gene-specific clinical guideline.
Order simple star alleles numerically while preserving suballele spellings.
When to use this tool
Use Pharmacogene Diplotype Order Canonicalizer when you need this specific allele-token, reference-coordinate, copy-budget, or source-support check.
How to use the tool and how it works
- Enter first, second. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read first, second, swapped. Inspect swapped before interpreting the associated values.
Parse each allele as * followed by a positive integer and an optional decimal suballele suffix. Compare the major numbers using exact integers, then numeric suballele values, treating an absent suffix as -1. Return the original strings ordered by those keys and swapped.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First supported star-allele label; output is one original input string. | Required. Text; maximum UTF-16 length 8192. |
| second | Second supported star-allele label; output is one original input string. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| first | First supported star-allele label; output is one original input string. | Required. Text; maximum UTF-16 length 8192. |
| second | Second supported star-allele label; output is one original input string. | Required. Text; maximum UTF-16 length 8192. |
| swapped | Swapped | Required. Boolean. |
{
"input": {
"first": "*10",
"second": "*2"
},
"output": {
"first": "*2",
"second": "*10",
"swapped": true
}
}Limitations and assumptions
- Leading zeros in a suffix are preserved and numerically equal suffixes retain input order. No gene context, nomenclature lookup, phase, or clinical equivalence is established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use a current gene-specific nomenclature and a validated interpretation process when allele identity, phase, function, or clinical decisions matter. Verify source versions and reference coordinates before combining records.
References
Similar or alternative tools
- Pharmacogene Copy Number Token Field
Parse an explicit star-allele copy token; copies is zero when the copy number is unknown.
- pharmacogenomics/star-allele-diplotype-phase-separator
Split a simple two-star-allele diplotype subset without inferring haplotypes or function.