eduKateSG · Why Science?
An image can illustrate a cell type without becoming the definition of the whole class
Choose the closest question, or read the guide from the beginning. Each chapter keeps its explanation, example and next step visible.
A colourful image of a fruit-fly neuron can make a complex subject feel wonderfully approachable. The next useful question is less obvious: does the image show one observed neuron, a named cell type or an anatomical region used to organise many observations? The Drosophila Anatomy Ontology, commonly identified by the prefix FBbt, helps keep those meanings distinct. Science learning turns an attractive picture into evidence we can explain.
The OBO Foundry identifies FBbt as an anatomy ontology for Drosophila melanogaster and documents its use by FlyBase for expression and phenotype records and Virtual Fly Brain for brain-image annotation. Virtual Fly Brain's current cell-type documentation distinguishes a class from an individual reconstructed or imaged neuron. Its registration guide, dated 18 August 2026, explains why images are aligned to common templates and why that alignment still has limits.
This article owns the bridge between anatomy vocabulary and image interpretation, not a complete connectomics course. The related eduKate pages on Uberon, biological position and term lookup support other questions. Every image card, local cell label, count and comparison in our worked cases is fictional. They are not actual FBbt terms or reported FlyBase results, and the activities use drawings and documentation rather than animal handling or specialist imaging procedures.
Follow the connected evidence: Uberon and Cross-species Anatomy; Biological Spatial Ontology; Ontology Lookup Service. For education and school-choice guidance, use the Education Hub; for possible work directions, continue to Careers by Subject Capability. These routes are separate from the specialist topic here.
| Layer | Question | Record | Boundary |
|---|---|---|---|
| Class | Which kind of neuron or structure? | Reviewed FBbt term and definition | Not one pictured individual |
| Individual | Which reconstructed or imaged object? | Source dataset and object identifier | Not every member of the class |
| Position | Which coordinate space? | Template and transformation context | Not raw coordinates from another image |
| Connection | What evidence supports a relation? | Observed relation and method | Not apparent overlap alone |
Inside this guide
Chapters 1–8 · Meaning and evidence
- 1. Did You Know? A type and its pictured example are different objects
- 2. FBbt names anatomy while the image record preserves evidence
- 3. A definition needs evidence beyond visual resemblance
- 4. Similar names and aliases need identifier checks
- 5. Anatomical regions and neuron types answer different queries
- 6. Coordinates need a named image space
- 7. Registration helps comparison without making images identical
- 8. Apparent overlap does not establish a synaptic connection
Chapters 9–16 · Comparison and learning
- 9. A reconstruction has its own completeness and provenance
- 10. Count individuals, classes and images separately
- 11. An annotation does not settle functional behaviour
- 12. Compare datasets at a supported level of meaning
- 13. Review the term and dataset histories separately
- 14. A drawing workshop on class, individual and template
- 15. Questions readers often ask about anatomy images
- 16. Finish with an image-to-meaning evidence packet
CHAPTER 1 OF 16 · Read anatomy and cell identity
1. Did You Know? A type and its pictured example are different objects
Virtual Fly Brain describes a cell type as a class and an individual reconstructed or imaged neuron as an instance. Source: VFB cell-type documentation. This is a compact distinction with a large practical effect. A class organises meaning across examples; an individual carries particular observations. Keeping both identifiers visible stops one image from becoming a claim about every member of a type.
Imagine a fictional local class called Type A with three image cards. Each card belongs to a different specimen and has a distinct source identifier. The shared type label helps find them together. Their measurements, reconstruction completeness and source methods can still differ. An annotation to Type A does not make the three images copies of one individual or identical evidence.
Students can practise with a category such as triangular paper shapes and three actual cut-outs. The category is not one cut-out, and one cut-out's dimensions do not define all triangles. This analogy is a learning tool rather than a biological claim. It gives learners a clear sentence to use when reading scientific images: “This is an observed example annotated to this class, supported by this source.”
CHAPTER 2 OF 16 · Read anatomy and cell identity
2. FBbt names anatomy while the image record preserves evidence
An anatomy term helps describe a structure or cell category. The image record identifies the evidence source and its particular object. Do not store only the category label when the task requires an individual image, specimen or reconstruction. A recommended record keeps annotation and evidence references side by side, with the reason for the classification when it matters.
For a fictional dataset, Image One and Image Two both carry Type A. Image One is a complete local drawing; Image Two shows only a selected portion. The shared annotation may be useful, but a comparison of total extent would need to account for their different coverage. The vocabulary does not repair the incomplete image automatically or reveal the unseen parts.
Write the record's job before reading it. Is it describing a class, cataloguing an individual, locating a signal or measuring a feature? Those tasks need different fields. Students can create two versions of the same card: a class definition and an image evidence record. Comparing the cards makes the distinction visible and helps them see why controlled terminology should organise observations without replacing the original source details that make those observations checkable.
CHAPTER 3 OF 16 · Read anatomy and cell identity
3. A definition needs evidence beyond visual resemblance
VFB's documentation explains that its ontology cell types are defined through properties and referenced evidence, not merely a picture or a name. Source: VFB cell-type documentation. A visually similar example can be a useful candidate for review, but resemblance alone should not be presented as a completed classification decision. Inspect the definition and the information available for the individual.
Suppose a fictional local definition requires two features. Image One shows both, while Image Two shows only one because the relevant region is missing. Image Two may be compatible with the class, yet it lacks evidence for a confirmed assignment under the exercise's rule. Preserve that uncertainty rather than calling the missing feature present because the overall shape looks familiar.
A recommended annotation note states the features checked, source references and unresolved distinctions. Keep candidate classes separate from accepted classes if the review is incomplete. This is useful scientific reading: the learner moves from “it looks like” to “these observations support this definition”. A careful uncertain result can still help discovery, as long as later readers can see that it is a candidate rather than a confirmed statement about anatomy.
CHAPTER 4 OF 16 · Read anatomy and cell identity
4. Similar names and aliases need identifier checks
The OBO Foundry specifies the mixed-case identifier prefix FBbt. Source: OBO Foundry FBbt overview. Use the actual supplied identifier and preserve its case when recording a term. Display labels and synonyms help readers find concepts, but they should not be used as the only keys in a dataset that needs unambiguous reference.
In a fictional catalogue, two source groups use different names for a similar-looking local type. The first task is to inspect their definitions and identifiers, not to merge records because one name appears in the other's notes. A shared alias may help discovery. It does not establish that the sources classified their objects at the same level or with the same evidence.
Keep source wording alongside the accepted ontology identifier and review rationale. Check copying errors separately from meaning errors: a correct-looking label paired with the wrong identifier is still a problem. Students can simulate the challenge using local cards with overlapping names and distinct definitions. The activity teaches why a stable reference and clear meaning work together, making a scientific record easier to search without allowing search convenience to decide its interpretation.
CHAPTER 5 OF 16 · Inspect images and registration
5. Anatomical regions and neuron types answer different queries
A region annotation describes an anatomical place; a cell-type annotation describes a kind of cell. A particular neuron can have relationships to several regions, but those relationships should remain explicit. Do not treat the name of a region as if it were automatically the name of every cell associated with it. The query's wording should reveal which layer it targets.
Our fictional system has Region R and local Type A. One individual of Type A has a marked feature in R. A query for all Type A examples and a query for all objects with that feature in R may return different sets. Neither result is wrong if its definition is clear. The problem arises when the two questions are compressed into an unexplained “region neurons” category.
Recommended query records include the target entity, relationship and scope. Preserve each returned object's original annotation and source. Students can draw a map with objects partly crossing two zones, then define a query for object type and another for zone overlap. This safe exercise makes the distinction visible and prepares learners to read anatomy data as connected descriptions rather than a collection of labels assumed to mean the same thing.
CHAPTER 6 OF 16 · Inspect images and registration
6. Coordinates need a named image space
A coordinate identifies a position within a specified system. The same numerical coordinates in two images need not identify the same anatomical place. VFB's registration guide explains how image alignment maps samples to common templates. Source: VFB registration documentation. That makes template and transformation context essential when positions are compared across datasets.
Use a fictional paper drawing with a point at coordinate 4, 6. Enlarge the drawing or rotate its axes, and the corresponding object no longer sits at the same numerical coordinate. The point's anatomical identity and its coordinate representation are different layers. A comparison must state the coordinate frame rather than assuming the numbers carry their own location meaning.
Recommended position fields include dataset, image identifier, coordinate system, units or scale, template and any transformation used. Keep original coordinates alongside transformed ones when appropriate. Students can work through a simple translation on squared paper, recording both before and after positions. The exercise teaches a mathematical move while protecting the scientific distinction: changing the representation can help comparison, but it does not make the source image and the target template the same observed specimen.
CHAPTER 7 OF 16 · Inspect images and registration
7. Registration helps comparison without making images identical
Registration aligns images for comparison. VFB's guide also explains that registered positions remain estimates and that alignment accuracy has limits. Source: VFB registration guide. Treat the transformed image as a useful representation of source evidence, not a replacement that removes all uncertainty. The template supports a common frame, while the individual remains a distinct specimen record.
For a fictional demonstration, align two drawings using three landmarks. The landmarks may coincide while a small feature between them remains slightly displaced. A neat overlay can therefore conceal local mismatch. Record which transformation was used and inspect the features important to the question. Do not claim exact correspondence simply because the broad outlines appear well aligned.
Keep original image references, template identity and relevant quality notes with the transformed view. A student can compare alignment using large landmarks and then inspect a small feature, learning why the task's scale matters. This is an editorial activity, not a software tutorial or a claim about a particular registration algorithm's accuracy. The positive outcome is a comparison whose uncertainty is visible enough for another learner to judge whether it supports the intended question.
CHAPTER 8 OF 16 · Inspect images and registration
8. Apparent overlap does not establish a synaptic connection
VFB's registration documentation cautions that overlap in common template space is not evidence of a synapse. Source: VFB registration guide. An overlay can suggest where to investigate, but a connection claim requires appropriate evidence of the relationship itself. Keep discovery, anatomical proximity and demonstrated connectivity separate in the report.
In an invented drawing exercise, two coloured paths overlap on a flat page. They could cross without connecting, share a projected position at different depths or actually join at a defined point. The picture alone needs a legend or other evidence to distinguish those possibilities. A diagram can be informative and still leave the connection unresolved.
Ask learners to write three levels of statement: overlap is visible in this representation; a possible relationship is worth reviewing; the stated evidence supports a specified connection. They should identify what changes between the levels. This gives scientific language a useful ladder without treating every image as a finished conclusion. The activity does not diagnose a neural circuit or reproduce an actual VFB result; it teaches the evidence boundary that makes anatomical imagery safer to interpret.
CHAPTER 9 OF 16 · Review counts and connections
9. A reconstruction has its own completeness and provenance
A reconstructed object should retain its source dataset, identifier and relevant completeness information. A type annotation does not establish that every part was reconstructed, and an attractive rendering can make missing material difficult to notice. A recommended review asks what evidence was included, which boundaries were examined and which details remain unavailable.
Our fictional Individual A has a complete local path drawing, while Individual B has a truncated path. Comparing their total drawn lengths without accounting for truncation would confuse missing evidence with a shorter object. The difference may concern representation coverage rather than a biological feature. Preserve the status so the later calculation does not silently make that interpretive choice.
Students can create a full drawing and an intentionally cropped copy, then list which comparisons remain meaningful. Position of a visible landmark may still be assessable; total extent may not be. This makes limitations constructive. The source record can remain useful for a narrower question even when it cannot support a broader one. Clear provenance and completeness notes help another reader choose that question without mistaking the visual polish of a rendering for complete evidence.
CHAPTER 10 OF 16 · Review counts and connections
10. Count individuals, classes and images separately
A database can contain several images of one individual and many individuals annotated to one class. The number of image files is not automatically the number of observed cells, and the number of classes is not a specimen count. Define the counting unit before making a chart or reporting a summary. Keep identifiers that make deduplication possible.
Suppose a fictional catalogue contains six image cards: three views of Individual A, two of Individual B and one of Individual C. There are six images and three individuals. If all are annotated to Type A, there is one represented type in this local set. These numbers answer different questions. Calling every image a different neuron would double-count the observed objects.
Make the arithmetic visible by grouping cards around their individual identifiers. Then group the same individuals by type. Students can see how the totals change without any new observation being added. This is a practical connection between Biology and computing: the data model determines which objects can be counted honestly. A correct count begins with a clear entity definition, not with whatever row total a spreadsheet displays at the bottom.
CHAPTER 11 OF 16 · Review counts and connections
11. An annotation does not settle functional behaviour
An anatomical category helps organise a cell or structure. A claim about behaviour, activity or causal function requires its own evidence. Keep those interpretations distinct from image-derived shape and location. Even a carefully reviewed type assignment should not be treated as proof that the pictured individual performed every function associated with related literature in the particular context examined.
For a fictional record, an individual is annotated to Type A and a visible feature lies in Region R. A separate note proposes a role in Task T. The annotation and location provide context, but the task claim needs evidence beyond the category label. The report should distinguish documented background, direct observation and the hypothesis being considered.
Students can practise by writing an image caption and a hypothesis sentence separately. The caption states what the source image and annotation support; the hypothesis states what they would like to test. This keeps curiosity lively without overstating the result. Scientific learning is not only about collecting facts. It is also about knowing which kind of evidence would move an interesting idea from a plausible explanation to a supported conclusion.
CHAPTER 12 OF 16 · Review counts and connections
12. Compare datasets at a supported level of meaning
A shared FBbt class can connect examples across datasets, but the datasets may use different methods, image spaces, coverage or review standards. Treat a shared annotation as one part of a comparison. Inspect the underlying individual records and define the measurement or relationship being compared. A category match does not create complete methodological equivalence.
Imagine two fictional collections each containing Type A individuals. One stores original image coordinates; the other stores transformed template coordinates. A position comparison requires an appropriate common frame. A count comparison requires clear individual identifiers and selection rules. A morphology comparison requires suitable completeness and measurement definitions. The same class label supports discovery while each analysis retains its own requirements.
Write a comparison note that identifies the accepted alignment and the remaining limitations. Use the eduKate Uberon and Biological Spatial Ontology guides for broader anatomical and reference-frame questions, but preserve the fly-specific source evidence. A learner can make progress without resolving every technical difference: one clear statement about what is comparable, what is not yet comparable and which evidence would help is already a useful scientific product.
CHAPTER 13 OF 16 · Make evidence easier to explain
13. Review the term and dataset histories separately
A cell-type definition and an image dataset can change independently. A revised term may alter classification, while a corrected reconstruction may alter the observed geometry. Recommended records preserve ontology and dataset versions, review dates and material changes. Do not describe a changed image as if it were merely a renamed term, or a revised definition as if new biological material had been observed.
The FlyBase ontology repository supplies the project route for current files and issue tracking. Source: official FBbt repository. For a specific annotation, inspect the release used and its supporting definitions. This guide does not claim a current total of neuron classes or a fixed update interval. Historical publication statistics should remain dated when they are used elsewhere.
For a fictional correction, keep both the earlier and revised annotation with a reason. State whether the revision came from additional source evidence, a clearer definition or a repaired identifier. If a downstream count changes, identify which record changed and why. This makes scientific maintenance a visible part of the learning story: improvement is valuable when readers can trace how the evidence and interpretation developed.
CHAPTER 14 OF 16 · Make evidence easier to explain
14. A drawing workshop on class, individual and template
Create three fictional path drawings and a local class definition with two required features. Give each drawing a distinct individual identifier. Ask learners to decide which examples meet the definition and which need more evidence. Then align the drawings to a shared squared-paper template, preserving the original sheets and transformation notes.
Primary Science and PSLE Science learners can focus on category versus example and clear observation language. Secondary Science and Mathematics learners can inspect translations, scaling and counting units. Computing learners can design a record that links classes, individuals and images without conflating them. The workshop is an editorial suggestion and does not reproduce a professional fly-brain analysis or require children to work with animals.
Finish with two captions: one for the class definition and one for a particular image. Each should state the right kind of object. Add a note about what the template overlay can show and which connection remains unresolved. This creates a practical, optimistic learning outcome: a picture becomes easier to understand because its labels, evidence and limits are visible, not because it has been given more complicated terminology.
CHAPTER 15 OF 16 · Make evidence easier to explain
15. Questions readers often ask about anatomy images
Does one image represent an entire cell type? It can illustrate an annotated individual, but the class definition is a separate object. Does a matching type label make every measurement comparable? The source methods, completeness and measurement definitions still need review. Are two overlapping shapes connected? A specified connection requires evidence beyond visual overlap in a common representation.
What should I keep when downloading or recording an example? Preserve the legitimate source link, dataset and individual identifiers, annotation and relevant version or image-space context. Check reuse terms before copying source imagery; this guide links to project documentation rather than claiming rights to redistribute all images. What if the type assignment is uncertain? Keep candidate status and explain the missing distinction instead of forcing a precise label.
Where can a learner continue? The Science Learning Hub connects observation and data literacy with broader study; the Education Hub supports study planning and school-choice exploration; the careers-by-subject page offers capability-based reflection. These pages help learners see possible next steps without presenting this exercise as a qualification, admission requirement or career guarantee. The immediate goal is a caption or record whose scientific meaning another person can inspect.
CHAPTER 16 OF 16 · Make evidence easier to explain
16. Finish with an image-to-meaning evidence packet
Select one fictional image and prepare a record with individual identity, class annotation, source evidence, anatomical relationships, coordinate frame and completeness. State which features support the annotation and which interpretation remains a hypothesis. If a transformed image is used, retain the original reference and the relevant template information. The packet should help a partner understand the picture without relying on private explanation.
Challenge the record with a second view of the same individual. Can the partner recognise that it is not a new specimen? Then challenge it with another individual of the same class. Can they see why its measurements are separate? These checks expose the distinction between identity, category and representation in a small, manageable exercise.
Why Science? Because it lets us enjoy a remarkable image while understanding what it can actually show. FBbt offers a structured language for fly anatomy, and VFB documentation helps explain the bridge from classes to individual images. Careful reasoning keeps annotation, position and connection evidence distinct. Start with one clear image caption, one traceable source and one honest uncertainty, and a complex picture becomes a useful learning opportunity.
Back to contents · Previous chapter · Continue to the Science Learning Hub
Sources and scope
Official and primary sources checked on 15 October 2026: OBO Foundry: Drosophila gross anatomy; FlyBase: official anatomy ontology repository; Virtual Fly Brain: cell types; Virtual Fly Brain: image registration, dated 18 August 2026. Project descriptions above are attributed to their named sources. Worked datasets are fictional; record designs, review checklists and teaching activities are editorial recommendations, not official ontology requirements. No search-volume, clinical, admission or career-outcome claim is made.