enram / vptstools

Python library to transfer and convert vertical profile time series data
https://enram.github.io/vptstools/
MIT License
4 stars 1 forks source link

WIP: Integrate data repo transfer2022 #9

Closed stijnvanhoey closed 2 years ago

stijnvanhoey commented 2 years ago

Code from the currently running data transfer service integrated in the repo with minimal adjustments. With this PR, we have all the current code for the aloft data service together (which was spread into this repo, the odimh5 and data-repository repos).

To make sure users who just want to use the odimh5 functionalities and are not interested in the data transfer services, the package dependencies used for the data transfer are defined as extras_require with the transfer ID. AS mentioned in the updates README.md, user can either install the package without pip install vptstools or with pip install vptstools[transfer] transfer dependencies.

coveralls commented 2 years ago

Pull Request Test Coverage Report for Build 3176928833


Changes Missing Coverage Covered Lines Changed/Added Lines %
src/vptstools/scripts/constants.py 0 1 0.0%
src/vptstools/scripts/generate_coverage.py 0 35 0.0%
src/vptstools/s3_list_helper.py 0 36 0.0%
src/vptstools/scripts/transfer_baltrad_to_aloft.py 0 54 0.0%
<!-- Total: 0 126 0.0% -->
Totals Coverage Status
Change from base Build 3176705215: -21.1%
Covered Lines: 106
Relevant Lines: 308

💛 - Coveralls
coveralls commented 2 years ago

Pull Request Test Coverage Report for Build 3176928833


Changes Missing Coverage Covered Lines Changed/Added Lines %
src/vptstools/scripts/constants.py 0 1 0.0%
src/vptstools/scripts/generate_coverage.py 0 35 0.0%
src/vptstools/s3_list_helper.py 0 36 0.0%
src/vptstools/scripts/transfer_baltrad_to_aloft.py 0 54 0.0%
<!-- Total: 0 126 0.0% -->
Totals Coverage Status
Change from base Build 3176705215: -21.1%
Covered Lines: 106
Relevant Lines: 308

💛 - Coveralls
stijnvanhoey commented 2 years ago

While the scripts now lack unity and most of the code is not unit tested, this gives us a reference point and overview of all the available code used to run the services now. From this point on, we can start refactoring and cleaning out the no-long valid parts once the implementation to CSV-based standard is done.