-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated changes in the documentation due to the restructuring
- Loading branch information
Showing
7 changed files
with
71 additions
and
55 deletions.
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,4 +5,3 @@ cd skw | |
make | ||
make lib | ||
cd .. | ||
|
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,56 +1,68 @@ | ||
Installing | ||
========== | ||
|
||
Please consult the :file:`setup.py` file for details on | ||
how to configure the location of the include and libraries. | ||
Basic install | ||
------------- | ||
First make sure Spglib is installed | ||
|
||
Only Spglib (in principle the only requirement for minimal | ||
functionality against calculations based on first-principle | ||
data) is included as a Git submodule. This can be activated by | ||
:: | ||
|
||
pip install spglib | ||
|
||
Then install T4ME by executing the command | ||
|
||
:: | ||
|
||
git submodule init | ||
git submodule update | ||
pip install t4me | ||
|
||
This will give the user the posibility to calculate the transport coefficients | ||
using integration routines in SciPy. For other integration and interpolation routines | ||
the user needs to follow the following recipe. | ||
|
||
Advanced install | ||
---------------- | ||
For more advanced functionality (interpolation and other integration routines) the | ||
user should determine which external libraries are needed and install them based | ||
on their respective documentation. | ||
|
||
The :file:`setup.py` file assume in its supplied form that the user installs the libraries | ||
in the standard folders, e.g. `$HOME/include` and `$HOME/lib` for the include and library | ||
files, respectively. If other locations are needed, please adapt the :file:`setup.py` | ||
file. | ||
|
||
And Spglib can be build with the included :file:`build_spglib` | ||
As an example, we want to enable the tetrahedron integration. A Spglib interface needs to be compiled. | ||
This can be build with the included :file:`build_spglib` file. | ||
|
||
:: | ||
|
||
./build_spglib | ||
|
||
It is possible to build Spglib elsewhere, but consult | ||
:file:`build_spglib` and make sure that the | ||
:file:`tetrahedron_method.h` is also inside the include | ||
directory. For instance, if access to Git is difficult one | ||
should make a `spglib` folder in the main T4ME directory | ||
and place a recent Spglib version there. This would give the | ||
same data structure as if using the Git submodule. | ||
The build script :file:`build_spglib` can then be executed. | ||
If that was successfull, T4ME can then be built by issuing the following command | ||
|
||
All other libraries need to be built externally and linked in. | ||
:: | ||
|
||
pip install . | ||
|
||
Then execute | ||
or | ||
|
||
:: | ||
|
||
python setup.py build_ext --inplace | ||
pip install -e .[dev] | ||
|
||
To build the necessary parts of interfaces used in T4ME. You should | ||
now be able to now execute t4me.py which is | ||
the main driver routine | ||
Another example. We want to enable SKW interpolation. The SKW routines can be built (assuming Intel MKL is installed) by issuing | ||
|
||
:: | ||
|
||
python t4me.py | ||
./build_skw | ||
|
||
This should execute cleanly. However, it might be usefull | ||
to run T4ME from other locations. In order to for this to | ||
work, the main directory of T4ME needs to be added to | ||
your ``PYTHONPATH`` environmental variable. Usually, this can | ||
be done (in bash) by adding the following to your | ||
:file:`.bashrc` or :file:`.bash_profile` | ||
If successfull, T4ME can then be installed by issuing one of the two commands listed above. If other FFT routines are to be used, please modify :file:`skw/Makefile`. | ||
|
||
All other libraries need to be built externally and linked in. | ||
|
||
Upon successfull completion of the installation, T4ME is executed with the command | ||
|
||
:: | ||
|
||
export PYTHONPATH=$PYTHONPATH:/home/username/somepath/t4me | ||
t4me | ||
|
||
An `input` directory is needed which should contain the input files. |
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,17 @@ | ||
Running tests | ||
============= | ||
|
||
Several tests are included, which can be used to test the installation, | ||
but more importantly assist in verify development steps. | ||
Several tests are included, which can be used to test the installation. | ||
|
||
Currently only basic functionality is tested and developers | ||
are encouraged to write tests for any added functionality. | ||
|
||
Tests can be run by setting the ``run_tests`` in the general parameter file, | ||
typically the file :file:`param.yml`. | ||
Tests are executed by issuing | ||
|
||
Most of the tests rely on the GSL library, so please install it. | ||
:: | ||
|
||
pytest | ||
|
||
In the base directory. | ||
|
||
Most of the tests rely on the GSL library, so please install it. If it is not present the tests relying on this will skip. |