Skip to content

Main content

Lineage Sibling Order Tie Tool

Order supplied annotated sibling birth times under an explicit exact-tie policy.

Loading tool…

Description

Order lineage sibling IDs by birth times and an explicit tie policy.

Developmental stages and lineages can be represented by labels, ordered events and observation intervals. Index and time differences preserve a declared representation but do not discover lineage, assign stage or establish biological equivalence.

Order lineage sibling IDs by birth times and an explicit tie policy.

When to use this tool

Use Lineage Sibling Order Tie when checking an explicit stage, lineage or observation-coordinate convention.

How to use the tool and how it works

  1. Enter birthTimes, ids, tiePolicy. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read orderedIds, tied. Inspect tied before interpreting the associated values.

Order lineage sibling IDs by birth times and an explicit tie policy. Require aligned times and unique IDs; sort ascending time, resolving ties by input or reverse-input index; tied reports duplicate times.1

Input fieldMeaning and unitsAccepted input
birthTimesBirth TimesRequired. Array of finite number; maximum items 256.
idsIdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
tiePolicyTie PolicyRequired. Text; one of "input", "reverse-input"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
orderedIdsOrdered IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
tiedTiedRequired. Boolean.
json
{
  "input": {
    "birthTimes": [
      2,
      1,
      1
    ],
    "ids": [
      "a",
      "b",
      "c"
    ],
    "tiePolicy": "input"
  },
  "output": {
    "orderedIds": [
      "b",
      "c",
      "a"
    ],
    "tied": true
  }
}

Limitations and assumptions

  • Tie breaking is bookkeeping rather than biological ordering or lineage inference.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the original biological evidence and its staging or lineage model before drawing mechanistic conclusions.

References

  1. Calculation and input contract: developmental-biology/lineage-sibling-order-tie — tool.io

Similar or alternative tools