-
Notifications
You must be signed in to change notification settings - Fork 297
unwrap_error_phase_closure: use user-defined connCompMinArea
#1336
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
Conversation
…rea when labeling connected components
Reviewer's Guide by SourceryThis pull request modifies the Sequence diagram for
|
| Change | Details | Files |
|---|---|---|
Modified the correct_unwrap_error_phase_closure function to accept a cc_min_area argument, allowing users to specify the minimum area for connected component labeling. |
|
src/mintpy/unwrap_error_phase_closure.py |
Assessment against linked issues
| Issue | Objective | Addressed | Explanation |
|---|---|---|---|
| #1335 | Ensure the correct_unwrap_error_phase_closure function uses the user-defined connCompMinArea value when labeling connected components, instead of the default value. |
✅ | |
| #1335 | The code should use the user-defined connCompMinArea value when labeling connected components during phase closure unwrapping error correction. |
✅ |
Possibly linked issues
- User-defined connCompMinArea not used during unwrapping error correction with phase_closure method #1335: The PR fixes the issue by adding a cc_min_area arg to correct_unwrap_error_phase_closure so the user-defined connCompMinArea can be passed to the connected component labeling function.
Tips and commands
Interacting with Sourcery
- Trigger a new review: Comment
@sourcery-ai reviewon the pull request. - Continue discussions: Reply directly to Sourcery's review comments.
- Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with@sourcery-ai issueto create an issue from it. - Generate a pull request title: Write
@sourcery-aianywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai titleon the pull request to (re-)generate the title at any time. - Generate a pull request summary: Write
@sourcery-ai summaryanywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment@sourcery-ai summaryon the pull request to
(re-)generate the summary at any time. - Generate reviewer's guide: Comment
@sourcery-ai guideon the pull
request to (re-)generate the reviewer's guide at any time. - Resolve all Sourcery comments: Comment
@sourcery-ai resolveon the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore. - Dismiss all Sourcery reviews: Comment
@sourcery-ai dismisson the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai reviewto trigger a new review! - Generate a plan of action for an issue: Comment
@sourcery-ai planon
an issue to generate a plan of action for it.
Customizing Your Experience
Access your dashboard to:
- Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others. - Change the review language.
- Add, remove or edit custom review instructions.
- Adjust other review settings.
Getting Help
- Contact our support team for questions or feedback.
- Visit our documentation for detailed guides and information.
- Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.
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 @Alex-Lewandowski - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding a check to ensure
cc_min_areais a positive value.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 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.
Good thought, but maybe it would be best to check in the |
+ objects.conncomp.label_conn_comp: skip removing small objects if there is only one label + cli.unwrap_error_phase_closure: add checking for --num-sample and --min-area
yunjunz
left a comment
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.
LGTM. Thank you @Alex-Lewandowski!
connCompMinAreaunwrap_error_phase_closure: use user-defined connCompMinArea
Make
correct_unwrap_error_phase_closureuse user-definedconnCompMinAreawhen labeling connected components. It currently always uses the default.Description of proposed changes
Fixes #1335
cc_min_areaarg tocorrect_unwrap_error_phase_closureso it can be passed tocc_obj.label(min_area=cc_min_area).min_areais not passedlabel, it uses the default of 2.5e3Reminders
If modifying functionality, describe changes to function behavior and arguments in a comment below the function declaration.If adding new functionality, add a detailed description to the documentation and/or an example.Summary by Sourcery
Modify the phase closure error correction function to allow user-defined minimum area for connected component labeling
New Features:
cc_min_areato control the minimum area threshold for connected component labelingBug Fixes:
Enhancements:
Summary by Sourcery
Modify the phase closure error correction function to allow user-defined minimum area for connected component labeling
New Features:
cc_min_areaparameter tocorrect_unwrap_error_phase_closurefunction to control the minimum area threshold for connected component labelingBug Fixes:
Enhancements: