Kernel registry

The kernel registry is the routing layer: it maps a user-facing kernel name to concrete implementations and metadata (support, parameterization, tail allowances).

What to document for each kernel

  • Support: positive or real line.
  • Parameters and constraints.
  • Which backends are supported (SB/CRP).
  • Whether bulk-only and bulk+GPD are supported.

Developer checklist

  1. Implement the distribution functions (and MixGPD wrappers if needed).
  2. Add the registry entry.
  3. Update kernel_support_table() expectations (docs + tests).
  4. Add a kernel documentation page under website/kernels/.

See developers/add-kernel.qmd for the end-to-end recipe.

Prereqs

  • Required packages and data for this page are listed in the setup chunks above.

Outputs

  • This page renders model fits, diagnostics, and summary artifacts generated by package APIs.

Interpretation

  • Canonical concept page: Spec And Contracts
  • Treat this page as an application/example view and use the canonical page for core definitions.

Next

  • Continue to the linked canonical concept page, then return for implementation-specific details.
(c) CausalMixGPD - Bayesian semiparametric modeling for heavy-tailed data
- - Cite - API - GitHub