WiPhy
Key Features
The major advantages of this package are highlighted as follows:
- Incredibly fast. It accelerates bit error ratio and average mutual information simulations by using a state-of-the-art Nvidia GPU and the massively parallel algorithms proposed in [1].
- JIT friendly. It dose not rely on any class and object-oriented programming, which is different from the conventional IMToolkit. It is suitable for both PyPy and Numba. Users are free from the nightmare of complex @jitclass decorations.
- Highly reliable. It has been maintained based on test-driven development, as with other high-quality packages. The simulation results have been used by IEEE journal papers.
Disadvantages
- Some methods are not well documented.
Installation Guide
WiPhy is available from the Python official package repository PyPi.
> pip install wiphy
The WiPhy development team welcomes other researchers' contributions and pull requests. In that case, it would be better to install the latest package and activate the editable mode as follows:
> git clone https://github.com/ishikawalab/wiphy/
> pip install -e ./wiphy # this activates the editable mode
If you use Anaconda, you can install WiPhy as follows.
> git clone https://github.com/ishikawalab/wiphy/
> conda develop ./wiphy
The Anaconda version 4.6.0 or above may also allow the following installation commands.
> conda config --set pip_interop_enabled True
> # for typical users
> pip install wiphy
> # for developers
> git clone https://github.com/ishikawalab/wiphy
> pip install -e ./wiphy
The above installation process requires NumPy, Pandas, SciPy, SymPy, Numba, and tqdm, all of which are popular Python packages. Additionally, it is strongly recommended to install CuPy 5.40+. WiPhy is heavily dependent on CuPy to achieve significantly fast Monte Carlo simulations. The key components required by CuPy are listed here. In case CuPy is not installed in your environment, WiPhy uses NumPy only.
Citations
It would be highly appreciated if you cite the following reference when using WiPhy.
- [1] N. Ishikawa, ``IMToolkit: An open-source index modulation toolkit for reproducible research based on massively parallel algorithms,'' IEEE Access, vol. 7, pp. 93830--93846, July 2019.
Of course, if your project relies on CuPy, the following reference is strongly recommended.
- [2] R. Okuta, Y. Unno, D. Nishino, S. Hido, and C. Loomis, ``CuPy: A NumPy-compatible library for NVIDIA GPU calculations,'' in Conference on Neural Information Processing Systems Workshop, Long Beach, CA, USA, December 4--9, 2017.
Metadata
Release files for wiphy 0.9.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wiphy-0.9.3-py3-none-any.whl | Python 3 | none | any | Details for wiphy-0.9.3-py3-none-any.whl |
Release files / wiphy-0.9.3-py3-none-any.whl
| Download URL | wiphy-0.9.3-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09f5ab7c462fe37d37f38dbd0cae52ddefba50c10a143cc3b8d8c065adffe895
|
|
BLAKE2b-256 checksum How to use checksums |
86d2cbc929dd9b95d0a00d7cfb2825f2a4a6b802fce4816fd55f4d2bb73ef377
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.24.0 setuptools/50.3.1.post20201107 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.5
|
Security for wiphy 0.9.3
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.