Skip to content

Releases: JuDFTteam/aiida-kkr

v2.3.1

05 Dec 15:11
Compare
Choose a tag to compare

Check the full changelog for important changes: v2.1.0...v2.3.1

v2.1.0

13 Nov 13:23
843b408
Compare
Choose a tag to compare

Important changes:

  • add support for BdG calculations in impurity code
  • add imp_BdG workflow
  • some bugfixes
  • allow to deactivate SOC in impurity run with new solver
  • update tests to aiida-core v2.3.0
  • update dependencies
  • improve LDA+U capabilities

v1.1.13: Merge pull request #117 from JuDFTteam/develop

06 Apr 11:05
19feee5
Compare
Choose a tag to compare

v1.1.12: Merge pull request #109 from JuDFTteam/develop

22 Aug 13:47
914bdc4
Compare
Choose a tag to compare

v1.1.11.post1: Remove aiida-testing dependency from testing extras

21 Jul 14:35
Compare
Choose a tag to compare

Bugfixes

12 Feb 09:13
Compare
Choose a tag to compare
Bugfixes Pre-release
Pre-release

Fixes for bugs #25 and #27

Merge branch 'develop', drop python 3.4 support, bumpversion -> v1.1.10

27 Jan 10:47
Compare
Choose a tag to compare
Dropped support for python 3.4 since the latest AiiDA-core requires graphviz==0.13 which is not available there

Release for aiida-core v1.0.0

31 Oct 12:45
Compare
Choose a tag to compare
v1.1.9

Merge branch 'develop', bumpversion -> v1.1.9

Fix pypi publishing

18 Mar 14:39
Compare
Choose a tag to compare

Fixed publishing step to pypi (poetry forgot about the entrypoints).

Unification of workflow input nodes

15 Mar 13:52
Compare
Choose a tag to compare

Important changes:

  • consistent naming conventions for workflow input nodes:
    • computer options: options (respective entries are always: 'queue_name', 'resources', 'max_wallclock_seconds', 'custom_scheduler_commands' , 'use_mpi')
    • names for JuKKR code input nodes : kkr (KKRhost), voronoi, kkrimp
    • if there is only one RemoteData input node for the workflow, the name should be remote_data, for more than one: remote_data_{...}
    • general workflow parameter input nodes should always be named wf_parameters
    • the impurity information node for impurity embedding is always named impurity_info
  • consistent naming conventions for workflow output nodes:
    • general information about the workflow run should be stored in a workflow_info ParameterData node
  • fix auto tests