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

Decide on footprints and areas for gg and gk #2

Open
msyriac opened this issue Nov 28, 2018 · 4 comments
Open

Decide on footprints and areas for gg and gk #2

msyriac opened this issue Nov 28, 2018 · 4 comments

Comments

@msyriac
Copy link
Member

msyriac commented Nov 28, 2018

We have overlap mainly in Deep56 and Deep8 for S16.

  • Should we restrict the cross-correlation to exactly the "Steve mask" region?
  • Should we extend the gg auto-correlation to the full Y3 footprint? Does this matter for sample variance cancellation? Do we care about sample variance cancellation?
@ajvanengelen
Copy link

I think the answer to the first one is probably yes, as that is our nominal region (for S15 at least). If it is too narrow, that should be brought to the attention of everyone doing act lensing, not just this paper

@xuod
Copy link
Collaborator

xuod commented Nov 29, 2018

For the second point, I'm thinking yes, unless that makes things too difficult to get a joint covariance matrix.

@msyriac
Copy link
Member Author

msyriac commented Nov 29, 2018

@ajvanengelen agreed!
@xuod Good point. I would guess that the gg-gk covariance is negligible if we use 800 sq.deg. of gk overlap and 5000 sq.deg. of Y3 gg. If we checked this with gaussian sims, would that be enough?

Another option is to have 3 data vectors {gk,gg_o,gg_no} where gg_o is calculated in the overlap region and gg_no elsewhere.

@xuod
Copy link
Collaborator

xuod commented Nov 29, 2018

Yep, probably worth testing it. For the other option, I guess that might introduce more covariance between data vectors. Perhaps worth testing too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants