Torch-CPD
Pytorch Implementation of the Coherent Point Drift Algorithm.
Introduction
This is a PyTorch re-implementation of the excellent pycpd package, which implements the Coherent Point Drift (CPD) algorithm. Only Rigid and Deformable Registration and currently implemented. The default is to use CUDA to speed up computation, which is significantly faster than pure Numpy. Refer to the pycpd package for examples of how to use CPD for registration.
Installation
Install from PyPI
You should install torch separately, follow instructions at https://pytorch.org/get-started/locally/
pip install torchcpd
Installation from Source
git clone https://github.com/ramtingh/torchcpd.git $HOME/torchcpd
Install the package:
pip install .
Metadata
Release files for torchcpd 1.0.2
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 | |
|---|---|---|---|---|
| torchcpd-1.0.2.tar.gz | 10.2 kB | Without provenance | Details |
Release files / torchcpd-1.0.2.tar.gz
| Download URL | torchcpd-1.0.2.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fc3729dc9d61c0dbc8b11fbdfb6eee6469b61ed60cd9b355e03f515cfde9183
|
|
BLAKE2b-256 checksum How to use checksums |
6e52e2c6f1b31d79ad8eb385d964b64644c4cdc2dd4a4e6826effa0248f6e5a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.11.3 pkginfo/1.8.3 requests/2.28.1 requests-toolbelt/0.9.1 tqdm/4.64.1 CPython/3.9.16
|
Security for torchcpd 1.0.2
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.