Document the option to run LOBSTER with one jobscript only #811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@utf, I have recently made some modifications to custodian so that we can run VASP and LOBSTER now with a minimal setup on 1 node. Users can use this new option once the new custodian version is required and #723 is merged.
I would love to advertise this also in the new atomate2 paper, as this now enables us to use the full capabilities of jobflow with the LOBSTER workflow as well. Of course, specialists might want to run VASP on more than one node. However, in most use cases, this version should be sufficient. And, we might attract a few new atomate2 users in this way.