S4D Sidekit For Diarization
PREREQUISITES
Sidekit for Diarization requires the following software installed for your platform:
[Python](http://www.python.org)
[NumPy](http://www.numpy.org/)
[Scipy](http://http://www.scipy.org/)
[Pandas](http://http://www.pandas.org/)
[Sphinx 1.1.0 or newer](http://http://sphinx-doc.org/) to build the documentation
[SIDEKIT](https://lium.univ-lemans.fr/sidekit/)
INSTALLATION
We recommend the use of a virtual environment (e.g. [Miniconda](https://conda.io/miniconda.html) or [Virtualenv](https://virtualenv.readthedocs.io/en/latest/)).
TUTORIALS
Once your installation is complete, you can take a look at the [tutorials](https://git-lium.univ-lemans.fr/Meignier/s4d/tree/master/tutorials).
- Authors:
Sylvain Meignier & Anthony Larcher & Pierre-Alexandre Broux & Florent Desnous
- Version:
0.1.4.1 of 2020/01/23
Metadata
Release files for s4d 0.2.6
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 |
|---|---|---|---|---|
| s4d-0.2.6.tar.gz | 98.1 kB | Without provenance | Details for s4d-0.2.6.tar.gz |
Release files / s4d-0.2.6.tar.gz
| Download URL | s4d-0.2.6.tar.gz |
|---|---|
| Size | 98.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d16bfb2c1d0340b28ec839759a8dc3ef2b355fefc562da162d07fa366821758
|
|
BLAKE2b-256 checksum How to use checksums |
78528ed570399c12f2ca099967f6e9d9684f4d3e0fb44923ff69be7ea032f1a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for s4d 0.2.6
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.