RadioAstronomySoftwareGroup / RadioAstronomySoftwareGroup/pyuvsim
UVBeam runtime / memory usage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 54
- Forks
- 11
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 8
Description
We've always known that UVBeam increases runtime and memory usage, but we should get a better handle on how much. Changes to runtime also seemed to have occurred in 1.4.1 but possibly in a way that hurt the runtime of Analytic Beams. See the table below, where for complete, the "dev" version in the bottom rows refers to pyuvdata 3.1.4.dev85+g7283786a, pyuvsim 1.4.1.dev62+gfc43d8a, and pyradiosky 1.0.2.dev46+gaa1cd83.
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 reproducing the runtime and memory measurements for UVBeam, comparing the listed development versions with the relevant releases. Pay particular attention to whether the apparent 1.4.1 change affects Analytic Beams. Done means documenting comparable measurements and identifying whether a regression exists; the issue names no files or tests to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100