Skip to content

General update and product rename - #193

Merged
abradley60 merged 14 commits into
mainfrom
general_update_and_product_rename
Aug 20, 2026
Merged

General update and product rename#193
abradley60 merged 14 commits into
mainfrom
general_update_and_product_rename

Conversation

@abradley60

Copy link
Copy Markdown
Collaborator

@caitlinadams caitlinadams left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This largely looks good to me, I made a few minor requests for clarity, but happy for you to address them as you see fit.

returned from the ASF API is different than that returned from the CDSE API
returned from the ASF API is different than that returned from the CDSE API.

Warning - Only IW Bursts Available

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'm not sure I entirely understand this comment -- are you saying that ASF only has IW bursts (and not EW bursts), or are you saying that ASF only has IW in bursts (not scenes). Will a warning be triggered if the user tries to look for EW bursts?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Added some clearer comments

)
from sar_pipeline.analysis.compare_cog import compare_cog_stats

VALID_SENSOR_MODES = ["IW"]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is the plan to update this when EW is supported? Or is IW the only valid sensor mode?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

If plan is to update, it might be worth adding a "TODO" comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yep thats planned in another PR, will add a TODO

# make the base .yaml for RTC processing
if product == "RTC_S1":
RTC_RUN_CONFIG = RTCConfigManager(base_config="S1_RTC.yaml")
RTC_RUN_CONFIG = RTCConfigManager(base_config=f"S1_RTC_{sensor_mode}.yaml")

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

You don't have a failure mode if that config file doesn't exist -- should you add one in case they're deleted or someone tries to use their own config file? Or are these scenarios unlikely to come up?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This does get handles in the RTCConfigManager if it's not a valid BaseConfigType -

@caitlinadams caitlinadams left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks good, thanks for making the minor changes

@abradley60
abradley60 merged commit 109e5f6 into main Aug 20, 2026
2 checks passed
@caitlinadams
caitlinadams deleted the general_update_and_product_rename branch August 27, 2026 04:12
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.

2 participants