pyAbacus
pyAbacus is built to simplify the usage of Tausand Abacus family of coincidence counters, providing a library aimed to interface these devices using Python coding.
Written in Python3, pyAbacus relies on the following modules:
- pyserial
Library version: 1.2.1
Original release date: 12/28/2017 (mm/dd/yyyy)
Current release date: 06/11/2024
Supported models: AB1002, AB1004, AB1502, AB1504, AB2502, AB2504.
About Tausand Abacus AB1000
This is a family of coincidence counters, ideal to measure temporal correlations in particle detection and quantum optics experiments.
To learn more about them, visit our website www.tausand.com
To obtain a Tausand's Abacus coincidence counter, visit our online shop or contact us at sales@tausand.com
Installation
pyAbacus can be installed using pip as:
pip install pyAbacus
Or from GitHub
pip install git+https://github.com/Tausand-dev/PyAbacus.git
Examples and documentation
To learn how to use pyAbacus, take a look at the examples folder and run the scripts after you've installed pyAbacus. For more details on how to run this library, read PyAbacus_Documentation.pdf or navigate the HTML version located at docs/build/html/index.html.
For developers
Clone the GitHub repository and then follow the next steps:
Creating a virtual environment
Run the following code to create a virtual environment called .venv
python -m venv .venv
Activate
- On Unix systems:
source .venv/bin/activate
- On Windows:
.venv\Scripts\activate
Deactivate
deactivate
Installing packages
After the virtual environment has been activated, install required packages by using:
python -m pip install -r requirements.txt
This will allow you to build the documentation using Sphinx.
Editing version number
When a new version is created, the new numbering should be updated in the following files:
- docs/source/conf.py
- pyAbacus/__init__.py
- setup.cfg
Building docs
Go to the docs folder and run
make <command>
Where <command> is one of the following:
latexpdfhtml
To run the latexpdf command you will need a working installation of Latex.
Metadata
Release files for pyAbacus 1.2.1
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 |
|---|---|---|---|---|
| pyabacus-1.2.1.tar.gz | 24.3 kB | Without provenance | Details for pyabacus-1.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyAbacus-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for pyAbacus-1.2.1-py3-none-any.whl |
Total release size: 48.1 kB
Release files / pyabacus-1.2.1.tar.gz
| Download URL | pyabacus-1.2.1.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
712fee837627e602476403a65585cc07e85555d6f086f4aaa809e0711099a4b7
|
|
BLAKE2b-256 checksum How to use checksums |
c5c7a8b7127af9ba7d4b1cdd74ee24d98836469b3fb9dd725b84ff2d120f6bf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Release files / pyAbacus-1.2.1-py3-none-any.whl
| Download URL | pyAbacus-1.2.1-py3-none-any.whl |
|---|---|
| Size | 23.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69671e2d3853f84eca06a73b3ed1e10624473bb6169f716b15f95b92f874d941
|
|
BLAKE2b-256 checksum How to use checksums |
50b6b44f63dee760090462e8fcc1d480c75d5948db77bf3f3c671687f6c24112
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Security for pyAbacus 1.2.1
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.