RadioAstronomySoftwareGroup / RadioAstronomySoftwareGroup/pyuvdata
Coarse band shape for uncommon frequency resolutions.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 14
Description
Hi there,
When reading raw MWA fits files with 1kHz Frequency resolution, and without remove_coarse_band=False I get this error.
ValueError: mwax passband shapes are only available for 40 kHz and 80 kHzfine channel widths. To request a passband for a different fine channel width create an issue on the pyuvdata repository. To run without a passband, resubmit with correct_coarse_band=False
This message appears to be out of date, as the UVData.read() argument has been renamed to remove_coarse_band.
If anyone wants to implement the coarse band shape for uncommon frequency resolutions, here's some info about how it was done in Birli:
All currently available correlator frequency resolution modes are a multiple of 200Hz. The Birli implementation of the PFB passband shape correction "scrunches" the 200Hz correction provided on this page to the frequency resolution.
Edit: I'd be happy to provide a raw fits file from this obs if it helps with testing. http://ws.mwatelescope.org/observation/obs/?obsid=1390928416
Thanks
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 with the UVData.read() handling for MWA coarse-band passbands and the error text shown in the issue. Compare the existing 40 kHz and 80 kHz behavior with Birli's 200 Hz correction and its scrunching approach for other resolutions. Done means uncommon resolutions such as 1 kHz can request a coarse-band shape, and the message uses remove_coarse_band consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100