-
Notifications
You must be signed in to change notification settings - Fork 68
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
CoM rotation and flip in the GUI #1087
Conversation
+ `Analysis.need_rerun`: based on old and new parameters, decide if we can re-use an existing UDF result, or if we need to re-run + `COMAnalysis`: don't re-run if only `flip_y` or `scan_rotation` changed + JobDetailHandler: re-use existing UDF results, based on `Analysis.need_rerun`
Codecov Report
@@ Coverage Diff @@
## master #1087 +/- ##
==========================================
+ Coverage 69.28% 69.44% +0.15%
==========================================
Files 268 268
Lines 12614 12795 +181
Branches 1777 1817 +40
==========================================
+ Hits 8740 8885 +145
- Misses 3532 3567 +35
- Partials 342 343 +1
Continue to review full report at Codecov.
|
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.
Looks good so far! We should include a link or info sign that explains the parameters. We have them documented in https://libertem.github.io/LiberTEM/reference/api.html#libertem.api.Context.create_com_analysis, for example. :-)
With near-instantaneous recalculation after parameter change it would be awesome to have a slider for the angle, or a rotation handle on the widget for position and size!
I noticed that we don't have COM in our Applications section. We could perhaps create a stub for the "phase contrast" application with an API example, link to reference docs and one screenshot for COM, and a link to https://ptychography-4-0.github.io/ptychography/algorithms.html for SSB ptychography?
We could consider baking a new release soon after this? |
👍 - I'll add more information about the parameters. I also thought about always showing the parameter form, as it doesn't take up a lot of space anyway - what do you think?
Thanks, I'll look into that, should be easy to fix.
Yeah, I thought the same - what do you think about including a fix for #633, too, as I'm touching that code anyways?
Sure, I'll add a section to the docs. |
Yes, I was wondering why they were hidden but figured you had your reasons. 😆
Yes, perfect! Would require a bit more change in the CoM API, but should be pretty straightforward, right? :-) Other points: Thx, great! 👍 |
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
@uellue I've pushed the last fixes; if you are happy with this, I can re-build the client and merge - or do you want to push CoM docs also to this PR? |
If it is OK it could be a quick solution! :-) I can also rebuild the client if I am at it. :-) |
Sounds good! |
* Include links to API use * Cite seminal paper on CoM * Notebook test coverage for new parameters
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Looks good, many thanks! :-)
Should be ready to merge now. :-)
Fixes #31
TODO
Contributor Checklist:
Reviewer Checklist:
/azp run libertem.libertem-data
passed