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

apply gains to autocorrs #436

Closed
o-smirnov opened this issue Feb 23, 2021 · 6 comments
Closed

apply gains to autocorrs #436

o-smirnov opened this issue Feb 23, 2021 · 6 comments

Comments

@o-smirnov
Copy link
Collaborator

@bennahugo has requested that we apply gains to autocorrelations when forming corrected data.

At the moment we zero them "as a precaution" here, but I see no reason not to flag them with FL.SKIPSOL instead (as we do with baseline length selections right now) to have them ignored yet corrected.

@JSKenyon
Copy link
Collaborator

I have taken a brief look. While I do think that it will probably be ok to do as you suggest, it will also require changes to the compute_corrected kernels. At present, they loop over baseline with a strict p < q approach. We will need them to include p == q. If you think this is worthwhile, I can try to implement something tomorrow.

@JSKenyon
Copy link
Collaborator

This slipped my mind - should I give it a shot @o-smirnov?

@o-smirnov
Copy link
Collaborator Author

Yes, please! I am buried in admin at the moment.

You need to fix the kernels, take out the "precaution", and set FL.SKIPSOL on them instead.

@JSKenyon
Copy link
Collaborator

@o-smirnov @bennahugo See #437. I have tried it out locally and nothing seems to burst into flame.

@o-smirnov
Copy link
Collaborator Author

and nothing seems to burst into flame.

That's my definition of a successful pipeline run!

@o-smirnov
Copy link
Collaborator Author

Also when I don't get arrested.

@JSKenyon JSKenyon closed this as completed Jun 6, 2023
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

2 participants