-
Notifications
You must be signed in to change notification settings - Fork 320
Update prep_aria to support handling of NISAR tropo and SET layers #1514
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
Open
sssangha
wants to merge
2
commits into
main
Choose a base branch
from
nisar_tropo_set
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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.
issue (complexity): Consider refactoring the new NISAR path by splitting
invert_diff_correctionsinto smaller helpers for math, HDF5 writing, and design-matrix creation, and by encapsulating the NISAR/non-NISAR branching logic inload_ariato keep the main flow simple.The new NISAR logic is functionally solid but
invert_diff_correctionsis taking on too many responsibilities and duplicating parts of the existing timeseries writing path. You can reduce complexity by teasing apart the math, IO, and metadata while keeping behavior identical.1. Extract math into a focused helper
Move the dense inversion + masking logic into a small helper that takes already‑prepared arrays. This keeps
invert_diff_correctionsfocused on reading metadata and orchestrating:Then
invert_diff_correctionscan be simplified to:This isolates the inversion semantics (incl. NaN masking) in one place and makes them easier to test.
2. Extract a shared HDF5 writer for timeseries cubes
The HDF5 write path in
invert_diff_correctionsmirrorswrite_timeseries. You can factor a common helper that both NISAR and non‑NISAR flows call, avoiding divergence when metadata layout changes:Then in
invert_diff_corrections:And you can similarly refactor
write_timeseriesto usewrite_timeseries_cubeonce it has built itstimeseriesarray, so there is a single path for writing the HDF5 cube.3. Separate design‑matrix construction from IO
Building
Ais currently interleaved with reading each band. You can simplify this by a small helper that only maps pair metadata →A:Then
invert_diff_correctionsbecomes:This reduces cognitive load by making “what indices correspond to which dates” an explicit, testable unit instead of being buried in the read loop.
4. Keep NISAR branching in
load_ariasmallThe new NISAR branch in
load_ariais reasonable, but you can keep it from growing by encapsulating the strategy selection:Usage:
This keeps platform‑specific branching out of the main
load_arialoop and makes it easier to add future platform behaviors without expanding the loop itself.These small, focused helpers keep all existing functionality (including the NISAR‑specific inversion semantics) but make the code easier to reason about, test, and evolve.