Random DNA Sequences in Seqqio: Control Base Weights, Seeds, and Batch Size

When you prepare a FASTA import exercise or test a sequence-processing tool, the input needs to be recoverable. If an import fails, you want to return to the same records and settings. This example shows how to keep that connection from the first generation through later reuse.

Random DNA Sequence is one of 39 apps in the Seqqio toolkit. It brings generation, record inspection, exports, and work history into one local workspace. The tutorial gives you a complete task to try and concrete results to compare when evaluating that workflow.

In Seqqio, choose Generate, open Random DNA Sequence, and select Batch output. This generator needs parameters only; no input sequence or FASTA file is required.

Equal length bounds give every record exactly 301 bases. Uniform distribution gives A, C, G, and T equal probabilities. Enter all 20 seed digits exactly to reproduce the example; smaller seeds work for your own projects. If you use Load example, replace its demonstration values with the settings above.

1. Select Generate sequences. When the run finishes, confirm that it reports two generated outputs.
2. In Sequence results, check that both rows show Success and 301 output symbols.
3. Select #0000001 to open the first record, then scroll to Output sequence.
4. Inspect the bases and coordinates. Use the copy controls or Save this output FASTA to keep that record. Select Back to results to return to the batch.

The record identifier connects the detail view to its row and exported sequence. Display grouping helps you read the bases; it does not change the DNA in the export.

To check composition, calculate GC percentage = 100 × (G count + C count) / sequence length. We counted the exported bases independently to obtain the values below. These are calculated results, not GC fields in Seqqio's sequence detail view.

Uniform probabilities give an expected GC content of 50%. Individual sequences fluctuate around that expectation. A 301-base record cannot contain exactly equal counts of all four bases because 301 is not divisible by four.

Use the three export buttons above the result list. Save all three files in the same project folder so the DNA stays connected to its identifiers, results, and generation settings.

A FASTA header begins with > and a sequence identifier; sequence lines follow. The NCBI nucleotide FASTA guide explains this structure. Seqqio also includes provenance fields in its headers, so check the import requirements of the tool that will receive the file.

You now have a reusable dataset: the FASTA supplies the DNA, the TSV makes the output inspectable, and the JSON records how it was generated.

1. Keep the count at 2, both length bounds at 301, Uniform distribution, and the exact seed from Step 1.
2. Select Generate sequences again.
3. Save the new FASTA under a different name, such as gui-uniform-repeat.fasta.
4. Compare corresponding identifiers and bases. Join wrapped FASTA sequence lines before comparing sequence identity.

Our result: the repeated FASTA was byte-for-byte identical to the first export. You can inspect the second exported FASTA alongside the original.

For exact repetition, retain the app version, method identifier, seed, output count, length bounds, and complete base-weight settings. Our run used Seqqio-SequenceGeneration-ChaCha20-v1. Another generator can produce different DNA from the same seed.

To recover a setup later, scroll to Work history, choose Open beside the relevant run, and review its saved parameters. Select Restore this setup, then Generate sequences when ready. The history list also provides a direct Restore setup button. In our test, restoring the original entry recovered the two-record count, 301-base bounds, uniform distribution, and exact seed.

The seed field accepts decimal integers from 0 through 18446744073709551615. Leave it blank for a new seed, then keep the resolved value from the result or metadata if you want to repeat the run. Work history is useful for revisiting settings; it is not a substitute for your own project archive.

1. Open Input and generation settings. Keep the count, length bounds, and seed fixed.
2. Change Symbol distribution to Custom relative weights.
3. Enter A=2, C=3, G=3, T=2, generate the batch, and save its exports separately.

Expected GC fraction = (C weight + G weight) / total weight. Here, (3 + 3) / (2 + 3 + 3 + 2) = 60%. Each weight is an integer from 0 to 1,000,000, and at least one must be positive. A zero excludes that base. The weights do not need to total 100.

We counted the bases in the custom-weight FASTA and checked the exported JSON settings:

What changed: the same two-record, 301-base setup moved from 48.50% and 52.82% GC under uniform sampling to 61.79% and 64.12% with the custom weights. These four records demonstrate the example; they are not a statistical validation sample.

The settings define probabilities, not exact per-sequence quotas. Under independent base draws, the G-or-C count follows a binomial model. Applying the mean and standard deviation in the NIST binomial reference, a 301-base record at expected GC of 60% has a GC-percentage standard deviation of about 2.82 percentage points. This is a model calculation, not an interval every record must satisfy.

For a lower-GC exercise, weights 3/2/2/3 give a 40% expectation. Preserve the complete integer vector when repeating a run: a GC target alone does not specify the individual base probabilities.

1. Restore the original uniform setup from Work history.
2. Change Output sequences from 2 to 3, keeping the seed and both 301-base bounds unchanged.
3. Generate again. Confirm that the result list contains three successful records of 301 symbols, then export the FASTA.

Our three-record FASTA retained the first two sequences exactly and added random-dna-sequence_0000003, also 301 bases long. Comparing the exported bases confirmed this; matching row labels alone would not establish sequence identity.

Each output copy has its own deterministic stream. Keeping the same method, seed, and other parameters lets you extend a batch while preserving earlier copies. This does not enforce uniqueness: duplicate sequences are retained.

For variable-length test inputs, set different minimum and maximum lengths. Seqqio samples each record's length uniformly within that inclusive interval.

The count control supports up to 1,000,000 sequences, subject to these independent limits:

• 10,000,000 bases per sequence.
• 1,000,000,000 requested output symbols, calculated as maximum length times output count.
• A separate 4 GiB working-output budget that includes a conservative allowance for output artifacts.

Inspect the preflight result before scaling. One million 1,000-base records can exceed the working-output budget despite meeting the symbol limit. The four small runs documented here establish the demonstrated workflow; they are not a throughput or maximum-capacity benchmark.

Random DNA Sequence draws bases independently. Use it for declared baseline models, synthetic software inputs, and teaching exercises. Biological negative controls require task-specific validation: independent bases do not model genome organization, neighboring-base dependencies, or organism-specific codon use.

When your task changes, other Seqqio apps address different needs. Shuffle Sequence preserves the exact base counts and length of an existing sequence while reordering its symbols; it does not preserve dinucleotides, codons, or motifs. Random Coding DNA provides a coding-sequence model. Random DNA Regions provides protection settings for intervals in an existing sequence. Explore the broader catalog in the complete Seqqio tool guide.

For the related task of preparing synthetic proteins, the random protein sequence guide covers a separate web utility.

You now have DNA you can inspect, settings you can restore, and a batch you can extend. If these are recurring tasks, Seqqio brings them together with other sequence tools in one graphical workspace, with local execution and reusable run records.

The US$99 one-time purchase covers all 39 Seqqio applications. The package is a Windows 64-bit installer with no activation key. Using the desktop workflow requires no Python or Rust development environment.

Consider Seqqio when you prefer graphical controls and expect to use several of its sequence tools. If an existing documented script already handles your complete workflow comfortably, compare that experience with the record inspection, saved settings, and exports in this tutorial.

Explore Seqqio and the US$99 toolkit