Frass Freshness Activity Indicator Rater
Independent pest-observation screen retaining competing explanations, not age frass from colour alone, species identification or authorize treatment. Independently established feature columns: independently observed recent frass, independently observed live pest/activity, alternative debris source independently excluded. Unknown evidence and overlapping candidates retained; not semantic parsing, identity, causation, diagnosis, lawfulness, authenticity or safety determination.
Description
Frass-related observations can support different levels of evidence about pest activity.
Frass-related observations can support different levels of evidence about pest activity.1
Fresh-looking traces and independently observed live activity are distinct annotations.
When to use Frass Freshness Activity Indicator Rater
Use this tool to compare independently annotated evidence with the stated candidate rules. Establish the object or visitor scope, measurement units and independently applicable conservation, engineering, access or editorial reference.
How to use Frass Freshness Activity Indicator Rater and understand its results
- Establish the object or visitor scope, measurement units and independently applicable conservation, engineering, access or editorial reference.
- Enter observedFeatureFlags, featureKnownFlags, using the field meanings and rules below, then run the tool.
- Read result.compatibleClasses, result.witnessedClasses, result.unknownFeatureIndices. Use the units and sign conventions below. Review unresolved records and any possible bounds separately from known results.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedFeatureFlags | Observed feature flags | list of number | Required |
| featureKnownFlags | Feature known flags; binary 1 means the matched observation is known, 0 means unknown | list of number | Required |
Supply exactly three binary feature flags and matched binary known flags in the table's order. A known mismatch with a required feature excludes a class; unknown required features leave it compatible but not fully witnessed. Ignored features never block witnessing. Return compatible and witnessed classes plus zero-based unknown feature indices; there is no overall pest-activity verdict.
| Candidate | Independently observed recent frass | Independently observed live pest/activity | Alternative debris source independently excluded |
|---|---|---|---|
| possible-current-activity-evidence | Known present | Ignored | Known present |
| live-activity-evidence | Ignored | Known present | Ignored |
compatible_c=no known constrained feature mismatch; witnessed_c=compatible_c and every constrained feature known Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured result; its nested fields below contain the actual calculation or selected reference | object |
| result.compatibleClasses | Classes with no known mismatch against a constrained feature; unknown evidence can leave classes compatible | list |
| result.witnessedClasses | Compatible classes for which every constrained feature is known; ignored features need not be known | list |
| result.unknownFeatureIndices | Unknown Feature Indices; zero-based positions in the corresponding input record; unresolved records kept separate from known results | list |
{
"input": {
"observedFeatureFlags": [
1,
1,
1
],
"featureKnownFlags": [
1,
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"possible-current-activity-evidence",
"live-activity-evidence"
],
"witnessedClasses": [
"possible-current-activity-evidence",
"live-activity-evidence"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
Object condition, observation coverage and applicable references determine applicability. A supplied comparison or record does not certify conservation treatment, engineering, access compliance or insurance eligibility. Compatibility with unknown required features is not full witnessing; witnessing reflects only the supplied annotations.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Quarantine Isolation Duration Default Weeks Lookup: Collection quarantine duration depends on the actual pest, object and applicable protocol. For a complementary comparison, use Heat Treatment Hours at Target Temp Pest Lookup: Collection heat-treatment duration depends on object compatibility and a qualified pest-control protocol.
References
-
Frass Freshness Activity Indicator Rater — tool.io
Similar or alternative tools
- Quarantine Isolation Duration Default Weeks Lookup
Collection quarantine duration depends on the actual pest, object and applicable protocol.
- Heat Treatment Hours at Target Temp Pest Lookup
Collection heat-treatment duration depends on object compatibility and a qualified pest-control protocol.