Avoid deep copying?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
Currently, we are using deep copies of parameters in order to avoid a memory leak issue that resulted in MCMC chains overwriting an inappropriately shared value for a particular parameter. While this seems to fix the bug, @jasonasher and @ekr-cfa have said that this is not likely the right way to solve the problem, and probably some restructuring of the code can avoid the problem.
We need to dig into this a bit more to determine what other approaches may be viable.
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
No files, tests, or entry points are identified. Start by tracing where parameter deep copies are made and how MCMC chains share or overwrite parameter values. Done means identifying and implementing a restructuring that avoids the memory-leak-related overwrite without relying on deep copies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100