RadioAstronomySoftwareGroup / RadioAstronomySoftwareGroup/pyuvdata
Investigate extra_keywords handling in measurement sets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 14
Description
The current approach is to put the entire extra_keywords dict into the main MS table as a dict called "pyuvdata_extra". Will this work if there are arrays or more complicated things present? If not we should warn about those kinds of things.
Also, this approach might not pick up generic extra keywords inserted by other MS writers. Maybe this isn't a common practice though, as it is in e.g. uvfits.
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 tracing how extra_keywords is written into the main measurement-set table under the pyuvdata_extra dict. Investigate whether arrays or other complex values are supported and whether generic keywords from other measurement-set writers are preserved; done means a documented handling decision and warnings where needed.
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