D3TaLES API
API designed for the D3TaLES project. Includes data processing, database access functions, and property calculators.
Website with full documentation for the D3TaLES API can be found here.
Modules
This API contains three modules:
D3database: Interface for interacting with the D3TaLES databases. Includes queries, data insertion with validation, and a REST API interface.Processors: Processing code for extracting data from computational and experimental data files as well as ExpFlow run objects.Calculators: Property calculators and plotters for cyclic voltammetryWorkflows: Fireworks workflow for the D3TaLES databases high throughput workflows
Installation
PIP Install
This module can be installed with pip install by running the following code:
pip install git+https://github.com/d3tales/d3tales_api.git
Installation Notes:
- If your python version is greater than 3.8, then you will need to install pymatgen directly into the environment you are working in. It is best to use conda for this.
- If you plan to use any NLP parsers, you will need to install ChemDataExtractor2 with
pip install ChemDataExtractor2. Dependency conflicts make it necessary to install separately.
Environment Variables
Note that many operation require a DB_INFO_FILE environment variable. This environment variable
should be a path to a JSON file containing connection information for the databases. The keys should
be the database names such as frontend, backend, expflow, and fireworks. An example
can be found at db_info_ex.json.
To set this variable run:
export DB_INFO_FILE=$PWD/db_infos_ex.json
You can also set a GROUP_FILE environment variable. This should point to a json
file containing source_group tag names. This is optional.
To set this variable run:
export GROUP_FILE=$PWD/group_file_ex.json
REST API (d3tales_api.restapi.RESTAPI) will use UPLOAD_USER and UPLOAD_PASS environment
variables if username and password arguments are not provided. These environment variables
can be set in the same was as the DB_INFO_FILE variable.
Metadata
Release files for d3tales-api 0.2.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 |
|---|---|---|---|---|
| d3tales_api-0.2.0.tar.gz | 83.2 kB | Without provenance | Details for d3tales_api-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| d3tales_api-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for d3tales_api-0.2.0-py3-none-any.whl |
Total release size: 171.7 kB
Release files / d3tales_api-0.2.0.tar.gz
| Download URL | d3tales_api-0.2.0.tar.gz |
|---|---|
| Size | 83.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b5804584c201246e942c8f8f84ac055a67b1622fe0fda8ad9d60c48fa063b23
|
|
BLAKE2b-256 checksum How to use checksums |
77f05f717432162b0dd5ae928cc38322d5e73a8ecd119e75339a8f98816ce516
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.5
|
Release files / d3tales_api-0.2.0-py3-none-any.whl
| Download URL | d3tales_api-0.2.0-py3-none-any.whl |
|---|---|
| Size | 88.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28c262be4fe9826705231ef13b2f3c86bef40745ac3182a19dae72bf5d2a46af
|
|
BLAKE2b-256 checksum How to use checksums |
02269e9234d1449962e49dc075078eb896cb1007bf6729f9270d0795e5266302
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.5
|
Security for d3tales-api 0.2.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.