Random Coding DNA in Seqqio: Generate Reproducible DNA and Protein Pairs
Create three coding DNA and protein pairs in Seqqio, verify start and stop codons, export the results, and repeat the exact batch with a recorded seed.
When you test a translation or FASTA-import workflow, a DNA record is more useful when you also know its expected protein and how it was generated. Random strings of bases can contain internal stops. A complete coding-sequence model gives you a defined starting point for tests that expect an uninterrupted CDS.
Random Coding DNA is one of the 39 applications in Seqqio's Windows desktop toolkit. This tutorial follows two actual runs in Seqqio 0.1.0 on September 14, 2026. You can inspect the original exports below before deciding whether the graphical workflow fits your work.
1. Configure three sequences with 100-residue proteins
Open Random Coding DNA from Seqqio's application catalog. Select Batch output, then Load example. The built-in batch example supplies the following settings; you can also enter them directly.
| Control | Setting |
|---|---|
| Output mode | Batch output |
| Output sequences | 3 |
| Minimum length (codons) | 101 |
| Maximum length (codons) | 101 |
| Genetic code | 1 · Standard |
| Seed (optional) | 20260910 |
This is parameter-only generation: you do not paste a reference DNA sequence or a target protein. Equal minimum and maximum lengths give every output the same size. Different bounds request lengths sampled uniformly from the inclusive codon interval.
The length includes the start and terminal stop codons. For a requested length of n codons, the DNA has 3n nucleotides and the returned protein has n − 1 residues. Here, one initiator plus 99 internal codons produces 100 amino acids; the final stop adds three DNA bases and no amino acid.
2. Generate and inspect both sides of each pair
Click Generate sequences. The results show three successful outputs, each with 303 output symbols. Click a sequence title to open its detail view. Check Output length and Translated residues, then use the Output sequence and Translation tabs to inspect the DNA and protein.
| Output | Observed sequence pair |
|---|---|
| Output 1 | 303 nucleotides; 100 residues. Start ATG; terminal stop TAG. Protein begins MCFPADFLPPVK. |
| Output 2 | 303 nucleotides; 100 residues. Start TTG; terminal stop TAG. Protein begins MSLCSMCRAIRK. |
| Output 3 | 303 nucleotides; 100 residues. Start CTG; terminal stop TAA. Protein begins MCLTIAMSRGGV. |
The protein snippets show the first 12 residues, not the complete sequences. The downloads contain every nucleotide and amino acid. Output titles run from random-coding-dna_0000001 through random-coding-dna_0000003, so you can match records across files.
Why do TTG and CTG produce an initial M?
Under the Standard table used here, ATG, TTG, and CTG are eligible initiators. Seqqio applies complete-CDS conventions and translates the initiator as methionine, M. Internally, TTG and CTG encode leucine. The distinction is documented in the NCBI genetic-code reference.
Seqqio samples uniformly from the selected table's eligible initiators. These three outputs illustrate that model; they do not estimate the frequency of alternative initiation in an organism. If your test requires every sequence to begin with ATG, this generator's current settings do not enforce that constraint.
3. Export the sequences and preserve their settings
Use the export controls above the results. Save both sequence files together with the report and metadata. These are the original files from the tutorial run:
| Export control | File and purpose |
|---|---|
| FASTA | Download the three DNA sequences. Use these as complete-CDS inputs. |
| Translation FASTA | Download the three corresponding proteins. Match each protein to the DNA record with the same title. |
| Report TSV | Download the tab-separated report. Inspect status, identity, sequence, and translation together. |
| Run metadata | Download the run settings. Preserve the genetic code, length bounds, output count, seed, and method. |
Keep the JSON with the FASTA files. The FASTA headers retain record identity, seed, and method, but do not include the genetic-code setting. That setting is preserved in Run metadata. A downstream translator needs the same code to interpret the DNA correctly.
Verify the translation with matching conventions
We independently parsed the exported FASTA files with Biopython 1.87 and translated all three DNA sequences using Seq(dna).translate(table=1, cds=True). Every result matched its exported protein character for character. We also checked that the report contained the same DNA and protein sequences.
The Biopython translation documentation explains why cds=True matters: it checks the complete-CDS structure, treats an eligible initial codon as methionine, and excludes the terminal stop. Seqqio itself does not require Python; this was an independent check of its output.
| What you see | What to check |
|---|---|
| Output 2 or 3 starts with L instead of M | Ordinary translation can interpret the first TTG or CTG as an internal leucine codon. Use complete-CDS initiation rules for this comparison. |
| A trailing * appears after 100 amino acids | Your translator may retain a stop symbol. Seqqio's paired protein excludes the terminal stop; compare using the same convention. |
4. Repeat the batch and keep a recoverable run
Leave the parameters unchanged and click Generate sequences again. Export the DNA to a different filename. Our second run produced a FASTA file that was identical byte for byte, including the record headers. You can inspect the repeated DNA FASTA alongside the first export.
A seed is only part of the recipe. Retain the same application, method, genetic code, length settings, and output count when reproducing this example. The recorded method is Seqqio-SequenceGeneration-ChaCha20-v1. Leaving the seed blank requests a new system seed; the result records the resolved value.
Work history provides Restore setup for recovering saved parameters and the seed. Opening a saved result does not rerun generation. If session export files have expired, restore the setup and generate again. Keep your own project archive of the exported data and settings.
5. Choose the genetic code and batch size for your next test
Seqqio offers 27 NCBI genetic codes. Choose the table expected by the downstream workflow. For example, table 2, the Vertebrate Mitochondrial Code, assigns TGA to tryptophan and AGA/AGG to stops. Changing the table changes the generation model as well as the interpretation; see the official code definitions.
Some tables also contain codons that have different internal and terminal meanings. Seqqio follows complete-CDS semantics for those tables. Avoid applying a universal list of stop triplets without considering the selected code and position.
For larger datasets, adjust Output sequences after checking a small run. The implementation allows up to 1,000,000 outputs and 2–3,333,333 codons per sequence, subject to the separate 1,000,000,000 output-symbol and 4 GiB working-output budgets. These are simultaneous limits, not a promise that every combination fits. This tutorial tests three records, not maximum capacity or throughput.
Use the model for the right kind of work
Random Coding DNA is useful for complete-CDS test inputs, translation demonstrations, and workflows that need matched DNA and expected-protein files. Internal sense codons are sampled uniformly. Under code 1, six of the 61 sense codons encode leucine and one encodes methionine, so uniform codon sampling does not give every amino acid the same probability.
The generator does not optimize codon usage for a host, impose a GC target, or construct DNA for a protein you supply. A syntactically complete CDS does not establish expression, biological function, or suitability as an experimental negative control.
Bring generation, inspection, and repeatability into your desktop workflow
Seqqio puts the controls, paired results, saved setup, and exports in one graphical workspace. If you regularly prepare sequence test data and perform follow-up analysis, the Seqqio application overview shows how this generator fits into the wider toolkit.
The US$99 one-time purchase covers all 39 Seqqio applications. It provides a Windows 64-bit installer with no activation key. Consider the toolkit when you prefer graphical controls and expect to use several sequence tools. If an existing documented script already handles your complete workflow comfortably, use these files and checks to compare the practical fit.
References
- National Center for Biotechnology Information. The Genetic Codes NCBI Taxonomy genetic-code reference Standard Code (table 1), eligible initiation codons, and Vertebrate Mitochondrial Code (table 2) assignments.
- Biopython contributors. Bio.Seq module — Biopython 1.87 documentation Official Biopython 1.87 API documentation Bio.Seq.translate: table, cds, to_stop and the context-dependent stop-codon note.