python-unf
unf contains Python code for Universal Numeric Fingerprints (UNFs).
UNFs are defined at http://guides.dataverse.org/en/latest/developers/unf/index.html.
Usage:
>>> import unf
>>> unf.unf(1.23456789)
'UNF:6:vcKELUSS4s4k1snF4OTB9A=='
>>> unf.unf(1.23456789, 9)
'UNF:6:N9:IKw+l4ywdwsJeDze8dplJA=='
Basic usage
UNFs are calculated according to UNF Version 6 (1).
The number of rounding digits can be specified, but the string truncation length and the hash truncation length are fixed to the specification defaults (128 bytes and 128 bits, respectively).
None can be used to indicate a missing value, so to match the
example "Vector (numeric): {1.23456789, <MISSING VALUE>, 0}"
(1), use:
>>> unf.unf([1.23456789, None, 0])
'UNF:6:Do5dfAoOOFt4FSj0JcByEw=='
Existing implementations include IQSS/UNF (2) and the R UNF package (3). The data structures supported by these implementations require sequences containing values of a single data type. Although the UNF specification does not explicitly allow or forbid it, this implementation does allow sequences containing multiple basic data types. Compound sequences (sequences containing sequences) are forbidden for native Python data types.
NumPy support
NumPy arrays are supported:
>>> unf.unf(numpy.array([1, 2, 3]))
'UNF:6:AvELPR5QTaBbnq6S22Msow=='
Only numeric NumPy data types are supported.
Note that 2-D NumPy arrays are interpreted as collections of vectors and are subject to the digest-sort-digest rule for "higher-level objects" (1). So:
numpy.array([[1, 2], [3, 4]])is treated as a collection of vectors[1, 2]and[3, 4]and will be evaluated the same way as a data frame with two variables. This will therefore evaluate to the same UNF asnumpy.array([[3, 4], [1, 2]])), so the UNF is not suitable for matrices.numpy.array([[1, 2]])is interpreted as a collection of one vector and evaluates to the same UNF as the vector itself,numpy.array([1, 2]).numpy.array([[1], [2]])is treated as a collection of two (one-element) vectors.
Primitives (non-arrays) with NumPy data types and arrays of greater than two dimensions are not supported.
Note that NumPy does not have a special indicator for a missing
value. If we try to use None as we did in the pure Python example,
we find that NumPy translates it to nan:
>>> a = numpy.array([None], dtype=float)
>>> a
array([nan])
which is itself a special value (distinct from a missing value) where UNFs are concerned. NumPy arrays should therefore not be used when data is missing.
pandas support
pandas series and data frames are supported:
>>> unf.unf(pandas.Series([1, 2, 3]))
'UNF:6:AvELPR5QTaBbnq6S22Msow=='
>>> unf.unf(pandas.DataFrame({'a': [1, 2, 3], 'b': [4, 5, 6]}))
'UNF:6:Np0sj111a+rrJBgl6wNF9w=='
Only numeric data types are supported.
Behavior on multi-indexed data frames is undefined.
pandas does have an indicator for missing values (pandas.NA), but
its use requires a series of data type object, which is not
supported. And like NumPy, pandas translates None to NaN, so
there is no unambiguous way to indicate missing data in pandas.
pandas objects should therefore not be used when data is missing.
References
1: https://guides.dataverse.org/en/latest/developers/unf/unf-v6.html
2: https://raw.githubusercontent.com/IQSS/UNF/master/doc/unf_examples.txt
3: https://github.com/leeper/UNF
See also
Please see ROUNDING.md for a note about rounding.
Metadata
Release files for unf 0.11.0
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 | Actions |
|---|---|---|---|---|
| unf-0.11.0.tar.gz | 14.5 kB | Without provenance | Details for unf-0.11.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| unf-0.11.0-py3-none-any.whl | Python 3 | none | any | Details for unf-0.11.0-py3-none-any.whl |
Total release size: 21.4 kB
Release files / unf-0.11.0.tar.gz
| Download URL | unf-0.11.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcd160d1a71fad42b917469ef8e476a105d2cd51340fa71fe9d2ecb67986471b
|
|
BLAKE2b-256 checksum How to use checksums |
0b8e29971eb45a95e15a8dff218fd6555ae5314c3a0bce1ec914428f7759d296
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Release files / unf-0.11.0-py3-none-any.whl
| Download URL | unf-0.11.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5fcd3ccf0da9636b8d629d4604b37a16a881b5e528623823b5b5db594312d56
|
|
BLAKE2b-256 checksum How to use checksums |
d25b85fce6b41bf562ef1e6e05214ed76323d7c9807874783c06102bfa8484ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Security for unf 0.11.0
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.