Welcome to ClientVPS Mirrors

Dirty data and safe infeasibility handling

Dirty data and safe infeasibility handling

WFC stops early when design roles, source evidence, checksums, categories, or sample support are inconsistent. A stop is evidence to repair or review the inputs, not permission to choose a more convenient target.

Common safe responses are:

design <- wf_prepare_design(
  design_only,
  id = "person_id",
  calibration = c("age_group", "region"),
  base_weight = "base_weight"
)

target <- wf_import_target(
  "population-margins.csv",
  "population-margins.csv.source.dcf",
  dims,
  key_map = c(age_group = "age_group", region = "region"),
  count = "population_count"
)

precheck <- wf_precheck(design$data, target, id = design$roles$id)
cell_plan <- wf_plan_cells(design, target, dims)

WFC never widens bounds, changes method, changes target, or approves a plan in response to infeasibility. Those are separate human decisions and may require a new workflow.

Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.

This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.