-
Notifications
You must be signed in to change notification settings - Fork 74
Fix solid earth tides computation fail when frequencyA is missing #243
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
xhuang-jpl
merged 29 commits into
isce-framework:develop
from
xhuang-jpl:fix_solid_earth_freq
Apr 14, 2026
+11
−3
Merged
Changes from all commits
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
da95af1
sm r3.4
3a8e2ec
merge R4.0.2beta-1
b6cfbbb
change the SM commit id for R4.0.2
f764f2f
merge upstream develop branch
a920ae6
Merge remote-tracking branch 'upstream/develop' into develop
1d28fae
Merge remote-tracking branch 'upstream/develop' into develop
84f3874
Merge remote-tracking branch 'upstream/develop' into develop
2bb897a
Merge remote-tracking branch 'upstream/develop' into develop
da76f88
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
6313217
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
ce2b301
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
8394511
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
72645bd
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
6f93fd3
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
eebd988
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
9b108ce
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
b1c78f7
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
e46f53f
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
54d6ab4
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
73b6b9b
Merge branch 'develop' of https://github-fn.jpl.nasa.gov/isce-3/isce …
2eb1387
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
42f2514
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
39c9883
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
f6cfd55
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
6176caa
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
1f111b3
Merge branch 'develop' of https://github.com/isce-framework/isce3 int…
2ac16f7
fix the frequency bug
a6dbede
fix typos
54dba04
add the comments
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we capture first available of A or B instead of calculating a different datacube for each? They would have different values, wouldn't they?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good question @Tyler-g-hudson, for NISAR InSAR processing, we are always processing frequencyA even if the product has both freqA and freqB. This fix is for users who need to process the freqB stand alone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I've understood that part - what I mean to ask is why we have selected to do that when the values might be different between two different data cubes, is it because we only expect people to use it for the primary frequency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We always expect people use the frequencyA as the primary at least for the NISAR.