Description
Record an explicit codon role and genetic-code source.
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.
Record an explicit codon role and genetic-code source.
When to use this tool
Use Codon Start Stop Source Tag when you already have codonText, suppliedRole, geneticCodeSource and need to record an explicit codon role and genetic-code source.
How to use the tool and how it works
- Enter codonText, suppliedRole, geneticCodeSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter codonText, suppliedRole, geneticCodeSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| codonText | Codon Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedRole | Supplied Role | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| geneticCodeSource | Genetic Code Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"codonText": "ATG",
"suppliedRole": "start",
"geneticCodeSource": "table supplied by caller"
},
"output": {
"token": "[\"ATG\",\"start\",\"table supplied by caller\"]"
}
}Limitations and assumptions
- The result records supplied values without assigning start or stop status across code tables. Sources and asserted relationships are not independently authenticated.
- 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 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
- FASTQ Header Pair Index Token
Preserve an explicitly supplied FASTQ read pair index and source format.
- BED Zero To Start
Convert a nonempty zero-based half-open BED interval to one-based endpoints.