be-datahive
Python library for the BE-dataHIVE API.
Installation
be_datahive is available on
PYPI. Install with pip:
pip install be_datahive
Get Started
Create an api object for interacting with the API:
from be_datahive import be_datahive
api = be_datahive()
Obtain efficiency & bystander data:
efficiency_data = api.get_efficiency()
bystander_data = api.get_bystander()
Convert efficiency & bystander data into machine-ready arrays:
ef_features, ef_target, variable_info = api.get_efficiency_ml_arrays(efficiency_data, target_col = "efficiency_full_grna_reported", encoding='hilbert-curve', clean=True, flatten=True)
by_features, by_target, variable_info = api.get_bystander_ml_arrays(bystander_data, encoding='one-hot', bystander_type = 'edited', clean=True, flatten=True)
API Documentation
The Python wrapper uses the BE-dataHive API which is accessible at the endpoint (https://api.be-datahive.com). The detailed API documentation, describing all endpoints, query parameters, and response schema, can be viewed here.
Troubleshooting
If you encounter any issues while using the be_datahive library, please refer to the common issues listed below:
- Installation issues: Make sure you have the latest version of
pipand Python installed. Usepip install --upgrade pipto upgrade pip if necessary. - API Connection Errors: Check your internet connection and ensure that the API endpoint (https://api.be-datahive.com) is reachable.
- Data Retrieval Issues: Ensure that you are using the correct function names and parameters as outlined in the documentation.
If your issue is not listed here or you need further assistance, please open an issue on GitHub or reach out directly.
Reporting Issues
If you have any problems, you can open an issue on GitHub in the following format:
Title: [Brief description of the issue]
Description:
- Summary: A detailed description of the issue.
- Steps to Reproduce: Step-by-step instructions to reproduce the issue.
- Expected Result: What you expected to happen.
- Actual Result: What actually happened.
- Software: Operating system and Python version.
- Additional Information: Any other information that may help us resolve the issue.
Alternatively, you can reach out directly to Lucas Schneider at lucas.schneider@cs.ox.ac.uk.
Citation
When using the BE-dataHIVE API, please cite our paper as outlined below.
@article{Schneider.2023,
title = "BE-dataHIVE: a Base Editing Database",
author = "Lucas Schneider, Peter Minary",
year = "2024",
}
Metadata
Release files for be-datahive 0.1.4
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 | |
|---|---|---|---|---|
| be_datahive-0.1.4.tar.gz | 5.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| be_datahive-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / be_datahive-0.1.4.tar.gz
| Download URL | be_datahive-0.1.4.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d3de3c81913f8d631fbfa84adf58b2838a310d2e2ad8d4bc97f0c44bbba5d0a
|
|
BLAKE2b-256 checksum How to use checksums |
304871a4cf6f6ee1f340aecba70b86b278f1e98bf4c765d32863042fd507c0e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Release files / be_datahive-0.1.4-py3-none-any.whl
| Download URL | be_datahive-0.1.4-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25e74c2e747afc36b49afabbd91a82b868738f1ec05c23c798b2d330b09589bf
|
|
BLAKE2b-256 checksum How to use checksums |
5f448b1544136e5b844a61dfa9633093c6343673a4564b71ce304951650957e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Security for be-datahive 0.1.4
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.