Description
Format a supplied protein-residue position and zero-based index.
Sequence formats distinguish coordinate origins, included endpoints, allele separators and identifier grammars. A genomic interbase position differs from a base number, and a parsed optional-field value may still violate its declared type. Local token checks preserve representation without validating a complete file, sequence, reference assembly or biological interpretation.
Format a supplied protein-residue position and zero-based index.
When to use this tool
Use Protein Residue Position Label when you already have sequenceId, residue, oneBasedPosition and need to format a supplied protein-residue position and zero-based index.
How to use the tool and how it works
- Enter sequenceId, residue, oneBasedPosition. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read label, zeroBasedIndex. Use the output convention below.
Require nonempty sequenceId, one ASCII uppercase letter or * residue, and a positive safe whole oneBasedPosition. Format sequenceId:residuePosition and return position-1.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sequenceId | Sequence Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| residue | One ASCII uppercase letter or *, without sequence or amino-acid vocabulary verification. | Required. Text; maximum UTF-16 length 8192. |
| oneBasedPosition | One Based Position | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| label | Label | Required. Text; maximum UTF-16 length 8192. |
| zeroBasedIndex | Zero Based Index | Required. Safe integer. |
{
"input": {
"sequenceId": "P17",
"residue": "K",
"oneBasedPosition": 42
},
"output": {
"label": "P17:K42",
"zeroBasedIndex": 41
}
}Limitations and assumptions
- The letter is not checked against a specific amino-acid alphabet or sequence. No sequence lookup, residue verification, variant interpretation or length bound 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use the complete applicable file specification and a full format validator for conformance. Verify reference assembly, sequence bounds, annotation and database context before interpreting local fields or coordinate transformations.
References
Similar or alternative tools
- Genomic Insertion Interbase Coordinate
Crosswalk a supplied left-base insertion position to an interbase coordinate.
- CDS Frame Offset
Calculate a supplied coding-sequence offset modulo three.