Skip to content

Fix issue 310 #335

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

Merged
merged 2 commits into from
May 16, 2021
Merged

Fix issue 310 #335

merged 2 commits into from
May 16, 2021

Conversation

mcgarth
Copy link
Contributor

@mcgarth mcgarth commented May 12, 2021

This PR introduces a circumventive measure to address the Issue identified at: #310

Specifically, I add a small value of 1e-20 to the reference phase that is subtracted from each interferogram. This avoids pixels taking the exact value of zero (0.0) and possibly being converted to NaN downstream in the workflow.

@mcgarth mcgarth self-assigned this May 12, 2021
@mcgarth mcgarth requested review from basaks and richardt94 May 12, 2021 01:52
Copy link
Contributor

@richardt94 richardt94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. You've added comments which make the reference phase correction process more clear in the code, as well as fixing the bug. Comments as noted - we'll eventually want a more robust fix in APS, up to you whether you want to flag this in comments as a "to do" for later. The offset strategy should work well enough for now.

@basaks basaks merged commit 6a64861 into develop May 16, 2021
@mcgarth mcgarth deleted the mg/issue-310 branch May 17, 2021 01:07
@mcgarth mcgarth linked an issue May 24, 2021 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nans for pixels in reference window in linear_rate product
3 participants