INSTALLATION
The configuration is performed with cmake. You will need cmake (version 3.12 or later installed). The installation of the python components is performed with pip.
To install cmake and update your version of pip, you can run:
USERBASE=$(python3 -m site --user-base)
USERSITE=$(python3 -m site --user-site)
export PATH="${USERBASE}/bin:${PATH}"
export PYTHONPATH="${USERSITE}:${PYTHONPATH}"
python3 -m pip install pip --upgrade --user
python3 -m pip install cmake --upgrade --user
You should consider adding the above export commands to your ${HOME}/.bashrc and then source ~/.bashrc.
If, for whatever reason, pip is unavailable on your system, you can install it using the directions here: https://pip.pypa.io/en/stable/installation/
To install ndfes:
cd build
bash ./run_cmake.sh
make install VERBOSE=1 -j4
cd ../local
export PATH="${PWD}/bin:${PATH}"
export PYTHONPATH="${PWD}/lib/python3.XX/site-packages:${PYTHONPATH}"
where python3.XX should be replaced by the appropriate python version.
ndfes has dependencies on blas/lapack and nlopt. The cmake configuration will check if these libraries are available. If they are not available, it will automatically download them from github and install them.
- The blas/lapack libraries are installed from the openblas package.
- The nlopt software is used to perform nonlinear optimizations.
These libraries could also be installed globally using your system’s package manager. For example, on Fedora, you could install them with:
sudo dnf install NLopt-devel openblas
See the contents of build/run_cmake.sh to see how you can adjust the compilers, compiler flags, python interpreter, and installation directory.
Metadata
Release files for ndfes 3.6.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ndfes-3.6.10-py2.py3-none-musllinux_1_2_x86_64.whl | Python 3, Python 2 | none | Linux musl 1.2+ x86-64 | Details for ndfes-3.6.10-py2.py3-none-musllinux_1_2_x86_64.whl |
| ndfes-3.6.10-py2.py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | Python 2, Python 3 | none | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details for ndfes-3.6.10-py2.py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
Total release size: 44.5 MB
Release files / ndfes-3.6.10-py2.py3-none-musllinux_1_2_x86_64.whl
| Download URL | ndfes-3.6.10-py2.py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 23.3 MB |
| Tags | Linux musl 1.2+ x86-64 Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b4b3a812f0c76ee53d5de4f9287b9fe4b89ff86500f6a50194bb63c9c4b81206
|
|
BLAKE2b-256 checksum How to use checksums |
459df2d2abb508aae5087623c808b781e3813ebe7944d457777346e7800139af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / ndfes-3.6.10-py2.py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | ndfes-3.6.10-py2.py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 21.2 MB |
| Tags | Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
08f707cdc0d0c866ea72360cfbc0f2509b91ffb3fa2f3a0adf596666ead1bd44
|
|
BLAKE2b-256 checksum How to use checksums |
e1c514bbd5dd133ab42f6c43973fb0a4db94e756bbc1a9b9cdb62669d3eb30c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for ndfes 3.6.10
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.