Release v2.3.0 #169
Merged
Release v2.3.0 #169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
- Allow to set energy range from input - Fix input of 'retrieve_kkrflex' - Cleanup in workflow
- Fix error where process gets stuck due to label being too long (255 max numbe rof chars) - Add possibility to use custom scanning positions via 'scan_positions' entry in 'tip_position' input dict
…to correctly generate the rotation matrices
…e impurity parser in the dos mode
- allow to set shapefun in voronoi calculation from input - set kkrflex_llyfac from wfac_renorm - minor bugfix in gf_writeout which can now also start from a voronoi run
…he correct np.array format if the key 'imp_cls' was alreday present
…ctly use the 'noco_angles' and assign these angles for the vacuum sites. Also a robustness update was made if the imp info is already in the cls format it is able to work with that
… a description for what they do
- fix offset position (removed modulo 1 in `tools/tools_STM_scan.py`->`get_r_offset`) - removed code duplication by `self.get_tip_position_dict(da, db)` in `workflows/kkr_STM.py` - corrected confusing names of functions (combine_potentials`->`combine_imp_info` and `combine_nodes`->`combine_potentials`) - corrected deduplication checking of cluster positions (`pos_exists_already` needed `clust_offset` input instead of position without layer offset)
…ew version of a helper function in the kkr_STM
- take care of edge case where Zimp is not a list but a number (happens for single impurity case without specification of imp_cls input) - fix renaming params_kkr_overwrite -> params_overwrite
… without embedding any sites
Update to latest released version
Taken from original location: JuDFTteam/judft_tutorials@89f6286
Development of STM workchain
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #169 +/- ##
==========================================
+ Coverage 59.41% 68.51% +9.10%
==========================================
Files 102 104 +2
Lines 14606 14850 +244
==========================================
+ Hits 8678 10175 +1497
+ Misses 5928 4675 -1253 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release v2.3.0
Description of important changes
Checklist for next release
developbranchaiida_kkr/__init__.py,pyproject.toml,.bumpversion.cfg)If everything is done, you can merge your changes from
developback intomasterand create a tag for the new version number. Creating a new tag always triggers publication to pypi (see.github/workflows/cd.ymlfor the definition of this github action).