Make DesignMatrixBuilders pickleable and saveable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 990
- Forks
- 106
- Avg merge
- 7d 34m
- Merged PRs (30d)
- 1
Description
Use cases:
- It should be possible to pickle a
DesignMatrixBuilder(and/orDesignInfo, same issue) - Checking if two designs are the same: this comes up for rERPy -- it's only valid to form a grand average across multiple analyses if the underlying regressions were the same. In particular it would be good to be able to check for subtle gotchas like use of
center(...)with different means across the different analyses.
The easy part of this is reviewing the inner structure of DesignMatrixBuilder (column builders and all that) to make sure it's sensible, and similarly for factor state dicts.
The more complicated part is capturing the evaluation environment in a reasonable way.
Precondition: #25
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.
Research direction
Begin with prerequisite issue #25, then inspect DesignMatrixBuilder, DesignInfo, column builders, and factor state dictionaries. Determine how their evaluation environment is represented and define what must be preserved for pickling, saving, and comparing designs, including differing center(...) means. Done means these objects can be serialized and subtle design differences can be detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100