You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# If you have trouble cloning repo, replace "github.com" with "gitee.com".
18
23
CMD mpirun --use-hwthread-cpus abacus
19
24
20
-
# To run ABACUS built by this image with all available threads, execute `docker run -v <host>:<wd> -w <wd/input> abacus`.
25
+
# To run ABACUS built by this image with all available threads, execute `docker run -v <host>:<wd> -w <wd/input> abacus:latest`.
21
26
# Replace '<host>' with the path to all files(including pseudopotential files), '<wd>' with a path to working directory, and '<wd/input>' with the path to input folder(containing 'INPUT', 'STRU', etc.).
22
-
# e.g. after clone the repo to `$HOME` and pulled this image, execute `docker run -v ~/abacus-develop/tests/integrate:/workspace -w /workspace/101_PW_15_f_pseudopots abacus`.
23
-
# To run ABACUS with a given MPI process number, execute `docker run -v <host>:<wd> -w <wd/input> -it --entrypoint mpirun abacus -np <processes> abacus`. Note: the first "abacus" is the name of the image, the second "abacus" is the name of the executable file. Do not use '--cpus' flag of 'docker run' to specify the number of processes.
27
+
# e.g. after cloning the repo to `$HOME` and pulling image, execute `docker run -v ~/abacus-develop/tests/integrate:/workspace -w /workspace/101_PW_15_f_pseudopots abacus:latest`.
28
+
# To run ABACUS with a given MPI process number, execute `docker run -v <host>:<wd> -w <wd/input> -it --entrypoint mpirun abacus:latest -np <processes> abacus`.
29
+
# Note: It would be better using all available CPUs. Docker uses CFS to share the CPU resources, which will result in bad CPU affinity.
24
30
25
31
# To use this image as developing environment, execute `docker run -it --entrypoint /bin/bash abacus`.
26
32
# Please refer to https://docs.docker.com/engine/reference/commandline/run/ for more details.
Copy file name to clipboardExpand all lines: README.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ The following files are the central input files for ABACUS. Before executing the
95
95
96
96
- The numerical orbital files
97
97
98
-
This part is only required in LCAO calculations.
98
+
This part is only required in LCAO calculations.
99
99
The filename for each element’s numerical orbital basis needs to be specified in the STRU file, together with the directory of the orbital files unless they are already present in the working directory.
100
100
ABACUS provides numerical atomic basis sets of different accuracy levels for most elements commonly used. Users can download these basis sets from the [website](http://abacus.ustc.edu.cn/pseudo/list.htm). Moreover, users can generate numerical atomic orbitals by themselves, and the procedure is provided in this [short introduction](docs/generate-basis.md).
101
101
@@ -136,7 +136,7 @@ into which the following output files will be generated:
136
136
[back to top](#readme-top)
137
137
138
138
## Hands-on examples
139
-
The following provides basic sample jobs in ABACUS. More can be found in the directories `examples/` and `tests/`, with an introduction [here](tests/README.md), and the corresponding reference outputs can be found in the file `result.ref` under each subdirectory.
139
+
The following provides basic sample jobs in ABACUS. More can be found in the directories `examples/` and `tests/`, and the corresponding reference outputs can be found in the file `result.ref` under each subdirectory.
140
140
141
141
*Note that the examples there are intended as quick hands-on jobs, and the results are NOT converged with regard to basis set or k point sampling.*
142
142
@@ -171,13 +171,13 @@ The following references are required to be cited when using ABACUS. Specificall
171
171
-**For general purpose:**
172
172
173
173
[1]. Mohan Chen, G. C. Guo, and Lixin He. "Systematically improvable optimized atomic basis sets for ab initio calculations." Journal of Physics: Condensed Matter 22.44 (2010): 445501.
174
-
174
+
175
175
[2]. Pengfei Li, et al. "Large-scale ab initio simulations based on systematically improvable atomic basis." Computational Materials Science 112 (2016): 503-517.
176
176
177
177
-**If Stochastic DFT is used:**
178
178
179
179
[1]. Qianrui Liu, and Mohan Chen. "Plane-Wave-Based Stochastic-Deterministic Density Functional Theory for Extended Systems." https://arxiv.org/abs/2204.05662.
180
-
180
+
181
181
-**If DFT+U is used:**
182
182
183
183
[1]. Xin Qu, et al. "DFT+ U within the framework of linear combination of numerical atomic orbitals." The Journal of Chemical Physics (2022).
@@ -189,17 +189,17 @@ The following references are required to be cited when using ABACUS. Specificall
189
189
-**If berry curvature calculation is used in LCAO base:**
190
190
191
191
[1]. Gan Jin, Daye Zheng, and Lixin He. "Calculation of Berry curvature using non-orthogonal atomic orbitals." Journal of Physics: Condensed Matter 33.32 (2021): 325503.
192
-
192
+
193
193
-**If DeePKS is used:**
194
194
195
195
[1]. Wenfei Li, Qi Ou, et al. "DeePKS+ABACUS as a Bridge between Expensive Quantum Mechanical Models and Machine Learning Potentials." https://arxiv.org/abs/2206.10093.
196
-
196
+
197
197
-**If hybrid functional is used:**
198
-
198
+
199
199
[1]. Peize Lin, Xinguo Ren, and Lixin He. "Efficient Hybrid Density Functional Calculations for Large Periodic Systems Using Numerical Atomic Orbitals." Journal of Chemical Theory and Computation 2021, 17(1), 222–239.
200
-
200
+
201
201
[2]. Peize Lin, Xinguo Ren, and Lixin He. "Accuracy of Localized Resolution of the Identity in Periodic Hybrid Functional Calculations with Numerical Atomic Orbitals." Journal of Physical Chemistry Letters 2020, 11, 3082-3088.
202
-
202
+
203
203
[back to top](#readme-top)
204
204
205
205
# Development team
@@ -232,4 +232,3 @@ If you find a bug or have some questions, please refer to our GitHub [issue trac
Copy file name to clipboardExpand all lines: docs/features.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ In the INPUT file, the keyword basis_type controls what basis type to use:
34
34
35
35
The default value of basis_type is pw. When choosing lcao or lcao_in_pw, the user should prepare atomic orbitals first.
36
36
37
-
Information on the keyword basis_type can also be found in [the list of input keywords](input-main.md#basis-type).
37
+
Information on the keyword basis_type can also be found in [the list of input keywords](input-main.md#basis_type).
38
38
39
39
We also provide a [detailed instruction](generate-basis.md) on generating basis functions.
40
40
@@ -43,7 +43,7 @@ We also provide a [detailed instruction](generate-basis.md) on generating basis
43
43
## Pseudopotentials
44
44
45
45
Currently ABACUS uses norm-conserving pseudopotentials in the (old) format of UPF, which
46
-
is the standard pseudopotential format for uantum ESPRESSO. To run a calculation, the pseudopotential needs to be set in STRU file. For example:
46
+
is the standard pseudopotential format for Quantum ESPRESSO. To run a calculation, the pseudopotential needs to be set in STRU file. For example:
47
47
48
48
```
49
49
ATOMIC_SPECIES
@@ -63,7 +63,7 @@ vectors of the supercell are set in the STRU file.
63
63
64
64
For the input k-point (KPT) file, the file should either contain the k-point coordinates and weights or the mesh size for creating the k-point gird. Both options are allowed in ABACUS.
65
65
66
-
More information on k-points is provided in this [instruction](#docs/input-kpt.md)
66
+
More information on k-points is provided in this [instruction](input-kpt.md)
67
67
68
68
[back to top](#features)
69
69
@@ -86,7 +86,7 @@ hpseps can not be used with plane wave basis.
86
86
87
87
Then the user has to correct the input file and restart the calculation.
88
88
89
-
Information on the keyword ks_solver is also given in the [list of input variables](input-main.md#ks-solver).
89
+
Information on the keyword ks_solver is also given in the [list of input variables](input-main.md#ks_solver).
90
90
91
91
[back to top](#features)
92
92
@@ -126,6 +126,6 @@ The user can set the XC functional type in INPUT file with the parameter, dft_fu
126
126
127
127
If the functional specified by the user is not consistent with the pseudopotential file, the program will stop with an error message.
128
128
129
-
Information on the keyword ks_solver is also given in the [list of input variables](input-main.md#dft-functional).
129
+
Information on the keyword ks_solver is also given in the [list of input variables](input-main.md#dft_functional).
0 commit comments