DataPipelinePackage
To Install the Package
From the internet for use elsewhere:
$ pip install ecopipeline
Requires Python 3.11. The package pins numpy to the 1.24 series and pandas below 2.0; installing it will downgrade a newer numpy in the target environment.
For Development
This repository uses uv. From the DataPipelinePackage directory:
uv sync # build .venv from uv.lock
uv run pytest # run the test suite
Using the Package
See https://ecotoperesearch.github.io/DataPipelinePackage/build/html/index.html for documentation
config.ini
- database
- user: username for host database connection
- password: password for host database connection
- host: name of host
- database: name of database
- minute
- table_name: name of table to be created in the mySQL database containing minute-by-minute data
- hour
- table_name: name of table to be created in the mySQL database containing hour-by-hour data
- day
- table_name: name of table to be created in the mySQL database containing day-by-day data
- input
- directory: diretory of the folder containing the input files listed below
- site_info: name of the site information csv
- 410a_info: name of the 410a information csv
- superheat_info: name of the superheat infomation csv
- output
- directory: diretory of the folder where any pipeline output should be written to
- data
- directory: diretory of the folder from which extract loads the raw sensor data
- fieldManager_api_usr: Username for Field Manager API if extracting data through that medium
- fieldManager_api_pw: Password for Field Manager API if extracting data through that medium
- fieldManager_device_id: Device ID for Field Manager API if extracting data through that medium
Unit Testing
To run Unit tests, run the following command in the terminal in the corresponding directory:
uv run pytest
2 maintainers
Metadata
2 maintainers
Release files for ecopipeline 2.4.2
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 | |
|---|---|---|---|---|
| ecopipeline-2.4.2.tar.gz | 746.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ecopipeline-2.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / ecopipeline-2.4.2.tar.gz
| Download URL | ecopipeline-2.4.2.tar.gz |
|---|---|
| Size | 746.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c831ccd13b9d2af21252306a3689903bf388e01b0929314c7c9a2a3d0b7ec4b8
|
|
BLAKE2b-256 checksum How to use checksums |
702011b86305109a79a463ab5c554d9bb5b3674a95872bcf4f2b0c2bd86b9a35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / ecopipeline-2.4.2-py3-none-any.whl
| Download URL | ecopipeline-2.4.2-py3-none-any.whl |
|---|---|
| Size | 793.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d722c8dbd6cace33743c2cfcfaee699d09de049f2dd0c06d39a22be24c83a23f
|
|
BLAKE2b-256 checksum How to use checksums |
18fb49f20169196767ea883752093d5a2d05609b87818795880ce34af6432157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for ecopipeline 2.4.2
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.
