Implement an option for factor-based prediction
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reviewing the existing prediction and design-matrix APIs, then compare their representation with the factor-level metadata discussed in issue #61. Define how factor-value specifications should map to prediction inputs and what pairwise categorical comparisons must produce; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Description
Right now we can do prediction (i.e., design matrix generation) by specifying a set of data values ({"x": 1, "y": 2}). But for some purposes, like generating all pairwise categorical significance tests ("is the value of my linear predictor significantly different at a == a1 than it is at a == a2?"), it would be nice to be able to write this in terms of factor values ("is the value of my linear predictor significantly different when the C(...) factor is on level a1 compared to when it's on level a2?", without having to grovel through the AST of the factor's python code to figure out which data variables are being accessed. In particular, this would be expressed at the same representational level as factor-level metadata (see #61).
So we should have a version of predict that takes a set of specifications for factor values, and goes from there.
- Dominant language
- Python
- Stars
- 990
- Forks
- 106
- Avg merge
- 7d 34m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pydata/patsy
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100