Add ability to name weights
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by reading issue #199 and locating the code that handles weight sets and creates their columns. Determine how a weight name should be supplied and retained when another set overwrites it. Done means the overwritten weights appear in an appropriately named column, with tests covering the behavior.
Written by the indexing model from the issue text.
Description
So that when it gets overwritten with another set of weights (#199) it's added as an appropriately-named column.
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- Avg merge
- 13h 43m
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 PolicyEngine/microdf
-
docs/examples.md still says MicroDataFrame.cov() and .corr() are unweightedPossibly taken @juaristi22 claimed this 20 days ago. Open
PolicyEngine/microdf#335 · 1 assignee ·
Maintainers usually reply within 1 day
-
Poverty gap docstrings overclaim FGT indices, and the poverty estimators have no testsPossibly taken @juaristi22 claimed this 20 days ago. Open
PolicyEngine/microdf#334 · 1 assignee ·
Maintainers usually reply within 1 day
-
Fail closed: aggregation and construction paths that silently return unweighted resultsPossibly taken @juaristi22 claimed this 20 days ago. Openbug
PolicyEngine/microdf#333 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
PolicyEngine/microdf#314 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
PolicyEngine/microdf#264 · 2 comments ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microdf
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
adri0/scadustats#128 ·
Maintainers usually reply within 1 day
-
`TIMESTAMP`, `TIMESTAMP_NTZ`, `TINYINT` and the other `TypeDecorator`s don't declare `python_type`Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
RPBCOpenawaiting policy acceptance precheck-passed
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Bioconductor/BiocContributions#240 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation good first issue launch
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
FlologixAI/etchwork#4 ·