This release is a pre-release and may not be stable for production use.
idi-data-validation
Data Validation for IDI project
Welcome to Data Validation for the IDI Project. The purpose of this repo is to validate NTIA BEAD challenge process data.
Note This repo uses pre-commit hook, please install by typing pre-commit install.
More information can be found:
- Video Link
- Detailed Description
- Challenge Submission Templates
- Link to challenge notice This contains links to docs with detailed descriptions.
There are two components of this repo:
- A set of scripts and utilities for generating CSVs for the illinois BEAD project.
- A set of scripts and utilities for validating CSV files.
IL Specific
The file run_me.sh will execute the illinois specific pipeline. This requires access to the illinois BEAD database.
- Notebook Contains work in progress notebooks
- data Data related to Illinois data generation project
- scripts Scripts relating to IL
Data Validation
- validation Package for data validation.
Overview of Data Validation Package.
The purpose of this package is to execute and avoid common errors when submitting the NTIA CSV files.
Usage
To run the validations after placing data in the /output_csv/ dir (IL-specific: run run_me.sh),
mkdir logs
python validation/utils/validator.py output_csv --results_dir logs/
Installing route
I'll push this up to PyPI shortly, but for this commit, you can create an env and install this package via these commands.
cd path/into/idi_data_validation_directory
python -m venv .venv
source .venv/bin/activate
python -m pip install -e .
bread_inspektor output_csv/
Current Status
| File name | Initial Code | Tests | Tested on IL |
|---|---|---|---|
| cai.csv | X | ||
| challengers.csv | X | ||
| challenges.csv | X | ||
| cai_challenges.csv | |||
| post_challenge_locations.csv | X | ||
| post_challenge_cai.csv | X |
Metadata
Release files for bread-inspektor 0.1.dev71
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 | |
|---|---|---|---|---|
| bread_inspektor-0.1.dev71.tar.gz | 20.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bread_inspektor-0.1.dev71-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.8 kB
Release files / bread_inspektor-0.1.dev71.tar.gz
| Download URL | bread_inspektor-0.1.dev71.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4da2b51133e6bb41c52554057b986ee3cfdbfe9fd13e1434d72a5792be91842e
|
|
BLAKE2b-256 checksum How to use checksums |
6106414cbc4b3a50e8ca8ff405aafd0eef8d38390b193f8e95d42c3528d09f8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Release files / bread_inspektor-0.1.dev71-py3-none-any.whl
| Download URL | bread_inspektor-0.1.dev71-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b513cc0d50f993343f7fb3d2e1f61b912695a62576e4b3bce2bf6bac42f2d845
|
|
BLAKE2b-256 checksum How to use checksums |
4f9fe271e6ca81ed3b97b46fd23825b67174ca68a2d718d4946cb301edb595f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for bread-inspektor 0.1.dev71
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.