AFB Ropey Matchstick Test Checker

Caller independently observed brood texture/test evidence vs applicable veterinary/laboratory referral criteria; ropey observation alone does not diagnoseAFB. Independently declared positive requirements, overlapping/unknown classes retained. Caller independently verifies strain, site, protocol and evidence; not colony-health, treatment, transport-safety or regulatory certification.

Description

A ropey-brood observation is evidence considered in foulbrood assessment.

A ropey-brood observation is evidence considered in foulbrood assessment.1

An annotation checker does not confirm American foulbrood or replace an appropriate diagnostic process. Use AFB Ropey Matchstick Test Checker to evaluate the supplied inputs under the model explained below.

When to use AFB Ropey Matchstick Test Checker

Use AFB Ropey Matchstick Test Checker 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 AFB Ropey Matchstick Test Checker and understand its results

  1. Define the candidate classes and their positive-evidence requirements, then distinguish evidence presence from whether it is known.
  2. Enter Caller observed ropey brood class ids, Caller observed ropey brood requirements, Observed observed ropey brood evidence, Known observed ropey brood flags using the field table and validation rules below, then run the tool.
  3. Read Compatible caller classes, Fully witnessed caller classes; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. 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 fieldMeaningValue typeRequirement
callerObservedRopeyBroodClassIdsCaller observed ropey brood class idsarray of stringRequired; constraints below
callerObservedRopeyBroodRequirementsCaller observed ropey brood requirementsarray of arrayRequired; constraints below
observedObservedRopeyBroodEvidenceObserved observed ropey brood evidencearray of numberRequired; constraints below
knownObservedRopeyBroodFlagsKnown observed ropey brood flagsarray of numberRequired; 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 fieldMeaningValue type
compatibleCallerClassesCaller classes with no known absence of required positive evidence.array of string
fullyWitnessedCallerClassesCaller classes with all required positive evidence known and present.array of string
json
{
  "input": {
    "callerObservedRopeyBroodClassIds": [
      "a",
      "b"
    ],
    "callerObservedRopeyBroodRequirements": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedObservedRopeyBroodEvidence": [
      1,
      0
    ],
    "knownObservedRopeyBroodFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

Ropiness is one observed sign discussed in foulbrood assessment, alongside other observations and diagnostic methods. This tool compares supplied binary evidence with caller rules; it does not examine brood, confirm disease or choose a response.2

An annotation checker does not confirm American foulbrood or replace an appropriate diagnostic process. 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 EFB Scale vs AFB Differential Lookup for a related task: Foulbrood differential references describe observations under a verified protocol.

Use Chalkbrood Mummy Count Severity Classifier for a related task: Mummy counts can be expressed relative to matched inspected brood.

References

  1. AFB Ropey Matchstick Test Checker — tool.io

  2. Honey Bee Producer Guide: diagnosis and monitoring — Canadian Food Inspection Agency

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies