QuantEcon / QuantEcon/QuantEcon.py
[Update] ``Cartesian`` Module
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 2.3k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 3
Description
Review cartesian module and update as required:
- line_profile to see if further
numbaficationis useful or not
Current discussion from @albop:
@oyamad , @mmcky : On the cartesian function, the reasoning was that the loops and list comprehensions are made over the number of dimensions, so that they are probably only a few iterations. Appart from the loop over _repeat_1d, it seems likely that everything else is going to stay in python mode, with little performance gain if any. This was just my feeling though, I didn't test it.
- update so that numba isn't an explicit requirement (numpy version?)
- Incorporate Issue #98
Contributor 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.
Research direction
Start by reading the cartesian module, especially line_profile, and review the discussion about loop performance and numba. Check Issue #98 and identify the current numba requirement. Done means resolving the checklist items: deciding whether numba helps, removing its explicit requirement if appropriate, and incorporating Issue #98.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100