Relationship Degree Kinship r Value Lookup Table (0.5, 0.25, 0.125)
Retrieve idealized outbred pedigree relationship coefficients, distinct from kinship coefficient phi=r/2. Bounded exact-key educational reference only; observations and applicability must be established independently.
Description
Retrieve idealized outbred pedigree relationship coefficients, distinct from kinship coefficient phi=r/2.
Pedigree relationship coefficients are model expectations, while realized genomic sharing can vary. A degree lookup gives a small reference without estimating an individual's relatedness.
When to use this tool
Retrieve idealized outbred pedigree relationship coefficients, distinct from kinship coefficient phi=r/2.
- Prepare the supplied key fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter key. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.reference. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Supply key exactly as one of "first-degree", "second-degree", "third-degree". Check for that own key in the fixed local table and return its stored reference text unchanged. An unsupported key is an input error, rather than a null result; there is no network request, fuzzy matching or dynamic text generation.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| key | Exact stored-entry key; spelling and case must match. | "first-degree", "second-degree", "third-degree" |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.reference | The unchanged stored text for the supported exact key; unsupported keys cause an input error. |
{
"input": {
"key": "first-degree"
},
"output": {
"result": {
"reference": "Expected pedigree relationship r=0.5 for ordinary parent-child or full siblings; not a realized genomic estimate."
}
}
}Limitations and assumptions
- Only the supported relationship-degree keys are accepted. The tool does not analyze DNA, reconstruct a pedigree or account for inbreeding, unusual pedigree structures or forensic evidence.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Keep model assumptions and phenotype-category order with each result. Ratio tolerance screens differ from goodness-of-fit inference, and sequence matches or likelihood products do not independently establish a biological mechanism or personal identity.
References
Similar or alternative tools
- GWAS Genome-Wide Significance Threshold 5e-8 Bonferroni Lookup
Retrieve the conventional GWAS threshold and its limits.
- abo genotype cross
A simplified ABO cross maps A and B alleles to codominant expression and O to the recessive phenotype.