[Task name, imperative verb]¶
signature_style(inputs) -> output_shape
One-sentence description of what this accomplishes.
You'll need: prerequisites (e.g. "a person_id list", "WORKSPACE_CDR set") Tier: Registered / Controlled CDR versions validated: [list]
Reference¶
- Table(s):
table_name— columns used - Parameters:
param_name— type, format, meaning- Returns: dataframe shape + columns, in plain language
- Behavior notes: e.g. "excludes non-carriers by construction"
Usage¶
Basic usage¶
# canonical, most-common-case code block
# Keep under ~25 lines. If longer, split at a logical seam
# and place the Pitfall at the split point.
Pitfall
— placed INLINE, directly beside the line or parameter that silently produces a wrong answer. Never in Troubleshooting.
Variation: [name]¶
Troubleshooting¶
- If you see
ErrorMessage-> cause and fix.