aod-proof-and-analysis-toolkit

Validate probability and statistics calculations in the Area Occupancy Detection codebase.

316|9|Updated Nov 23, 2024
One-click install
npx skills add https://github.com/Hankanman/Area-Occupancy-Detection --skill aod-proof-and-analysis-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aod-proof-and-analysis-toolkit
Source: https://github.com/Hankanman/Area-Occupancy-Detection/tree/main/.claude/skills/aod-proof-and-analysis-toolkit
Command: npx skills add https://github.com/Hankanman/Area-Occupancy-Detection --skill aod-proof-and-analysis-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that probability/statistics math in Area Occupancy Detection is correct before merging pull requests, avoiding potential bugs and misestimations.

Core Features & Use Cases

  • Verify Prior Calculation: Checks if the global_prior calculation uses a period that reflects reality.
  • Logit-space Boost Validation: Ensures a boost's probability shift aligns with its stated gain.
  • Decay Curve Audit: Confirms decay_factor matches the expected formula and floor cutoff.
  • Timezone Audit: Prevents mixing of UTC and local timezones leading to anomalies.
  • Statistical Sufficiency: Evaluates if learned probabilities have enough data to be trusted.
  • Ratio Consistency: Audits that ratios have consistent numerator and denominator time windows.
  • Feedback-loop Analysis: Prevents area-to-area couplings from causing runaway loops.
  • Use Case: Before merging a PR, run this Skill to validate all mathematical calculations in the Area Occupancy Detection codebase.

Quick Start

Use the aod-proof-and-analysis-toolkit skill to validate the decay factor calculation for the area 'Living Room'.

Frequently Asked Questions about aod-proof-and-analysis-toolkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Bayesian occupancy probability calculations before merging code?

You validate Bayesian occupancy probability calculations by auditing global prior periods, logit-space probability shifts, and statistical sufficiency to ensure learned probabilities have enough trusted data before merging a pull request.

How do I prevent UTC and local timezone anomalies in occupancy detection statistics?

To prevent timezone anomalies in occupancy detection statistics, audit time window calculations to ensure UTC and local timezone mixing does not corrupt ratio numerators, denominators, or decay factor formulas.

What is the best way to audit decay factor formulas in area occupancy detection code?

The best way to audit decay factor formulas in area occupancy detection code is to confirm the decay calculation matches the expected mathematical formula and verify the floor cutoff prevents indefinite probability decay.

Do I need in-depth statistical knowledge to validate probability math in occupancy detection code?

Yes, validating probability math in occupancy detection code requires in-depth knowledge of Bayesian occupancy modeling and statistical analysis to accurately evaluate prior calculations, logit-space boosts, and statistical sufficiency.

Why do area-to-area couplings cause runaway feedback loops in occupancy modeling?

Area-to-area couplings cause runaway feedback loops in occupancy modeling when learned probabilities and activity patterns recursively amplify each other without statistical sufficiency checks or ratio consistency boundaries.

How do I check if learned probabilities in occupancy detection have enough data to be trusted?

To check if learned probabilities have enough data to be trusted, evaluate statistical sufficiency to determine if the collected activity patterns adequately support the estimated probability shifts and prior calculations.