Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ps_kspan moves power to eor window #200

Open
lmberkhout opened this issue Feb 25, 2020 · 9 comments
Open

ps_kspan moves power to eor window #200

lmberkhout opened this issue Feb 25, 2020 · 9 comments
Labels
bug An error discussion needed A call for discussion major A major/large bug fix or upgrade option

Comments

@lmberkhout
Copy link

First noticed in data and then reconfirmed in simulations. Using the ps_kspan keyword changes power in the EoR window by a few OOM.

ps_kspan not set in wrapper, uses default
Screen Shot 2020-02-25 at 1 40 13 PM

identical simulation with one extra keyword, ps_span=200. (wavelength units):
Screen Shot 2020-02-25 at 2 26 04 PM

@lmberkhout lmberkhout changed the title ps_kspan ps_kspan moves power to eor window Feb 25, 2020
@lmberkhout
Copy link
Author

The first test I did was to try going straight to power spectrum through uvf cubes. The keywords were identical to the first plot in the thread (no kspan restriction), with an additional keyword to save uvf cubes, and a keyword to point eppsilon to the uvf cubes to use. This is the result.
Screen Shot 2020-02-25 at 1 41 58 PM

@lmberkhout
Copy link
Author

Next step: Do a bit of code development, interpolate to an orthoslant grid from the zenith observation, take an obs at a different time, and interpolate to that same zenith orthoslant grid

@lmberkhout
Copy link
Author

linking to Nichole's issue on this topic #108

@nicholebarry
Copy link
Contributor

@rlbyrne Could this be similar to the effect that you talked about in Figure 4 of your paper? Essentially a wedge-dependent horizontal throw: the more wedge you include, the higher up in kpar it goes.

@lmberkhout I assume you aren't using the modified gridding kernel in these sims? I wonder if the effect is mitigated by the modified gridding kernel (my gut feeling is yes)

@lmberkhout
Copy link
Author

@nicholebarry I believe I am using the modified gridding kernel (at least I am very much intending to). This was replicating a simulation with keywords sent by @mwilensky768

@rlbyrne
Copy link
Contributor

rlbyrne commented Mar 4, 2020

@nicholebarry The effect I was talking about in my paper only comes in in calibration. My understanding is that ps_kspan doesn't affect calibration and only enters when the Healpix cubes are made.

@nicholebarry
Copy link
Contributor

@rlbyrne gotcha

@lmberkhout Okay cool, just checking. Would it be possible for you to plot the UV-plane at a frequency slice for both the default kspan and the 200 wavelengths kspan? I bet we'll see some spatial messiness at longer baselines. I believe Bryna has an in-house uv plotter, but I forget what it's called. But you can just plot it yourself with quick_image, the data are located in ps/data/uvf_cubes under something_something_something_model_uvf.idlsave

@bhazelton
Copy link
Member

bhazelton commented Mar 5, 2020

The one in eppsilon is called uvf_slice_plot.pro, it's easiest to invoke by calling ps_wrapper with the following keywords: /plot_slices, slice_type='raw' or /plot_slices, slice_type='divided' depending whether you want them before or after the weights are divided out. You can also use the uvf_plot_type keyword to control what is plotted -- the options are ['abs', 'phase', 'real', 'imaginary'], the default if you don't set it is 'abs'.

@lmberkhout
Copy link
Author

lmberkhout commented Mar 25, 2020

Slice type = 'abs' (default)
Default Kspan UV plane
Screen Shot 2020-03-24 at 5 05 43 PM
Kspan = 200. UV plane
Screen Shot 2020-03-24 at 5 16 13 PM
Some discussion with Nichole highlights that the background contamination is evident in these plots

@nicholebarry nicholebarry added bug An error discussion needed A call for discussion major A major/large bug fix or upgrade option labels Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error discussion needed A call for discussion major A major/large bug fix or upgrade option
Projects
None yet
Development

No branches or pull requests

4 participants