Jonathan Pober

Should actually be supported through 'cal_style' not 'cal_type'.

The original 21cmSense code has been deprecated for quite some time now. It's my fault for not formally updating this Github page and marking the code as such -- I...

@steven-murray is this something you are willing to (one day) help us with?

Another factor throw into the mix is brought up by this recent paper: https://ui.adsabs.harvard.edu/abs/2021ApJ...923...33B/abstract. They have a publicly available code for calculating the local horizon topography. I haven't looked at...

I'm not surprised to hear the code is bad, but I'd be surprised if it really doesn't account for local topography (since they claim it does exactly that in the...

@StellanBechtold I think it's a uvh5 file, right?

Back of the envelope, this is sub-micron shift in the telescope position. There's no need for pyuvdata to support that level of precision, but if it's an easy fix in...

Ok, so maybe I was wrong that it was the `set_uvws_from_antenna_positions` method in particular. But it looks like `parse_telescope_params` on line 1220 of simsetup.py runs: `tele_params['telescope_location'] = uvutils.XYZ_from_LatLonAlt(*telescope_location)` So that...

I can't say for certain, but my guess is the output location is an Earth radius like location. I say that because I believe pyuvdata has a check that the...

After an initial conversation with @aelanman this morning, we decided there are two issues, one easier to fix than the other: (1) line 1220 in simsetup sets the telescope location...