-
Notifications
You must be signed in to change notification settings - Fork 16
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
Reset GUI #489
Reset GUI #489
Conversation
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #489 +/- ##
==========================================
+ Coverage 77.29% 78.29% +0.99%
==========================================
Files 44 44
Lines 3127 3160 +33
==========================================
+ Hits 2417 2474 +57
+ Misses 710 686 -24
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
@superstar54 I did a test, and it seems the Smearing type: , Smearing width (Ry) arent reset , also Wavefunction cutoff (Ry) |
@AndresOrtegaGuerrero Thanks for the review.
I fixed it. Also fixed the
yes, each panel needs to implement a |
@superstar54 Would it be necessary to add in the documentation of qe_app in |
@superstar54 I tested the PR, now it does update the fields i told you, the one missing is the one from the nscf kpoints distance from PDOS panel. I also noticed some behavior. I started the app and select one workchain and then another , and then the first one again. (Everything was working) after another change (the previous workchain) the app crashed. |
@superstar54 another thing i noticed is that one of my workchain , (newer one) doesnt set the input parameters, but the another one i was using for testing it does. I know this is related to Load GUI PR. |
Good point. I have added it.
After resetting, the pdos panel is not visible anymore. how do you check this?
This is because I set the
Which workchain? In my test, the load_GUI is OK. |
It seems my workchain is "old" so i tried with a new one an no issues , maybe that workchain is incompatible with the load_GUI, but indeed i tried a new one and everything upload correctly |
@@ -278,7 +279,7 @@ def _on_cutoff_change(self, _=None): | |||
self.ecutrho = self.ecutrho_setter.value | |||
|
|||
def _reset_cutoff_widgets(self): | |||
self.ecutrho_setter.value = 0 | |||
self.ecutwfc_setter.value = 0 | |||
self.ecutrho_setter.value = 0 | |||
|
|||
def _reset_traitlets(self): |
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.
Maybe you should include docstring to these reset* functions , just to keep it consistent with the rest of your changes where you added docstring
Hi @AndresOrtegaGuerrero , thanks for the review. I made the changes as you requested.
|
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.
Thank you! LGTM. One note once you use .reset() for the settings in the panels, if a future plugin doesnt have this method it should be a problem right? I think that just be a different issue for the documentation for plugin developers
Thanks for the comment. In the |
Thanks @superstar54. This is finally happened, great!
However, there is no guarantee that user (property plugin developers) will implement this. I think if the |
Reset the GUI when selecting to start a new workflow. Related to #437 #420.
Reset:
Step 4 will be automatically reset when the
process
of step 3 is reset.