eduKateSG · Why Science?
Read a pairwise genome alignment in three lines—while keeping inclusive coordinates, strand, gaps, masking and scoring context visible
Choose the closest route, then return to the full index whenever you need the wider evidence chain.
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. UCSC documents AXT as a block-oriented pairwise alignment format produced from Blastz, with axtNet and axtChain outputs created by additional UCSC processing. Each block contains a nine-field summary line, one sequence line for the primary assembly and one for the aligning assembly, followed by a blank separator. Starts are one-based and ends are inclusive. A minus strand means that the aligning assembly coordinates are relative to the reverse-complemented chromosome. Sequence rows include inserted gap characters, and lower-case letters indicate repeats. An AXT block describes one algorithmic pairwise alignment; it does not prove orthology, conserved function, ancestry direction or uniqueness. 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: Chain files and genome coordinate mapping; MAF multiple genome alignments; 2bit compact reference genome sequences; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: UCSC Genome Browser AXT Alignment Format, checked 12 October 2026; UCSC Genome Browser Data File Formats FAQ, checked 12 October 2026; UCSC Genome Browser Chain 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
AXT is compact because each alignment block has only three content lines. The first line names two chromosomes, their interval bounds, the aligning strand and a score. The next two lines show aligned sequence strings. That apparent simplicity is useful, but it makes field order, coordinate convention and blank-line boundaries especially important: one shifted token changes the identity of everything that follows.
The primary and aligning assemblies do not play interchangeable roles. UCSC’s example describes human as the aligning assembly and mouse chromosome 19 as the primary assembly. The summary stores each chromosome and interval separately, so a report should name both assembly releases instead of saying only that two species were aligned.
AXT coordinates are one-based with inclusive ends, unlike the zero-based half-open intervals used by BED and many UCSC tables. A block from start 3001012 through end 3001075 spans 64 reference positions before alignment gaps are considered. Converting the same range to BED-like coordinates requires subtracting one from the start while retaining the numeric end.
The minus-strand rule applies to the aligning organism. When the strand field is minus, its start and end are relative to the reverse-complemented chromosome. A forward-coordinate conversion therefore needs the full chromosome size and a documented transformation. Guessing from the displayed sequence can silently place a block on the wrong interval.
Sequence rows have equal alignment-column length and can contain inserted gap characters. Their ungapped base counts should agree with the respective summary intervals. Lower-case letters mark repeats in the documented example, so changing case before inspection can remove information that explains ambiguous or repeated placements.
The final summary field is a Blastz score, and UCSC warns that different organism pairs can use different Blastz scoring matrices. Scores are therefore meaningful only with the pipeline and scoring context that produced them. They are not probabilities of homology, conservation or function and should not be compared blindly across releases or species pairs.
Validation reconstructs each block. Count nine summary fields; confirm two sequence rows of equal column length; remove gaps and compare ungapped lengths with inclusive coordinate spans; verify names against both assembly manifests; and test plus and minus fixtures. Then hash the source file and preserve the scoring README or pipeline configuration.
For students, AXT is an unusually clear demonstration that an alignment is a model with rules. Two strings can be placed side by side, yet a scientific reading still needs to ask where they came from, which direction they face, how gaps were introduced and what the score can honestly support.
Identity summaries should publish their denominator. The number of matching alignment columns, mismatching columns, gap columns and ungapped bases answer different questions. If a report excludes repeat-masked lower-case positions or gap-rich ends, say so explicitly and retain the raw counts. This prevents two pipelines from presenting different percentages under the same label and lets a reader recompute the chosen measure.
Block order also deserves testing. Alignment numbers should progress under the documented convention, yet scientific grouping should rely on chromosome, coordinates and producing pipeline rather than assuming that adjacent block numbers form one continuous biological feature. If blocks are resorted for indexing or display, preserve the original number and file order as provenance.
A visual comparison can support human review without replacing arithmetic. Display the two rows with coordinate labels, mark gaps and lower-case repeat segments, and show the strand transformation beside minus examples. Save the view as a review aid, while keeping field-level tests and sequence extraction as the authoritative check.
A durable archive should include small truth fixtures: a one-base plus block, a multi-gap block, a minus-strand block, a repeated lower-case segment and an intentionally malformed row. Re-run them whenever the parser, scoring pipeline or coordinate converter changes. These fixtures detect silent convention drift long before a whole-genome result looks suspicious.
A robust AXT validator should separate syntax, geometry and biological plausibility. Syntax checks count the summary fields and require the two sequence rows. Geometry checks compare ungapped target and query lengths with their declared inclusive intervals, applying the strand rule before interpreting the query. Plausibility checks can flag extreme gap runs or an unexpected species pairing, but they should not rewrite the evidence. Keeping these layers separate makes error reports useful: a malformed record is different from an unusual but valid alignment.
For reproducible reporting, preserve the source assembly identifiers, alignment release, chromosome naming convention, generation command and checksum of the exact AXT file. If the file is filtered, record whether filtering occurred by score, chromosome, interval or block identifier and count records before and after each step. A concise provenance table lets another learner or analyst tell whether a changed result reflects biology, a different assembly, or a transformation in the pipeline.
Sampling is useful only when the sampling frame is visible. Review blocks across chromosomes, score bands, strands, lengths, repeat content and gap density, then keep the random seed and selection code. A handful of convenient high-scoring blocks can make a parser appear correct while missing minus-strand or short-interval failures. Stratified review connects human inspection to the full dataset without pretending that a sample certifies every record.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Identify | Which two reference assemblies are compared? | Species, releases, chromosome names and sizes | A defined pairwise comparison |
| Locate | Where does each block lie? | One-based inclusive starts and ends plus strand | Two explicit coordinate intervals |
| Align | Which bases share alignment columns? | Two equal-length gapped sequence rows | A pairwise block model |
| Judge | What can the score and pattern support? | Scoring matrix, alternatives, repeats and validation | A qualified alignment statement |
Inside this guide
1–12 · Foundations and design
- 1. Start with a pairwise question
- 2. Recognise a block format
- 3. Know the documented origin
- 4. Keep primary and aligning roles distinct
- 5. Count nine summary fields
- 6. Read the alignment number
- 7. Read the primary chromosome
- 8. Read the primary start
- 9. Read the primary end
- 10. Read the aligning chromosome
- 11. Read the aligning start
- 12. Read the aligning end
13–24 · Models and estimation
- 13. Read strand precisely
- 14. Read the Blastz score
- 15. Read the primary sequence row
- 16. Read the aligning sequence row
- 17. Require equal column lengths
- 18. Interpret gap characters
- 19. Preserve lower-case repeats
- 20. Convert coordinates deliberately
- 21. Transform minus-strand bounds
- 22. Check ungapped spans
- 23. Separate score from probability
- 24. Inspect alternative blocks
25–36 · Diagnostics and interpretation
- 25. Connect AXT to chains
- 26. Connect AXT to nets
- 27. Protect sensitive sequences
- 28. Connect to Primary Science
- 29. Connect to Secondary Science
- 30. Connect to mathematics
- 31. Connect to computing
- 32. Connect to pathways
- 33. Did you know?
- 34. Write a reader-ready AXT note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with a pairwise question
An AXT file compares two defined assemblies under one alignment workflow. Similar species names can hide different releases.
Working checkpoint — AXT alignment: Name both providers, releases, sequence manifests and intended inference. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 2 of 36
2. Recognise a block format
Each AXT block has a summary line, two sequence lines and a blank separator.
Working checkpoint — pairwise genome alignment: Preserve record boundaries before parsing fields. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 3 of 36
3. Know the documented origin
UCSC describes AXT files as produced from Blastz, with axtNet and axtChain created by further utilities.
Working checkpoint — inclusive coordinates: Record the full producing pipeline rather than only the suffix. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 4 of 36
4. Keep primary and aligning roles distinct
The summary gives the primary assembly first and the aligning assembly second. Direction affects coordinates and reporting.
Working checkpoint — reverse strand: Label both roles in every table and diagram. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 5 of 36
5. Count nine summary fields
Alignment number, two chromosome names, four bounds, strand and score are required in order.
Working checkpoint — Blastz score: Reject a shifted or incomplete summary line. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 6 of 36
6. Read the alignment number
UCSC says numbering begins at zero and increments by one. It identifies block order, not a biological entity.
Working checkpoint — alignment block: Check sequence and uniqueness within the file. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 7 of 36
7. Read the primary chromosome
The second field names the chromosome or sequence in the primary assembly.
Working checkpoint — AXT alignment: Resolve it against the exact primary manifest. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 8 of 36
8. Read the primary start
The primary start is one-based, so the first base has position one.
Working checkpoint — pairwise genome alignment: Do not reuse it directly as a BED start. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 9 of 36
9. Read the primary end
The primary end is included in the interval.
Working checkpoint — inclusive coordinates: Compute span as end minus start plus one. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 10 of 36
10. Read the aligning chromosome
The fifth field names the sequence in the aligning assembly.
Working checkpoint — reverse strand: Resolve aliases before comparing chromosomes. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 11 of 36
11. Read the aligning start
Its interpretation depends on the aligning strand.
Working checkpoint — Blastz score: Keep raw coordinates and strand together. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 12 of 36
12. Read the aligning end
The end is inclusive and may be relative to a reverse-complemented chromosome.
Working checkpoint — alignment block: Validate it against chromosome size and strand. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 13 of 36
13. Read strand precisely
The strand belongs to the aligning organism; minus means reverse-complement coordinate values.
Working checkpoint — AXT alignment: Use documented reverse-coordinate arithmetic. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 14 of 36
14. Read the Blastz score
The score summarises the producing alignment under a scoring system that may differ by organism pair.
Working checkpoint — pairwise genome alignment: Preserve the scoring matrix or release README. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 15 of 36
15. Read the primary sequence row
Line two contains the primary sequence with inserted gap characters.
Working checkpoint — inclusive coordinates: Compare ungapped length with the primary span. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 16 of 36
16. Read the aligning sequence row
Line three contains the aligning sequence in alignment orientation.
Working checkpoint — reverse strand: Compare ungapped length with its interval. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 17 of 36
17. Require equal column lengths
The two sequence strings must occupy the same number of alignment columns.
Working checkpoint — Blastz score: Reject unequal rows before identity calculations. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 18 of 36
18. Interpret gap characters
A gap is part of the alignment model and changes columns without consuming a base on that row.
Working checkpoint — alignment block: Count gaps separately on each sequence. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 19 of 36
19. Preserve lower-case repeats
The documentation notes that repeats are shown with lower-case letters.
Working checkpoint — AXT alignment: State whether case was preserved or normalised. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 20 of 36
20. Convert coordinates deliberately
AXT one-based inclusive intervals convert to zero-based half-open by subtracting one from start, not from end.
Working checkpoint — pairwise genome alignment: Test a one-base and multi-base fixture. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 21 of 36
21. Transform minus-strand bounds
Forward coordinates require the aligning chromosome size and the stored reverse-complement interval.
Working checkpoint — inclusive coordinates: Keep both raw and transformed values. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 22 of 36
22. Check ungapped spans
Removing gaps from each row should yield base counts consistent with that row’s interval.
Working checkpoint — reverse strand: Stop on unexplained length differences. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 23 of 36
23. Separate score from probability
A larger score is not automatically a calibrated probability of orthology or function.
Working checkpoint — Blastz score: Describe the score only under its producing model. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 24 of 36
24. Inspect alternative blocks
Duplicated and repeated sequence can create several candidate alignments.
Working checkpoint — alignment block: Report retained alternatives and filtering policy. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 25 of 36
25. Connect AXT to chains
Chain processing links pairwise blocks into gapped paths with a different record structure.
Working checkpoint — AXT alignment: Do not treat AXT and chain as interchangeable files. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 26 of 36
26. Connect AXT to nets
Net processing organises selected chain fills and gaps hierarchically.
Working checkpoint — pairwise genome alignment: Keep each stage and its parameters traceable. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 27 of 36
27. Protect sensitive sequences
Reference comparisons are often public, but custom human or individual sequence data can be sensitive.
Working checkpoint — inclusive coordinates: Apply governance based on content, not extension. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 28 of 36
28. Connect to Primary Science
Two coloured symbol strips can model matched letters and gaps without real genomic data.
Working checkpoint — reverse strand: Ask which observations come directly from the strips. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 29 of 36
29. Connect to Secondary Science
Pairwise DNA comparison supports lessons on variation and evidence while leaving function as a separate claim.
Working checkpoint — Blastz score: Distinguish alignment from mechanism. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 30 of 36
30. Connect to mathematics
Inclusive intervals, orientation transforms and ratios make AXT a precise coordinate exercise.
Working checkpoint — alignment block: Calculate ungapped spans and identity by hand. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 31 of 36
31. Connect to computing
Stateful block parsing, ordered fields and validation show how text formats carry formal rules.
Working checkpoint — AXT alignment: Test truncation, extra blank lines and bad strands. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Section 32 of 36
32. Connect to pathways
Comparative genomics links biology, statistics, software and data stewardship and can illuminate STEM pathways.
Working checkpoint — pairwise genome alignment: Check current qualifications and roles separately. Read every block beside its two chromosome names, interval conventions, strand and aligned strings.
For future study, connect genetics to intervals and algorithms while checking pathways separately.
Section 33 of 36
33. Did you know?
AXT starts are one-based and ends are inclusive, unlike BED’s zero-based half-open coordinates.
Working checkpoint — inclusive coordinates: Demonstrate the conversion with one block. Preserve gaps, lower-case repeats and discarded candidates; they explain ambiguity.
For scientific writing, report roles, coordinates, strand, scoring and limits.
Section 34 of 36
34. Write a reader-ready AXT note
Name assemblies, roles, pipeline, score context, coordinate convention, masking and validation.
Working checkpoint — reverse strand: Keep it beside every derived chain or net file. Separate alignment geometry, sequence similarity, orthology, conservation and function.
For students, ask which letters share a column and what that does not yet prove.
Section 35 of 36
35. Build a validation ladder
Check blocks, nine fields, names, bounds, strand, row lengths, gaps, repeats, scores and alternatives.
Working checkpoint — Blastz score: Stop at the first unexplained inconsistency. Treat field order, coordinate basis, score model and reference identity as scientific inputs.
For parents, ask whether both assembly releases and score context are named.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver manifests, AXT hash, commands, scoring files, fixtures, summaries and bounded conclusions.
Working checkpoint — alignment block: Make every alignment column traceable to two references. Keep both assembly manifests, AXT hash, pipeline, scoring files and alternative blocks together.
For a classroom model, align invented symbols and avoid real personal sequence data.
Contents · Previous section · Continue to the Science Learning Hub