-
Notifications
You must be signed in to change notification settings - Fork 15
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
Do not recreate parser_name
input port to change default
#54
Do not recreate parser_name
input port to change default
#54
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #54 +/- ##
===========================================
+ Coverage 88.93% 90.24% +1.30%
===========================================
Files 32 32
Lines 2449 2408 -41
===========================================
- Hits 2178 2173 -5
+ Misses 271 235 -36
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
90c7ee3
to
aeadadd
Compare
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.
Hi @sphuber the tests seem to be failing for python 3.10 could you check why that is?
It seems that it is failing when trying to get the lammps version number.
I am seeing these errors in the logs:
Maybe it is not the Python version but the LAMMPS version. The Python 3.10 run is using |
The `CalcJob` plugins were setting the default value for the `parser_name` metadata option by redefining the port. This is not desirable since this loses the `help` attribute. Instead, we simply change the default through the attribute on the existing port.
The plugin was setting `CodeInfo.withmpi` based on the inputs from `metadata.options.withmpi`. This is not necessary as the metadata option is already handled by the `CalcJob` base class. The plugin implementation should only set `CodeInfo.withmpi` if it wants to _force_ the code to be run with MPI enabled or disabled. The `CalcJob` base implementation used to not distinguish between the two, but in aiidateam/aiida-core#5922 the handling of MPI was improved. A `Code` can now define whether it should be run with MPI or not and so the `CalcJob` class now has to raise if the MPI setting of the code and the plugin clash. The `withmpi` option, if explicitly set by the user, is also checked. Since the plugin doesn't intend to enforce MPI or not, the setting on the `CodeInfo` is removed.
This code is not used and seems to have no relation with the `BaseLammpsCalculation`.
aeadadd
to
6debf5b
Compare
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.
It looks good!
A number of fixes to the various
CalcJob
plugins.