BayesianOpt4dftu
This code determines the Hubbard U parameters in DFT+U via Bayesian Optimization approach.
Requirements
- Python 3.6+
- NumPy
- Pandas
- ASE (https://wiki.fysik.dtu.dk/ase/)
- pymatgen (https://pymatgen.org/)
- bayesian-optimization https://github.com/fmfn/BayesianOptimization
- Vienna Ab initio Simulation Package (VASP) https://www.vasp.at/
Set up the input file (input.json) before running the code
The input file contains these parts:
-
structure_info : Includes geometry information (such as lattice parameter, lattice vectors, atomic position, etc) of the target materials.
Example based on InAs:
- Lattice_param and cell: define the 2nd to 5th rows in your POSCAR.
"lattice_param": 6.0584, "cell": [ [ 0.0, 0.5, 0.5 ], [ 0.5, 0.0, 0.5 ], [ 0.5, 0.5, 0.0 ] ]- Atoms: Define the atomic positions of each atom in your system and the initial magnetic moment if there is any.
With SOC: "atoms": [ [ "In", [ 0, 0, 0 ], [ 0, 0, 1e-06 ] ], [ "As", [ 0.75, 0.75, 0.75 ], [ 0, 0, 1e-06 ] ] ] Without SOC: "atoms": [ [ "In", [ 0, 0, 0 ], 1e-06 ], [ "As", [ 0.75, 0.75, 0.75 ], 1e-06 ] ]So in this case, there are two atoms in the primitive cell which are located at the position
(0,0,0)and(0.75, 0.75, 0.75). The second term under each atom defines the initial magnetic moment. If the spin-orbit coupling is not included in your calculation, it is just an integer while otherwise it is a (3,) array of each element defines the initial moment of corresponding direction. If the initial moment is 0, it has to be set to a small number to avoid confliction in the ASE. -
general_flags: Includes general flags required in the VASP calculation.
-
scf: Flags required particularly in SCF calculation.
-
band: Flags required particularly in band structure calculation.
-
pbe: Flags required when using PBE as exchange-correlation functional.
-
hse: Flags required when using HSE06 as exchange-correlation functional. The flags can be added or removed. More flag keys can be found in the ASE VASP calculator.
Installation
pip install BayesOpt4dftu
Usage
To run the examples in the example folder, you need to modify the environment settings in the example.py of the selected calculation based on the specs of your system and VASP binary.
I will use /example/2d as an example:
1. Setting environments
Set the running command for VASP executable
VASP_RUN_COMMAND = 'srun -n 54 vasp_ncl'
Define the VASP output file name.
OUTFILENAME = 'vasp.out'
Define the path direct to the VASP pesudoopotential. (P.S. It should be the directory containing the potpaw_PBE folder)
VASP_PP_PATH = '/PATH/TO/THE/PESUDOPOTENTIAL/'
2. Arguments options
--which_u defines which element you would like to optimize the U for. For a unary substance, it has to be (1,). For compounds with over 2 elements, you can set each element to 0 or 1 to switch on/off the optimization for that element. For InAs, when optimizing for both In and As, it will be (1,1).
--br defines band range you would like to include in your Δband. It is a tuple of two integers, which define the number of valence bands and conduction bands from the Fermi level.
--kappa controls the exploration and exploitation when acquisition function sample the next points. Exploitation 0 <-- kappa --> 10 Exploration
--alpha1 and alpha2 are the weight coefficients of Δgap and Δband.
--threshold defines at what accuracy would you stop the BO process.
--urange defines the U parameter range for optimization, currently it's not supported to define different U ranges for different elements.
--import_kpath provides an external listing of high symmetry k-points in case some special k coordinates are not present in the ase library.
--elements defines the elements in your system. It is set for plotting the BO results. If it's a unary substance, it has to be (ele,).
--iteration defines the maximum steps that BO will be performed with.
3. Running the code
After setting up all these stuff, you can simply run the calculation by
cd example/1d
python example.py --arg1 XX --arg2 XX ...
4. Outputs
Once the threshold or the maximum iterations is reached, you will get two output files
u_xx.txt file consists of the U parameters, band gap, and the Δband at each step.
1D_xxx.png or 2D_xxx.png plots showing you the Gaussian process predicted mean and the acquisition function.
Example of BO plots
Optimal U values will be output at the end of entire process based on the interpolation from the predicted mean space. You can also pick up the Us that give you largest objective value from the u.txt file.
Citation
Please cite the following work if you use this code.
[1] M. Yu, S. Yang, C. Wu, N. Marom, Machine learning the Hubbard U parameter in DFT+ U using Bayesian optimization, npj Computational Materials, 6(1):1–6, 2020.
Metadata
Release files for BayesOpt4dftu 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| BayesOpt4dftu-0.1.4.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| BayesOpt4dftu-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / BayesOpt4dftu-0.1.4.tar.gz
| Download URL | BayesOpt4dftu-0.1.4.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a989d4fb8008e277462d13c99dc052fb13a96cd91dad55ee1576bfef3a7a1d0e
|
|
BLAKE2b-256 checksum How to use checksums |
88884969c2e49c9e86802a2232409c3973b6bff4cd296c969796d805d6e67c52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.5.0.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Release files / BayesOpt4dftu-0.1.4-py3-none-any.whl
| Download URL | BayesOpt4dftu-0.1.4-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c435d4b196b7c2170581bd07d213383f54409fd7623a909bc114d1df9b28f069
|
|
BLAKE2b-256 checksum How to use checksums |
d1a358e887bbf4a84a58d71357d3a17c9f53ba990c320a696d9cc63b5570ac46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.5.0.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Security for BayesOpt4dftu 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.