cython_bbox is widely used in object detection tasks. To my best knowledge, it was first implemented in [Faster-RCNN](https://github.com/rbgirshick/py-faster-rcnn). Since then, almost all object detection projects use the source code directly.
In order to use it in standalone code snippets or small projects, I make it a pypi module. The `cython_bbox.pyx` is totally borrowed from [Faster-RCNN](https://github.com/rbgirshick/py-faster-rcnn). Thanks [RBG](http://www.rossgirshick.info/)!
## install
```
pip install cython_bbox
```
## usage
```
from cython_bbox import bbox_overlaps
overlaps = bbox_overlaps(
np.ascontiguousarray(dt, dtype=np.float32),
np.ascontiguousarray(gt, dtype=np.float32)
)
```
Metadata
Release files for cython-bbox 0.1.3
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 | |
|---|---|---|---|---|
| cython_bbox-0.1.3.tar.gz | 41.3 kB | Without provenance | Details |
Release files / cython_bbox-0.1.3.tar.gz
| Download URL | cython_bbox-0.1.3.tar.gz |
|---|---|
| Size | 41.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82e2d887534ecc10d3507489a05b11259f3baacd29eee37e6d8c97e1ffb16554
|
|
BLAKE2b-256 checksum How to use checksums |
fab9fc7d60e8c3b29cc0ff24a3bb3c4b7457e10b7610fbb2893741b623487b34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.9.1 setuptools/24.0.3 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/2.7.11
|
Security for cython-bbox 0.1.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.