Chalkbrood Mummy Count Severity Classifier
Actual independently identified chalkbrood mummy/inspected-brood count screen against caller protocol threshold, no colony diagnosis or treatment. Caller independently verifies strain, site, protocol and evidence; not colony-health, treatment, transport-safety or regulatory certification.
Description
Mummy counts can be expressed relative to matched inspected brood.
Mummy counts can be expressed relative to matched inspected brood.1
A threshold screen does not confirm the cause or determine a treatment decision. Use Chalkbrood Mummy Count Severity Classifier to evaluate the supplied inputs under the model explained below.
When to use Chalkbrood Mummy Count Severity Classifier
Use Chalkbrood Mummy Count Severity Classifier to evaluate the supplied inputs under the model explained below. Establish the units, measurement scope and model assumptions before entering values.
How to use Chalkbrood Mummy Count Severity Classifier and understand its results
- Establish the units, measurement scope and model assumptions before entering values.
- Enter Observed mummy counts, Observed inspected brood counts, Caller severity minimum per100 using the field table and validation rules below, then run the tool.
- Read Observed mummies per100 brood, Caller monitoring threshold reached; 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 |
|---|---|---|---|
| observedMummyCounts | Observed mummy counts | array of number | Required; constraints below |
| observedInspectedBroodCounts | Observed inspected brood counts | array of number | Required; constraints below |
| callerSeverityMinimumPer100 | Caller severity minimum per100 | number | Required; constraints below |
Enter nonempty aligned nonnegative safe-integer mummy counts and positive safe-integer inspected brood counts, with mummies≤brood per sample, plus nonnegative caller severity floor per 100. Return 100×pooledMummies/pooledBrood and flag≥floor. No disease confirmation or installed severity categories are applied.
mummiesPer100=100Σmummies/ΣinspectedBrood; reached=rate≥callerFloor Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| observedMummiesPer100Brood | Observed mummies per100 brood | number |
| callerMonitoringThresholdReached | Caller monitoring threshold reached | boolean |
{
"input": {
"observedMummyCounts": [
2,
3
],
"observedInspectedBroodCounts": [
100,
100
],
"callerSeverityMinimumPer100": 2
},
"output": {
"observedMummiesPer100Brood": 2.5,
"callerMonitoringThresholdReached": true
}
} Limitations and assumptions
A threshold screen does not confirm the cause or determine a treatment decision. 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 Small Hive Beetle Trap Threshold Checker for a related task: Trap counts need matched observation durations to express beetles per trap-day.
Use Treatment Threshold Level Checker for a related task: Mite monitoring requires a measurement protocol and independently chosen review limits.
References
Similar or alternative tools
- Small Hive Beetle Trap Threshold Checker
Trap counts need matched observation durations to express beetles per trap-day.
- Treatment Threshold Level Checker
Mite monitoring requires a measurement protocol and independently chosen review limits.