Why Science? | Wiggle Tracks and Continuous Genomic Signals

Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. The UCSC Wiggle format is a line-oriented ASCII representation for dense quantitative data plotted across a genome. It has two data layouts: variableStep supplies an explicit chromosome position beside each value, while fixedStep declares a start and constant step followed by a column of values. An optional span says how many bases a value covers. UCSC notes that Wiggle custom-track storage can introduce a minor precision loss on export and recommends bigWig for routine large-data storage. A graph that looks smooth is not automatically an accurate measurement, a complete experiment or a biological mechanism. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.

Related eduKate reading: BED and genomic feature coordinates; GFF3 genome feature annotations; BGZF and blocked compression for genomic data; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.

Primary and official sources checked on 12 October 2026: UCSC Genome Browser Wiggle Track ASCII Text Format, checked 12 October 2026; UCSC Genome Browser bedGraph Track Format, checked 12 October 2026; UCSC Genome Browser bigWig Track Format, checked 12 October 2026; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Specifications, tools and recommendations can change, so preserve the dated documentation, exact source data, coordinate rules and software versions used.

A deeper reading route

Wiggle turns a long list of measurements into a compact positional contract. The declaration supplies the coordinate pattern; the following values supply the signal. This is efficient only when reader and writer agree on assembly, chromosome label, start, step and span. A plausible curve can still be shifted to the wrong bases if any one of those pieces is wrong.

variableStep is designed for irregularly spaced observations. Each data line contains a chromosome position and a value, while the declaration selects the chromosome and can declare one span for the dataset. UCSC describes it as the more commonly used Wiggle layout, but also warns that sparse points can make it inefficient. The format choice should follow data geometry rather than habit.

fixedStep is compact when observations begin at a known position and repeat at one interval. After the declaration, values appear alone; their coordinates are calculated from start plus repeated step increments. This removes repeated coordinates from the text, but also means that one altered or missing value changes the implied relationship between line number and locus.

Step and span answer different questions. Step is the distance between successive value starts; span is the number of bases each value covers. They can be equal, smaller or larger depending on the data model, and confusing them can create hidden gaps or overlaps. A reader-ready description reports both explicitly and explains the aggregation window that produced each value.

UCSC says Wiggle positions must be in numerical order and unspecified positions have no data. No data is not automatically zero. Treating a missing locus as a measured zero changes summaries, plots and conclusions. Analysis should carry the missingness rule from the generating workflow into every derived table.

Display settings are not the measurement itself. Autoscaling, smoothing, graph type and windowing can change what a track looks like without changing stored values. A screenshot should therefore record the viewed region, scale, transformation and aggregation settings, and important claims should be checked against exported or programmatically queried values.

UCSC notes a precision consideration: uploaded Wiggle custom tracks are compressed into bins, and exported data can lose a small amount of precision. bedGraph is recommended when exact exported values matter, and bigWig is recommended for large remote datasets. That guidance makes format selection part of the scientific method, not a cosmetic file choice.

Conversion to bigWig removes track and browser lines and uses a chromosome-sizes file. The sizes file binds the signal to a particular coordinate space. A successful conversion does not prove that the sizes correspond to the intended reference assembly, so the manifest should name the assembly, source of chrom.sizes and hashes of all inputs.

Validation needs more than a parser success message. Compare record counts and value ranges, inspect first and last coordinates, query known boundary intervals, and compare source values with converted values under documented tolerances. Include negative values, gaps, non-unit steps and a final partial region in the fixture set.

For students, Wiggle is a vivid bridge between graph reading and data provenance. The curve is not the evidence by itself: each bar or shade comes from a value, a coordinate rule and a display choice. That same habit strengthens school science, data analysis and later STEM education.

A sound teaching example should also distinguish sampling interval from biological resolution. A signal reported every 100 bases may have been calculated from a 100-base window, a wider smoothing window or a completely different experimental footprint. fixedStep tells the reader how starts advance, and span tells the reader what coverage is declared, but neither proves the laboratory process resolved events at that scale. State the generating window, smoothing and instrument or algorithm limits so students do not mistake tidy coordinate spacing for direct observation at every base.

Cross-track comparison needs a common contract. Two Wiggle files may use the same assembly yet differ in bin width, normalisation, baseline, strand handling, missingness and replicate aggregation. Overlaying them without reconciliation can create attractive but meaningless differences. A comparison manifest should list each track’s sample set, units, transformation, start, step, span and excluded regions, then use matched regions and a common display scale. The strongest check exports values and compares them numerically rather than relying on visual resemblance.

Archiving should preserve a human-readable preview without making the preview authoritative. Keep the original text, exact hash, parser or converter version, chromosome-size source and a small table of known coordinate-value pairs. Those fixtures let a future reader test a migrated copy or rebuilt bigWig even if the original browser session is gone. This is the practical meaning of reproducibility: another person can reconstruct where each value belongs and why the displayed track looked the way it did.

A four-step claim ladder for this method

Stage	Question	Evidence	Responsible output
Declare	How are positions generated?	Chromosome, variableStep or fixedStep, start and step	A coordinate rule
Measure	What value covers which bases?	Ordered values and optional span	A quantitative genomic signal
Display	How is the signal summarised visually?	Scale, graph mode, smoothing and view window	A reproducible view
Verify	Did storage or conversion preserve meaning?	Assembly, counts, ranges, fixtures and tolerances	A trustworthy track