-
Notifications
You must be signed in to change notification settings - Fork 297
sensor: add UAVSAR-L
#1320
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
sensor: add UAVSAR-L
#1320
Conversation
+ `utils.network.py`: - refactor `critical_perp_baseline()` to incorporate different near_range value of different sensors - `simulate_coherence_v2()`: add SNR as a input argument + `utils.ptime.get_date_range()`: ensure output dt_list is within the input `[dmin, dmax]`
Reviewer's Guide by SourceryThis pull request introduces several enhancements including adding UAVSAR-L sensor info, refactoring critical_perp_baseline to use sensor-specific near_range values and improved defaults, updating the simulate_coherence_v2 function to accept an SNR parameter, and ensuring the output date range is properly bounded in get_date_range. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
PR SummaryThis Pull Request introduces several enhancements and fixes across different modules of the codebase:
Overall, these changes enhance the functionality and flexibility of the codebase, particularly in handling different sensor configurations and improving date range calculations. Review Checklist
Suggestion
This comment was generated by AI. Information provided may be incorrect. Current plan usage: 0% Have feedback or need help? |
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.
Hey @yunjunz - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding a unit test for the
critical_perp_baselinefunction to ensure it returns the expected values for different sensors. - The
near_rangedictionary incritical_perp_baselinecould be moved to thesensor.pyfile to keep sensor-specific information in one place.
Here's what I looked at during the review
- π‘ General issues: 1 issue found
- π’ Security: all looks good
- π’ Testing: all looks good
- π’ Complexity: all looks good
- π’ Documentation: all looks good
Help me be more useful! Please click π or π on each comment and I'll use the feedback to improve your reviews.
Description of proposed changes
objects/sensor: add UAVSAR-L infoutils.network.py:critical_perp_baseline()to incorporate different near_range value of different sensorssimulate_coherence_v2(): add SNR as an input argumentutils.ptime.get_date_range(): ensure output dt_list is within the input[dmin, dmax]Reminders