This release is a pre-release and may not be stable for production use.
Energetic
Automated building energy efficiency descriptor generation, model training, and deployment — similar to Mordred for chemical descriptors and Jaqpotpy for model deployment, but purpose-built for building energy analysis.
Features
- 200+ automated descriptors from building geometry, context, envelope, and time-series data
- Minimal input required — pass a GeoJSON, Shapefile, CityJSON, or DataFrame with WKT geometries
- ML model training with XGBoost, RandomForest, LightGBM, and Neural Networks
- Hyperparameter optimization via Optuna
- Model packaging and upload to custom deployment platforms
- Open dataset integration (ASHRAE, Building Data Genome, NYC LL84, OSM)
- Meteorological data enrichment for expanded feature sets
Installation
pip install -e .
# With ML extras (XGBoost, LightGBM, Optuna)
pip install -e ".[ml]"
# Full installation
Quick Start
Generate Descriptors
from energetic import EnergyFeaturizer
featurizer = EnergyFeaturizer(descriptors="all", cache=True, n_jobs=-1)
features = featurizer.fit_transform("buildings.geojson")
print(f"Generated {len(featurizer.get_feature_names())} descriptors")
featurizer.to_csv("features.csv")
Train a Model
from energetic import EnergyFeaturizer, EnergyModelTrainer
import pandas as pd
featurizer = EnergyFeaturizer()
features = featurizer.fit_transform("buildings.geojson")
X = features.drop("building_id", axis=1)
y = pd.read_csv("eui_targets.csv")["eui"]
trainer = EnergyModelTrainer(task="regression", model="xgboost")
metrics = trainer.train(X, y, optimization_trials=50)
trainer.save("model.joblib")
Upload to Platform
from energetic import ModelUploader
uploader = ModelUploader(
endpoint_url="https://your-platform.example.com",
api_key="your-api-key",
)
model_id = uploader.upload(trainer, featurizer, metadata, "office_eui_v1")
CLI
# Generate descriptors
energetic featurize buildings.geojson -o features.csv
# Train model
energetic train features.csv targets.csv -o model.joblib -m xgboost
# Show descriptor info
energetic info --descriptors
# End-to-end pipeline
energetic pipeline buildings.geojson targets.csv -o output/
Descriptor Categories
| Category | Count | Examples |
|---|---|---|
| Morphological | 60+ | Area, Zernike moments, Hu moments, fractal dimension |
| Contextual | 40+ | Sky view factor, neighbor density, solar potential |
| Envelope | 50+ | Wall-to-floor ratio, WWR, thermal mass, roof type |
| Temporal | 50+ | PRISM parameters, load factor, seasonality, ramp rates |
Input Formats
- GeoJSON —
.geojson,.json - Shapefile —
.shp - CityJSON —
.city.json - CSV/DataFrame — WKT geometry column
- Python dicts — list of building dictionaries
Keeping your own fields
Your input usually carries identifiers and attributes that are not descriptor
inputs — a BBL, an address, a portfolio key, an OSM id. keep= carries them
through to the output so results join straight back to your source rows.
featurizer = EnergyFeaturizer(keep=["bbl", "address"])
features = featurizer.fit_transform("buildings.geojson")
# -> building_id | src_bbl | src_address | morph_* | env_* | ...
model = EnergyRegressor(
dataset=df, target=y, name="eui",
keep=["bbl", "address"], # or keep="all"
)
model.fit()
model.predict(df)
# -> building_id | src_bbl | src_address | prediction
Kept fields are read from your GeoJSON properties / CSV columns, prefixed
with src_ so they can never shadow a computed descriptor, and echoed back by
the packaged model on the inference API.
They are passengers, never features. Passthrough columns are attached after
the feature set is fixed, so they cannot reach the estimator — you can safely
keep the target column itself. Use keep_prefix="" for verbatim names (a
genuine collision then raises rather than silently overwriting).
Open Datasets
from energetic.datasets import OpenDatasetLoader
loader = OpenDatasetLoader()
# NYC LL84 — live Socrata API (no auth required)
nyc = loader.load("nyc_building_energy", max_records=1000, property_type="Office")
# ASHRAE / BDG2 — Kaggle API (requires ~/.kaggle/kaggle.json)
ashrae = loader.load("ashrae_great_energy_predictor")
bdgp = loader.load("building_data_genome", components=["metadata", "electricity"])
# OSM footprints — Overpass API or OSMnx
osm = loader.load("openstreetmap_buildings", latitude=40.75, longitude=-73.98, radius_m=300)
# Run standardized benchmarks
result = loader.run_benchmark("nyc_site_eui", model="random_forest")
print(result["test_metrics"])
License
MIT
Metadata
Release files for energetic 0.0.2b1
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 | |
|---|---|---|---|---|
| energetic-0.0.2b1.tar.gz | 145.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| energetic-0.0.2b1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 322.2 kB
Release files / energetic-0.0.2b1.tar.gz
| Download URL | energetic-0.0.2b1.tar.gz |
|---|---|
| Size | 145.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6839406eb88695a40b3fd84e88080c5d89c30766a62fa15bb335355ae09a491b
|
|
BLAKE2b-256 checksum How to use checksums |
92103a25a1deaeb6e4998a9e76081d97aad00f44c2fd3ce55c2fbdf8228c7b6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.0
|
Release files / energetic-0.0.2b1-py3-none-any.whl
| Download URL | energetic-0.0.2b1-py3-none-any.whl |
|---|---|
| Size | 177.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd68743e2bce146ad75cbc03a65a789389953e477014c325819020b489ac2e91
|
|
BLAKE2b-256 checksum How to use checksums |
0655fa2d34a6101edb6ed2a153edbcb7241c9ef58c079e3539b2f000c4f5d327
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.0
|
Security for energetic 0.0.2b1
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.