eduKateSG · Why Science?
Index gapped genome-to-genome chains for regional browsing—while preserving query bounds, strand, chain score, link blocks and assembly identity
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 defines bigChain as an indexed bigBed representation of gapped pairwise chain alignments. A bigChain record stores the reference interval, item identity, display score, strand, target size, query identity and bounds, and the original chain score. A companion bigLink file stores the aligned blocks or links. UCSC documents conversion with chainToBigChain followed by separate bedToBigBed commands for the bigChain and bigLink outputs. Regional indexing improves access; it does not make coordinate transfer unique or biologically correct. 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; Net files and hierarchical genome alignments; bigBed indexed genome annotation tracks; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 12 October 2026: UCSC Genome Browser bigChain Track Format, checked 12 October 2026; UCSC Genome Browser Chain Format, checked 12 October 2026; UCSC Genome Browser bigBed 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 dated documentation, exact source data, coordinate rules and software versions.
A deeper reading route
A chain groups a sequence of aligned blocks into one scored pairwise relationship while allowing gaps in both sequences. bigChain reorganises that relationship for reference-coordinate indexing. The header-like record belongs in the bigChain file, while detailed aligned links belong in a companion bigLink file. Both objects are needed to reproduce a displayed chain faithfully, including its full block geometry and every declared gap.
The bigChain schema begins with reference chromosome, start and end, name, display score and strand. It then records target size, query name, query size, query start, query end and the original chain score. Similar labels can be confusing: chrom is the indexed reference coordinate, while qName and q bounds describe the other sequence.
The display score is constrained to the bigBed convention of zero to one thousand, whereas chainScore is a double preserving the alignment score from the source chain. Scaling a chain score into a display score can be useful for drawing, but it must not overwrite or be mistaken for the source metric.
The bigLink companion carries block intervals and a link value under its schema. UCSC’s workflow produces a pre-bigChain and pre-bigLink pair with chainToBigChain, then converts them independently. The relationship between those outputs should be treated as a set: mixing a link file from another conversion may render plausible but incorrect block structure.
Reference and query assemblies must be named with exact releases. Chromosome aliases, alternate loci and patch sequences can differ between manifests. A legal interval against one chrom.sizes file may be wrong for another release. Assembly identity belongs in filenames, track labels, manifests and methods, not only in analyst memory.
Strand handling is central. Query start and end are expressed under chain conventions, and minus-orientation chains require coordinate transformations when extracting query sequence or comparing another format. Validate known plus and minus chains by reconstructing block pairs rather than trusting their browser direction alone.
UCSC documents chainToBigChain followed by bedToBigBed using bed6+6 for the main schema and bed4+1 for the link schema. These declared shapes, schemas and chromosome sizes are construction inputs. Preserve executable versions and commands because software or schema changes can alter output without changing the visible file extension.
Like other bigBed formats, bigChain remains on a web-accessible server and only needed portions are transferred. Browser responsiveness therefore depends on indexing, URL stability and byte-range support. Test both main and link URLs, because a reachable bigChain with an inaccessible companion can leave a partial or misleading display.
Validation starts by comparing source chain counts and IDs with main records, then checking that link blocks reconstruct reference and query spans within the chain. Test gaps, chromosome edges, long chains, minus strand and duplicate scores. Extracted regional data should match prepared text exactly, including floating-point chain score.
Coordinate transfer through a chain is not necessarily unique. Duplications, rearrangements, repeats and assembly differences can yield competing chains or unmapped intervals. Net hierarchies can select and organise chains for some workflows, but that additional selection is not contained merely because the file is called bigChain.
For students, bigChain resembles an express route with a route card and a separate list of stops. The route card says where the journey begins and ends; the links reveal the aligned pieces between gaps. Fast lookup helps navigation, while evidence and route choice still need thoughtful checking.
A reproducible package contains source chain, both prepared tables, bigChain and bigLink schemas, chromosome sizes, commands, hashes, track configuration and block-reconstruction tests. This set allows another analyst to trace a lifted interval back through the indexed record and the original chain.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Group | Which gapped alignment belongs together? | Main bigChain interval, ID, bounds and chain score | A chain-level relationship |
| Link | Which aligned blocks form the chain? | Companion bigLink intervals and values | Detailed block geometry |
| Index | How is regional access produced? | chainToBigChain, autoSql, chrom.sizes and bedToBigBed | Two region-seekable binary objects |
| Judge | What can coordinate transfer support? | Competing chains, assembly identity and validation | A bounded mapping claim |
Inside this guide
1–12 · Foundations and design
13–24 · Models and estimation
- 13. Understand the link companion
- 14. Keep link identities stable
- 15. Validate block ordering
- 16. Validate gap arithmetic
- 17. Use chainToBigChain
- 18. Use the main autoSql schema
- 19. Use the link autoSql schema
- 20. Use exact chromosome sizes
- 21. Sort both prepared inputs
- 22. Convert both binary files
- 23. Host both files
- 24. Round-trip regional records
25–36 · Diagnostics and interpretation
- 25. Inspect competing chains
- 26. Protect unpublished assemblies
- 27. Separate mapping from biology
- 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 mapping note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with the genome-mapping task
bigChain serves gapped pairwise genome alignments by indexed reference region.
Working checkpoint — bigChain: Name both assembly releases and intended use. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 2 of 36
2. Separate source, main and links
The chain file is transformed into main bigChain records and companion bigLink blocks.
Working checkpoint — bigLink: Preserve all three layers. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 3 of 36
3. Read reference chromosome
chrom identifies the sequence on which the bigBed index is built.
Working checkpoint — chain alignment: Resolve it against the target manifest. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 4 of 36
4. Read reference bounds
chromStart and chromEnd enclose the chain on the indexed reference.
Working checkpoint — pairwise genome mapping: Check zero-based half-open geometry. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 5 of 36
5. Read chain identity
name should link the main record to its prepared blocks and source chain.
Working checkpoint — bigBed index: Verify uniqueness and stable joins. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 6 of 36
6. Read display score
score is a zero-to-one-thousand drawing value.
Working checkpoint — regional access: Do not substitute it for the chain score. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 7 of 36
7. Read strand
strand records pairwise orientation under the conversion schema.
Working checkpoint — bigChain: Test minus transformations explicitly. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 8 of 36
8. Read target size
tSize records the complete size of the indexed target sequence.
Working checkpoint — bigLink: Compare it with chrom.sizes. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 9 of 36
9. Read query name
qName identifies the other assembly sequence.
Working checkpoint — chain alignment: Resolve aliases against the query manifest. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 10 of 36
10. Read query size
qSize is the full query-sequence length.
Working checkpoint — pairwise genome mapping: Validate every query bound against it. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 11 of 36
11. Read query bounds
qStart and qEnd locate the covered query span.
Working checkpoint — bigBed index: Apply strand-aware extraction rules. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 12 of 36
12. Read original chain score
chainScore preserves the source alignment score as a double.
Working checkpoint — regional access: Keep scoring algorithm and parameters. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 13 of 36
13. Understand the link companion
bigLink stores detailed aligned blocks related to the main chain record.
Working checkpoint — bigChain: Treat the files as one versioned set. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 14 of 36
14. Keep link identities stable
Prepared links must join back to the correct chain ID.
Working checkpoint — bigLink: Reject orphan or cross-release links. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 15 of 36
15. Validate block ordering
Aligned blocks should progress consistently under chain orientation.
Working checkpoint — chain alignment: Detect overlaps and reversed joins. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 16 of 36
16. Validate gap arithmetic
Differences between adjacent blocks describe reference and query gaps.
Working checkpoint — pairwise genome mapping: Reconstruct both coordinate paths. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 17 of 36
17. Use chainToBigChain
The UCSC utility creates pre-bigChain and pre-bigLink tables from a chain file.
Working checkpoint — bigBed index: Archive utility version and source hash. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 18 of 36
18. Use the main autoSql schema
The documented main conversion uses bed6+6 and bigChain.as.
Working checkpoint — regional access: Hash the schema with the output. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 19 of 36
19. Use the link autoSql schema
The link conversion uses bed4+1 and bigLink.as.
Working checkpoint — bigChain: Validate it separately. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 20 of 36
20. Use exact chromosome sizes
The main and link reference intervals must fit one assembly manifest.
Working checkpoint — bigLink: Reject sequence-name drift. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 21 of 36
21. Sort both prepared inputs
Each pre-table must satisfy bigBed ordering requirements.
Working checkpoint — chain alignment: Use stable numeric sorts. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 22 of 36
22. Convert both binary files
Main and link files are built independently and must both succeed.
Working checkpoint — pairwise genome mapping: Record two commands and two hashes. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 23 of 36
23. Host both files
Track display depends on web-accessible main and link URLs with byte ranges.
Working checkpoint — bigBed index: Test each anonymously. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 24 of 36
24. Round-trip regional records
Extract main and link rows and compare them with prepared source.
Working checkpoint — regional access: Include plus, minus and gapped fixtures. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 25 of 36
25. Inspect competing chains
Repeated or rearranged sequence can create several possible mappings.
Working checkpoint — bigChain: Keep alternatives before claiming uniqueness. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 26 of 36
26. Protect unpublished assemblies
Draft genome alignments can be embargoed or sensitive.
Working checkpoint — bigLink: Apply governance to both files. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 27 of 36
27. Separate mapping from biology
A chain supports coordinate correspondence, not functional conservation or causality.
Working checkpoint — chain alignment: Add independent evidence for biological claims. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 28 of 36
28. Connect to Primary Science
A route card plus separate stop cards can model one gapped alignment chain.
Working checkpoint — pairwise genome mapping: Keep every skipped segment visible. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 29 of 36
29. Connect to Secondary Science
Chain mappings illustrate models, evidence and uncertainty across changing reference systems.
Working checkpoint — bigBed index: Separate coordinate transfer from mechanism. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 30 of 36
30. Connect to mathematics
Paired intervals, gaps, orientation and score scaling create precise quantitative work.
Working checkpoint — regional access: Reconstruct a short chain by hand. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 31 of 36
31. Connect to computing
Companion files, indexes and joins show why distributed data objects need shared versioning.
Working checkpoint — bigChain: Test mismatched main and link files. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 32 of 36
32. Connect to pathways
Genome alignment joins biology, algorithms, comparative genomics and data engineering and can illuminate STEM pathways.
Working checkpoint — bigLink: Verify current study routes separately. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 33 of 36
33. Did you know?
A bigChain track normally depends on a second indexed bigLink file for its aligned blocks.
Working checkpoint — chain alignment: Check both URLs and versions. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 34 of 36
34. Write a reader-ready mapping note
Name assemblies, chain source, schemas, converter versions, companion URLs and validation.
Working checkpoint — pairwise genome mapping: Keep it beside every lifted result. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 35 of 36
35. Build a validation ladder
Check main fields, links, joins, bounds, strands, gaps, sorting, conversion and extraction.
Working checkpoint — bigBed index: Stop at the first broken chain. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver source chain, prepared tables, schemas, manifests, commands, hashes and bounded interpretation.
Working checkpoint — regional access: Make every mapped block traceable to one chain. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Contents · Previous section · Continue to the Science Learning Hub