eduKateSG · Why Science?
Score ligand–receptor possibilities with an explicitly regularised expression rule and curated interaction database—without treating a ranked pair as a measured signal
Reading routes
Science learning becomes useful when a familiar object or observation is turned into a system of quantities, mechanisms and claim limits. This guide owns one applied evidence-reading job inside eduKateSG’s wider Science estate. It connects naturally to Why Science Natmi Cell Connectivity Expression Weight Specificity Evidence; Why Science Cellphonedb V5 Multimeric Complexes Cell Communication Evidence; Why Science Liana Plus Multi Method Consensus Cell Communication Evidence; Why Science Connectome Differential Cell Signalling Topology Evidence; Education Hub; Singapore Secondary School Directory; Career Adulthood Hub. It also keeps current school and public claims traceable to visible primary sources: SingleCellSignalR primary study; SingleCellSignalR PubMed record; SingleCellSignalR full-text record; Official SingleCellSignalR repository; Current Bioconductor package page; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science syllabus; 2026 MOE G2 Computing syllabus. The sources describe the scientific scope; this article translates that scope into a calm route for Primary Science, PSLE Science, Secondary Science, O-Level Science, STEM exploration, school choices and career pathways without inventing admission or employment outcomes.
SingleCellSignalR is an R and Bioconductor framework for inferring ligand–receptor interactions from single-cell expression data. Its 2020 Nucleic Acids Research paper introduced the curated LRdb resource and a regularised product score designed to cope with variable sequencing depth and dropout. Current Bioconductor documentation describes version 2 as supporting transcriptomic or proteomic inputs through both the original LR score and a BulkSignalR statistical model. A ranked interaction is therefore a model-based compatibility estimate whose meaning depends on the selected score, resource, preprocessing and biological replication.
Inside this guide
1–12 · Foundations and models
- 1. Start with a regularised ligand–receptor score
- 2. Understand LRdb as a scientific input
- 3. Know what the original score addresses
- 4. Distinguish current package scope
- 5. Build a network from inspectable pairs
- 6. Treat confidence assessment as calibration
- 7. Keep inference and visualisation separate
- 8. Create a specimen-aware analysis plan
- 9. Audit clusters and cell labels
- 10. Control sparsity without hiding it
- 11. Inspect normalisation and depth
- 12. Separate RNA and protein inputs
13–24 · Evidence, testing and applications
- 13. Freeze identifiers and eligible pairs
- 14. Archive software and score settings
- 15. Practise with an invented score audit table
- 16. Read ranks with component distributions
- 17. Use score thresholds as decisions
- 18. Compare cell-pair aggregates carefully
- 19. Preserve biological replicates in contrasts
- 20. Decompose apparent communication change
- 21. Add spatial and structural plausibility
- 22. Audit LRdb and alternative resources
- 23. Audit the selected score model
- 24. Compare with simple and multi-method baselines
25–36 · Learning, decisions and pathways
- 25. Validate an edge in molecular order
- 26. Publish false positives and nulls
- 27. Design a discrimination test
- 28. Write a bounded score statement
- 29. Build a classroom model before code
- 30. Begin with Primary Science habits
- 31. Use PSLE Science to practise claim limits
- 32. Connect Secondary and O-Level Science
- 33. Let Computing support the biology
- 34. Choose opportunities by verified fit
- 35. See connected career families
- 36. Finish with a bounded scientific claim
Section 1 of 36
1. Start with a regularised ligand–receptor score
SingleCellSignalR ranks a known ligand in one population with its receptor in another using expression evidence and a regularised scoring rule. Regularisation helps handle sparse single-cell measurements, but it does not convert missing counts into observed protein. The score is a prioritisation device whose calibration must be examined.
Section 2 of 36
2. Understand LRdb as a scientific input
The 2020 paper described LRdb as a curated collection of literature-derived ligand–receptor pairs. The resource defines which interactions are eligible before the sample is scored. Its species, curation scope, version and complex representation belong in methods and result tables.
Section 3 of 36
3. Know what the original score addresses
The original regularised product score was introduced to reduce sensitivity to variable sequencing depth and dropout. It combines source and receiver expression under a method-specific rule. A larger value does not equal binding affinity, secretion rate, receptor occupancy or signal flux.
Section 4 of 36
4. Distinguish current package scope
Current Bioconductor documentation describes SingleCellSignalR v2 as supporting transcriptomic or proteomic inputs and offering both the original LR score and a BulkSignalR statistical model. Record the package version, input modality and scoring option; a v1 paper and a v2 run are not interchangeable labels.
Section 5 of 36
5. Build a network from inspectable pairs
Cell populations become nodes and scored ligand–receptor possibilities become edges. Aggregate views help find prominent senders and receivers, but every edge should retain its ligand, receptor, specimen support and filtering history. A network summary without the pair ledger is too compressed to audit.
Section 6 of 36
6. Treat confidence assessment as calibration
The primary paper compared scoring schemes and investigated false-positive control. That evaluation informs method choice but does not certify every new dataset. Examine null behaviour, score distributions and positive or negative controls in the present experiment.
Section 7 of 36
7. Keep inference and visualisation separate
Heat maps, circle plots and networks communicate different summaries of the same scored table. State whether an edge width represents score, count or another aggregate. Visual prominence is not an additional source of evidence.
Section 8 of 36
8. Create a specimen-aware analysis plan
Record organism, tissue, condition, donor or animal, batch, assay, input modality, preprocessing, cell count and annotation method. Preserve specimen identifiers after integration. Many cells nested in one sample cannot substitute for biological replication.
Section 9 of 36
9. Audit clusters and cell labels
Ligand and receptor averages inherit every error in clustering and annotation. Check marker coherence, mixed states, doublets and uncertain reference assignments. Repeat key scores at a coarser label resolution to see whether the conclusion depends on a fragile subtype boundary.
Section 10 of 36
10. Control sparsity without hiding it
Dropout motivates regularisation, but sparse evidence remains uncertain. Show detection fractions, distributions and specimen prevalence alongside scores. A high rank created by one nonzero cell should not be reported like a broadly expressed interaction.
Section 11 of 36
11. Inspect normalisation and depth
The original paper discusses depth variation, while current workflows may use different preprocessing. Preserve raw counts and document transformations. Repeat key conclusions under one justified alternative so a normalisation choice does not silently own the result.
Section 12 of 36
12. Separate RNA and protein inputs
Transcriptomics and proteomics observe different molecular layers, with different missingness and scale. Do not pool their scores without a declared model. When both are available, use them as complementary checks and report disagreement rather than forcing concordance.
Section 13 of 36
13. Freeze identifiers and eligible pairs
Archive gene symbols, aliases, species mapping, LRdb version and any custom resource. Distinguish a pair absent from LRdb from a pair eligible but unsupported in the sample. These states have different interpretations and different repair routes.
Section 14 of 36
14. Archive software and score settings
Save the input object, metadata, label dictionary, score model, thresholds, resource, version, random seeds, long-format results and plots. Current package behaviour may differ from the original publication; reproducibility requires the actual environment, not only a citation.
Section 15 of 36
15. Practise with an invented score audit table
This fictional table teaches calibration; it is not SingleCellSignalR output.
| Pair | Regularised score | Source prevalence | Receiver prevalence | Specimens | First reading |
|---|---|---|---|---|---|
| Amber | 0.82 | 78% | 74% | 6/6 | stable lead |
| Birch | 0.79 | 8% | 80% | 2/6 | sparse source |
| Coral | 0.55 | 62% | 66% | 5/6 | moderate support |
| Delta | 0.48 | 71% | 69% | 0/6 controls | condition lead |
Section 16 of 36
16. Read ranks with component distributions
For each top pair, plot the ligand in sources and receptor in receivers, by specimen. Rank alone hides whether both components are moderate or one is dominant. Preserve zeros and uncertainty rather than showing only group means.
Section 17 of 36
17. Use score thresholds as decisions
A cutoff converts a continuous ranking into an edge list. Justify it with nulls, controls or validation capacity rather than visual convenience. Report a stable core and a threshold-sensitive margin so downstream readers know which nodes and edges are provisional.
Section 18 of 36
18. Compare cell-pair aggregates carefully
Summed scores and edge counts can favour large, transcriptionally active or well-annotated groups. Compare raw and normalised summaries, and remove ubiquitous high-degree molecules as a sensitivity check. A prominent node is not automatically a biological master regulator.
Section 19 of 36
19. Preserve biological replicates in contrasts
Estimate support within donors or animals before comparing conditions. Pooled cells can create precise-looking scores even when specimens disagree. Report prevalence, heterogeneity and uncertainty beside a condition-level network.
Section 20 of 36
20. Decompose apparent communication change
A score can change because ligand expression, receptor expression, cell abundance, label composition, depth or preprocessing changed. Show those components. The phrase ‘communication increased’ is stronger than a transcript-based score difference warrants.
Section 21 of 36
21. Add spatial and structural plausibility
Test whether source and receiver share an appropriate compartment and whether required receptor subunits or co-factors are present. Spatial proximity and complex completeness constrain a candidate, but neither alone proves activation.
Section 22 of 36
22. Audit LRdb and alternative resources
Repeat headline pairs with a high-confidence subset or another curated resource mapped to the same genes. Track pairs lost by resource definition separately from pairs retained but re-ranked. Resource robustness is part of confidence.
Section 23 of 36
23. Audit the selected score model
Where the current package offers more than one model, compare them under a written plan. Differences may reflect how low counts, variance and sample structure are treated. Do not average incompatible scores merely to produce consensus.
Section 24 of 36
24. Compare with simple and multi-method baselines
Use a simple expression product and another ligand–receptor tool with identical inputs. SingleCellSignalR adds value when its calibrated score produces a stable, experimentally useful shortlist. Multi-method agreement is not independent validation because methods share data and priors.
Section 25 of 36
25. Validate an edge in molecular order
Measure source ligand protein, receiver receptor or complex, proximity, a receptor-proximal event and a downstream response. Perturb the ligand or receptor and include rescue where feasible. Each step closes a different inferential gap.
Section 26 of 36
26. Publish false positives and nulls
Show high-scoring pairs that fail protein or spatial checks, known routes not recovered and edges unstable across specimens. Calibration examples reveal how the score behaves in the present tissue and prevent selective reporting.
Section 27 of 36
27. Design a discrimination test
Choose two leading pairs that predict different early receiver events. Pre-register measurements and time points that would favour one, the other or neither. This uses a ranked network to sharpen experiments rather than decorate an already chosen mechanism.
Section 28 of 36
28. Write a bounded score statement
Prefer: ‘SingleCellSignalR prioritised an LRdb-supported pair with a reproducible regularised score and independent protein or spatial support.’ Avoid calling the score a direct measure of signalling strength unless that quantity was experimentally calibrated.
Section 29 of 36
29. Build a classroom model before code
Give students the same sparse table and two scoring rules, then ask why the rankings change and which validation would reveal a false positive. Label observations, transformations, assumptions and conclusions separately. The aim is to make every evidence hand-off visible enough for another student to question.
Section 30 of 36
30. Begin with Primary Science habits
Primary Science already supplies useful foundations for SingleCellSignalR: careful observation, fair comparison, consistent records and conclusions that fit the evidence. A simple investigation can show why compatible parts create a possibility without proving that an interaction occurred.
Section 31 of 36
31. Use PSLE Science to practise claim limits
PSLE Science trains students to connect evidence to process without jumping beyond an experiment. With SingleCellSignalR, ask what was measured, what came from a database, what the algorithm calculated and which new observation could distinguish competing explanations.
Section 32 of 36
32. Connect Secondary and O-Level Science
Secondary Science and O-Level Biology develop ideas about cells, organisation, transport, experimental design and evaluation. SingleCellSignalR turns those ideas into a modern data problem. The valuable lesson is disciplined interpretation, not memorising a software menu.
Section 33 of 36
33. Let Computing support the biology
Computing contributes data structures, scoring, graphs, algorithms, version control and reproducibility. Biology supplies specimens, mechanisms and validation. SingleCellSignalR shows why correct code is necessary but insufficient: a perfect program can still analyse confounded samples or uncertain labels.
Section 34 of 36
34. Choose opportunities by verified fit
For school choices and science enrichment, verify current programmes on official school and MOE pages. Look for opportunities that teach data sparsity, model calibration and laboratory validation as one chain. A fashionable mention of genomics, AI or bioinformatics does not guarantee sustained teaching, admission, mentorship or a particular career outcome.
Section 35 of 36
35. See connected career families
The reasoning in SingleCellSignalR appears in computational biology, biostatistics, network science, proteomics, genomics and translational research. Routes may pass through polytechnic, junior college, university or continuing education, with different blends of biology, statistics, computing and communication. Requirements change, so check the responsible institution directly.
Section 36 of 36
36. Finish with a bounded scientific claim
A defensible conclusion states exactly what SingleCellSignalR prioritised under which data, resource, settings and specimens. SingleCellSignalR calculates resource- and model-dependent ligand–receptor scores; it does not directly observe molecular transfer or causation. Report uncertainty, sensitivity, replication, negative results and independent validation together; those boundaries make the conclusion more useful.
SingleCellSignalR is easiest to interpret when every score remains attached to its inputs. For a leading pair, publish ligand and receptor distributions, detection fractions, cell counts, specimen prevalence and the LRdb record beside the regularised score. The score is a ranking device under a model; the adjacent columns reveal whether it represents broad moderate support or one component rescued from extreme sparsity.
Regularisation addresses unstable estimates but does not create missing biology. A model can stabilise a low-count product without proving that a protein was made, secreted or bound. Label pairs with sparse source, sparse receiver or both, then test whether rankings persist under a prespecified prevalence rule. This preserves the value of the model while making the evidentiary gap visible.
Did you know? A higher ligand–receptor score need not mean more signalling molecules crossed between cells. The value depends on expression, preprocessing, resource membership and the selected score model. Treat the units as computational unless calibrated against an assay that measures the relevant molecular process. Even then, calibration may be tissue- and protocol-specific.
Sequencing depth can change zeros and low counts. Record library size distributions by specimen and cell type, document normalisation and compare one biologically defensible alternative. If the headline edge changes rank only in the shallowest samples, describe it as depth-sensitive. Removing those samples without an a priori quality rule risks selecting the answer.
Current package documentation and the original publication should be distinguished. The package may add modalities or score options after the paper, while the paper documents the original validation. Record version, selected function and model; cite the source that actually supports each statement. A current feature should not be retroactively attributed to the 2020 study.
LRdb is an eligibility resource, not a measurement from the specimen. Freeze its release and any custom additions. An interaction that appears after a database update reflects knowledge expansion unless the biological input also changed. For longitudinal comparisons, use one resource snapshot or explicitly separate the resource effect from the sample effect.
Cell labels determine every sender–receiver aggregate. Audit doublets, transitional states and uncertain reference mappings, then repeat important results at a coarser hierarchy. A pair stable across fine and broad labels is easier to trust. A pair that depends on one fragile subtype can remain a useful discovery lead if that dependence is clearly reported.
Network totals can reward populous or transcriptionally active groups. Show the number of cells, the number of eligible pairs and normalised as well as raw summaries. Remove ubiquitous high-degree ligands or receptors in a sensitivity run. Centrality is a property of the constructed network, not an intrinsic title carried by a cell type.
Condition contrasts require biological replication. Calculate or summarise pair evidence within donors or animals before comparing groups, and keep the same cell-type universe when possible. Missing populations should be marked structurally absent, not converted to zeros without explanation. A pooled network can conceal substantial donor disagreement.
If both transcriptomic and proteomic inputs are used, preserve their layers. RNA abundance, surface-protein measurement and secreted-protein measurement have different noise and biological meanings. Report modality-specific support and discordance. A composite that averages them without a model can erase the very disagreements that would guide validation.
Complex receptors deserve explicit completeness rules even when the resource represents them compactly. State which subunits are required, how aliases are mapped and what minimum evidence each must meet. A pair with one strong chain and one absent chain should be flagged as complex-limited rather than allowed to inherit the strong component’s confidence.
Spatial evidence can reject some high-scoring possibilities. Test whether cells occupy compatible compartments and whether the mediator’s expected range fits their separation. Contact opportunity supports a membrane-bound route, while physical separation challenges it. Neither proximity nor distance alone establishes transcriptional direction or causal response.
Use nulls that preserve data structure. Permute labels or conditions within suitable specimen strata, compare incompatible compartments and examine resource-supported pairs whose proteins are known to be absent in the current tissue. Nulls should answer a declared question; randomising individual cells across donors can destroy real dependence and generate false precision.
Benchmark against a simple complete-pair expression rule and another method using the same resource. The regularised score adds practical value if it produces a stable shortlist with better independent validation, especially among sparse candidates. A larger or more elaborate network is not automatically better calibrated.
Follow validation in molecular order: ligand protein, full receptor, proximity, early pathway event, later target programme and phenotype. Include blockade and, where possible, rescue. Time matters because a downstream programme observed before the proposed source appears cannot be caused by that newly proposed route.
Archive exact inputs, preprocessing, LRdb snapshot, package version, score choice, thresholds, label map, specimen-level results and validation ledger. Store raw continuous scores before any graph cutoff. This lets later readers separate a model update, database update and biological replication from one another.
A bounded result states that SingleCellSignalR prioritised an LRdb-supported pair with a reproducible regularised score and specified orthogonal support. It does not call the score a direct measurement of communication strength. That phrasing is more informative because it names both the achievement and the unobserved molecular steps.
Contents · Previous section · Continue to the Science Learning Hub
