Green/Dry Bone Fracture Velocity Classifier

Independently measured fracture speed/morphology/moisture evidence against caller experimental green/dry classes, not postmortem interval. Independently declared positive evidence requirements; overlaps and unknowns retained. Caller independently establishes sample/context/calibration applicability; not definitive chronology, provenance, taxonomy, disease or human identity.

Description

Fracture-state interpretation depends on independently observed features and a rule set.

Fracture-state interpretation depends on independently observed features and a rule set.^[1]

A supplied evidence classification does not measure fracture velocity or establish a universal fresh-versus-dry verdict. Use Green/Dry Bone Fracture Velocity Classifier to evaluate the supplied inputs under the model explained below.

When to use Green/Dry Bone Fracture Velocity Classifier

Use Green/Dry Bone Fracture Velocity Classifier to evaluate the supplied inputs under the model explained below. Define the candidate classes and their positive-evidence requirements, then distinguish evidence presence from whether it is known.

How to use Green/Dry Bone Fracture Velocity Classifier and understand its results

Define the candidate classes and their positive-evidence requirements, then distinguish evidence presence from whether it is known.
Enter Caller bone fracture state class ids, Caller bone fracture state requirements, Observed bone fracture state evidence, Known bone fracture state flags using the field table and validation rules below, then run the tool.
Read Compatible caller classes, Fully witnessed caller classes; interpret the units, signs, ordering and unknown-value placeholders described below.
Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.

Input field	Meaning	Value type	Requirement
callerBoneFractureStateClassIds	Caller bone fracture state class ids	array of string	Required; constraints below
callerBoneFractureStateRequirements	Caller bone fracture state requirements	array of array	Required; constraints below
observedBoneFractureStateEvidence	Observed bone fracture state evidence	array of number	Required; constraints below
knownBoneFractureStateFlags	Known bone fracture state flags	array of number	Required; constraints below

Supply unique nonblank class IDs, one rectangular binary requirement row per class, and aligned binary observation and known-flag arrays. Each class must require at least one positive witness. Requirement 0 ignores an evidence column; requirement 1 needs a known positive observation for full witnessing. An unknown requirement remains compatible, while a known absent requirement excludes the class. Both returned class lists preserve caller order. No readiness rubric is installed and compatible does not mean fully witnessed or approved.

compatible = no required known absence; fully witnessed = every required witness known and positive

Use the field order, units and branch conditions described above.

Output field	Meaning	Value type
compatibleCallerClasses	Caller classes with no known absence of required positive evidence.	array of string
fullyWitnessedCallerClasses	Caller classes with all required positive evidence known and present.	array of string

json

{
  "input": {
    "callerBoneFractureStateClassIds": [
      "a",
      "b"
    ],
    "callerBoneFractureStateRequirements": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedBoneFractureStateEvidence": [
      1,
      0
    ],
    "knownBoneFractureStateFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

A supplied evidence classification does not measure fracture velocity or establish a universal fresh-versus-dry verdict. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Burning Stage Bone Color Classifier for a related task: Bone burning interpretation depends on more than color alone.

Use Mandibular Gonial Angle Measurement Tool for a related task: A gonial-angle measurement depends on independently defined rays and a measurement plane.

References

Green/Dry Bone Fracture Velocity Classifier — tool.io

Similar or alternative tools

Burning Stage Bone Color Classifier
Bone burning interpretation depends on more than color alone.
Mandibular Gonial Angle Measurement Tool
A gonial-angle measurement depends on independently defined rays and a measurement plane.