hefty 0.1.5__tar.gz → 0.2.0__tar.gz

{hefty-0.1.5/src/hefty.egg-info → hefty-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hefty
-Version: 0.1.5
+Version: 0.2.0
 Summary: Some (relatively) lightweight short-term energy forecasting tools for solar, wind, and load.
 Author: Will Hobbs
 License-Expression: BSD-3-Clause
@@ -14,24 +14,126 @@ Classifier: Topic :: Scientific/Engineering
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: herbie-data[extras]>=2026.3.0
+Requires-Dist: herbie-data[scikit-learn]>=2026.3.0
 Requires-Dist: pvlib>=0.13.1
 Requires-Dist: pandas>=3.0.0
 Requires-Dist: urllib3>=2.6.0
 Dynamic: license-file
 
-# hEFTy
+# hefty
 Some (relatively) lightweight short-term **e**nergy **f**orecasting **t**ools for solar, wind, and load.
 
-This repository currently includes solar and wind tools, but may expand one day to include electric load. Forecasts can be created using the NOAA GFS, NOAA GEFS, NOAA HRRR, and ECMWF IFS and AIFS (open data versions) Numerical Weather Prediction (NWP) and Machine Learning Weather Prediction (MLWP) models. The ECMWF CAMS version of IFS is also included, but only via `hefty.solar.get_solar_forecast()`, and it requires `cdsapi` to be installed and the user needs an API key (see https://ads.atmosphere.copernicus.eu/how-to-api).
+This repository currently includes solar and wind tools, but may expand one day to include electric load. Forecasts can be created using the following Numerical Weather Prediction (NWP) and Machine Learning Weather Prediction (MLWP) models:
+- NOAA GFS
+- NOAA GEFS
+- NOAA HRRR
+- ECMWF IFS (open data version)
+- ECMWF AIFS
+- ECMWF CAMS version of IFS* (a.k.a. "IFS-COMPO")
 
-For solar, look at the notebook [solar_example.ipynb](examples/solar_example.ipynb) for some examples, and [more_solar_examples.ipynb](examples/more_solar_examples.ipynb) for more examples. Both of these convert the resource forecasts to power.
+A detailed pvlib-based PV weather-to-power model is included in [pv_model.py](src/hefty/pv_model.py), `model_pv_power()`.
 
-There are also solar ensemble forecasts demonstrated in [ensemble_example.ipynb](examples/ensemble_example.ipynb).
+The [custom.py](src/hefty/custom.py) module is intended to help with getting forecasts of "custom" weather parameters, not necessarily specific to wind or solar, which migh be useful for load forecasting.
 
-For wind, look at the notebook [wind_example.ipynb](examples/wind_example.ipynb). The wind tools are not as developed at the solar tools.
+_*CAMS IFS is only available via `hefty.solar.get_solar_forecast()`, and it requires `cdsapi` to be installed and the user needs an API key (see https://ads.atmosphere.copernicus.eu/how-to-api and the [CAMS example notebook](examples/cams_example.ipynb))._
 
-The [custom.py](src/hefty/custom.py) module is intended to help with getting forecasts of "custom" weather parameters, not necessarily specific to wind or solar, which migh be useful for load forecasting.
+## Contents
+- [Installation](#installation) - getting started
+- [Quick example](#quick-examples) - a basic example of what hefty can do
+- [Example notebooks](#example-notebooks) - overview of the provided Jupyter notebook examples
+- [Supported forecast models](#supported-forecast-models) - description of NWP/MLWP models in hefty
+- [Handling dates and times](#handling-dates-and-times) - dates/times are comlicated with forecasting
+- [Local disk space](#local-disk-space) - downloads via hefty can use up a lot of storage space
+- [Troubleshooting](#troubleshooting) - common issues and possible solutions
+- [Data attribution](#data-attribution) - for using ECMWF data in particular
+- [References](#references)
+
+---
+## Installation
+
+A virtual environment is strongly recommended. You can install from PyPi with:
+
+```
+pip install hefty
+```
+
+To run the example Jupyter notebooks, you also need `jupyter`:
+
+```
+pip install jupyter
+```
+
+If you want to use ECMWF CAMS, you also need `cdsapi` (and an API key, see https://ads.atmosphere.copernicus.eu/how-to-api):
+
+```
+pip install cdsapi
+```
+
+## Quick example
+
+Here's a quick example of getting a solar resource data forecast, assuming you have already determined the dates/times needed:
+
+```python
+from hefty.solar import get_solar_forecast
+
+latitude = 33.5
+longitude = -86.8
+init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
+resource_data = get_solar_forecast(
+    latitude,
+    longitude,
+    init_date,
+    run_length=18, # 18 hours are included in the forecast
+    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
+    model='hrrr', # use NOAA HRRR
+)
+resource_data[
+    ['ghi','dni','dhi','temp_air','wind_speed']
+              ].plot(drawstyle='steps-mid')
+```
+
+with this output:
+
+<img src="images/output.png" width="500"/>
+
+<!-- Here's a wind resource forecast:
+
+```python
+from hefty.wind import get_wind_forecast
+
+latitude = 33.5
+longitude = -86.8
+init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
+resource_data = get_wind_forecast(
+    latitude,
+    longitude,
+    init_date,
+    run_length=18, # 18 hours are included in the forecast
+    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
+    model='gfs', # use NOAA GFS
+)
+resource_data[
+    ['wind_speed_10m', 'wind_speed_80m',
+    'wind_speed_100m', 'temp_air_2m', 
+    'pressure_0m']
+    ].plot(secondary_y=['pressure_0m'], drawstyle='steps-mid')
+```
+with this output (note that pressure is on the secondary y-axis):
+
+<img src="images/output_wind.png" width="500"/> -->
+
+## Example notebooks
+
+The [examples](examples) folder contains several example Jupyter notebooks. 
+
+- [solar_example.ipynb](examples/solar_example.ipynb): Example with multiple weather models, and includes power modeling with `model_pv_power()`.
+- [more_solar_examples.ipynb](examples/more_solar_examples.ipynb): Expanded examples, including multiple sites and multiple forecast initialization times.
+- [cams_example.ipynb](examples/cams_example.ipynb): Solar resource forecasting with CAMS IFS.
+- [ensemble_example.ipynb](examples/ensemble_example.ipynb): Examples of multi-member ensembles with IFS, AIFS, and GEFS.
+- [wind_example.ipynb](examples/wind_example.ipynb): A basic wind resource forecast example using a few models, including converting the data to a format compatible with `windpowerlib`*.
+- [erbs_vs_dirindex.ipynb](examples/erbs_vs_dirindex.ipynb): A comparison of Erbs and DIRINDEX irradiance decomposition models using SURFRAD measurements.
+
+\* https://github.com/wind-python/windpowerlib/
 
 ## Supported forecast models
 
@@ -61,7 +163,7 @@ Custom forecasts use the `period`, `product`, and `search_str` arguments
 passed to `get_custom_forecast()`, rather than the model-specific
 forecast-hour formatter used by the solar and wind tools.
 
-### Handling dates and times
+## Handling dates and times
 
 Handling dates and times can get a bit complicated when it comes to forecasts. hefty tries to match conventions used in the Solar Forecast Arbiter (https://forecastarbiter.epri.com/definitions/), such as "_lead time to start_" and "_run length_". However, the Arbiter uses the term "_issue time_" to represent the time that a forecast is issued/delivered, but that time is not necessarily directly relevant to NWP/MLWP outputs.
 
@@ -120,70 +222,59 @@ Model delays are more than just a fixed time: they can vary by lead time and by
 
 Delays calculated in `adjust_forecast_datetimes` are based on experiments in this gist https://gist.github.com/williamhobbs/9585ff5d1248ab5de4d9e8665d7c8ea6 (which will hopefully one day be cleaned up and added to this repo somehow), documentation published by ECMWF, and this cool dashboard by dynamical.org https://dynamical.org/status/.
 
-## Quick examples
+## Local disk space
+The current version of hefty keeps copies of downloaded grib files on your local storage. This can result in a large amount of disk space being used up. Future versions of hefty may change this (see [issue #70](https://github.com/williamhobbs/hefty/issues/70)), but for now, users may need to monitor storage space and manually delete files if needed. 
 
-Here's a quick example of getting a solar resource data forecast, assuming you have already determined the dates/times needed:
+hefty uses the directory configured by Herbie for storing files. See Herbie documentation here for details https://herbie.readthedocs.io/en/stable/user_guide/configure.html. The default `~\data` folder on Windows is `C:\Users\[username]\data`.
 
-```python
-from hefty.solar import get_solar_forecast
+## Troubleshooting
 
-latitude = 33.5
-longitude = -86.8
-init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
-resource_data = get_solar_forecast(
-    latitude,
-    longitude,
-    init_date,
-    run_length=18, # 18 hours are included in the forecast
-    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
-    model='hrrr', # use NOAA HRRR
-)
-resource_data[
-    ['ghi','dni','dhi','temp_air','wind_speed']
-              ].plot(drawstyle='steps-mid')
+### GRIB file issues
+GRIB files can occasionally download with missing/incomplete artifacts. This has been known to cause errors like:
+
+```
+TypeError: objects must be an iterable containing only DataTree(s), Dataset(s), DataArray(s), and dictionaries: ['t2m']
 ```
 
-with this output:
+If forecasts contain unexpected missing/incomplete values, try deleting cached GRIB files from your
+Herbie cache. See the Herbie cache configuration docs:
+https://herbie.readthedocs.io/en/stable/user_guide/configure.html. Navigating to the corresponding `~\data` folder, e.g., `C:\Users\[username]\data\ifs\20240605`, and deleting the contents may fix this.
 
-<img src="images/output.png" width="500"/>
+If deleting the cache does not resolve the issue, try downloading the same
+forecast from a different Herbie source, such as Azure, Google, or AWS.
 
-Here's a wind resource forecast:
 
-```python
-from hefty.wind import get_wind_forecast
+### Server issues
+ECMWF IFS/AIFS data have known issues via AWS that can result in 503 SlowDown responses. See https://forum.ecmwf.int/t/503-slowdown-errors-for-requests-to-s3-ecmwf-forecasts/14345, https://github.com/blaylockbk/Herbie/discussions/487. Using `priority='google'` (or `'azure'`) will likely help. 
 
-latitude = 33.5
-longitude = -86.8
-init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
-resource_data = get_wind_forecast(
-    latitude,
-    longitude,
-    init_date,
-    run_length=18, # 18 hours are included in the forecast
-    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
-    model='gfs', # use NOAA GFS
-)
-resource_data[
-    ['wind_speed_10m', 'wind_speed_80m',
-    'wind_speed_100m', 'temp_air_2m', 
-    'pressure_0m']
-    ].plot(secondary_y=['pressure_0m'], drawstyle='steps-mid')
-```
-with this output (note that pressure is on the secondary y-axis):
+Conversely, AWS may be more reliable than Google or Azure for NOAA models. 
 
-<img src="images/output_wind.png" width="500"/>
+### Install issues, Python version
 
-## Troubleshooting
+If you have problems installing dependencies or get errors related to `eccodes` (e.g., `RuntimeError: Cannot find the ecCodes library`), one possibility is that you are using a version of Python that is not yet fully supported by some dependencies. Among other possibilities, ECMWF appears to sometimes get behind in publishing wheels for all platforms. If you are using one of the latest versions of Python, downgrading to an earlier version that is till in "bugfix" status, or even "security", may fix these issues. 
 
-GRIB files can occasionally download with missing/incomplete artifacts. If forecasts
-contain unexpected missing/incomplete values, try deleting cached GRIB files from your
-Herbie cache. See the Herbie cache configuration docs:
-https://herbie.readthedocs.io/en/stable/user_guide/configure.html.
+### Firewall/certificate issues
+If you are using `hefty` behind a firewall, you might run into SLL/certificate issues. Making sure that Python knows where to find valid local certificates might help. _Potential_ solutions include the following, but check with your IT/security resources first:
 
-If deleting the cache does not resolve the issue, try downloading the same
-forecast from a different Herbie source, such as Azure, Google, or AWS.
+**Option 1**: Install `pip-system-certs`:
+
+```bash
+pip install pip_system_certs
+```
+
+**Option 2**: Use `certifi` and set environment variables at the beginning of each script/notebook:
+
+```python 
+import certifi
+# Set requests to use the certificates in your current environment
+os.environ['REQUESTS_CA_BUNDLE'] = certifi.where()
+os.environ['CURL_CA_BUNDLE'] = certifi.where()
+```
 
-## Attribution
+### Intermittent SSL errors
+In some instances, intermittent SSL errors (`Exception has occured : Processing failed:`... `[SSL: UNEXPECTED_EOF_WHILE_READING]` ...) _might_ be fixed by upgrading urllib3, e.g., `pip install --upgrade urllib3`.
+
+## Data attribution
 ### ECMWF
 If you use models from ECMWF, you may need to include attribution language with the results. 
 
@@ -200,25 +291,7 @@ A possible example attribution and citation for the CAMS version of IFS:
 > Contains modified Copernicus Atmosphere Monitoring Service information [2026]. Neither the European Commission nor ECMWF is responsible for any use that may be made of the Copernicus information or data it contains.  © 2026 European Centre for Medium-Range Weather Forecasts (ECMWF), www.ecmwf.int. This data is published under a Creative Commons Attribution 4.0 International (CC BY 4.0). https://creativecommons.org/licenses/by/4.0/.
 >
 > Copernicus Atmosphere Monitoring Service (2021): CAMS global atmospheric composition forecasts. Copernicus Atmosphere Monitoring Service (CAMS) Atmosphere Data Store, DOI: 10.24381/04a0b097 (Accessed on DD-MMM-YYYY).
-## Installation
-
-A virtual environment is strongly recommended. You can install from PyPi with:
-
-```
-pip install hefty
-```
-
-To run the example Jupyter notebooks, you also need `jupyter`:
-
-```
-pip install jupyter
-```
 
-If you want to use ECMWF CAMS, you also need `cdsapi`:
-
-```
-pip install cdsapi
-```
 
 ## References
 This project uses several Python packages, including pvlib, an open-source solar PV modeling package [1, 2], and Herbie [3, 4], a package for accessing weather forecast data from NOAA. `pv_model.py` (with the `model_pv_power()` function used here) comes from [5] which leverages some functions from [6].

{hefty-0.1.5 → hefty-0.2.0}/README.md

@@ -1,15 +1,117 @@
-# hEFTy
+# hefty
 Some (relatively) lightweight short-term **e**nergy **f**orecasting **t**ools for solar, wind, and load.
 
-This repository currently includes solar and wind tools, but may expand one day to include electric load. Forecasts can be created using the NOAA GFS, NOAA GEFS, NOAA HRRR, and ECMWF IFS and AIFS (open data versions) Numerical Weather Prediction (NWP) and Machine Learning Weather Prediction (MLWP) models. The ECMWF CAMS version of IFS is also included, but only via `hefty.solar.get_solar_forecast()`, and it requires `cdsapi` to be installed and the user needs an API key (see https://ads.atmosphere.copernicus.eu/how-to-api).
+This repository currently includes solar and wind tools, but may expand one day to include electric load. Forecasts can be created using the following Numerical Weather Prediction (NWP) and Machine Learning Weather Prediction (MLWP) models:
+- NOAA GFS
+- NOAA GEFS
+- NOAA HRRR
+- ECMWF IFS (open data version)
+- ECMWF AIFS
+- ECMWF CAMS version of IFS* (a.k.a. "IFS-COMPO")
 
-For solar, look at the notebook [solar_example.ipynb](examples/solar_example.ipynb) for some examples, and [more_solar_examples.ipynb](examples/more_solar_examples.ipynb) for more examples. Both of these convert the resource forecasts to power.
+A detailed pvlib-based PV weather-to-power model is included in [pv_model.py](src/hefty/pv_model.py), `model_pv_power()`.
 
-There are also solar ensemble forecasts demonstrated in [ensemble_example.ipynb](examples/ensemble_example.ipynb).
+The [custom.py](src/hefty/custom.py) module is intended to help with getting forecasts of "custom" weather parameters, not necessarily specific to wind or solar, which migh be useful for load forecasting.
 
-For wind, look at the notebook [wind_example.ipynb](examples/wind_example.ipynb). The wind tools are not as developed at the solar tools.
+_*CAMS IFS is only available via `hefty.solar.get_solar_forecast()`, and it requires `cdsapi` to be installed and the user needs an API key (see https://ads.atmosphere.copernicus.eu/how-to-api and the [CAMS example notebook](examples/cams_example.ipynb))._
 
-The [custom.py](src/hefty/custom.py) module is intended to help with getting forecasts of "custom" weather parameters, not necessarily specific to wind or solar, which migh be useful for load forecasting.
+## Contents
+- [Installation](#installation) - getting started
+- [Quick example](#quick-examples) - a basic example of what hefty can do
+- [Example notebooks](#example-notebooks) - overview of the provided Jupyter notebook examples
+- [Supported forecast models](#supported-forecast-models) - description of NWP/MLWP models in hefty
+- [Handling dates and times](#handling-dates-and-times) - dates/times are comlicated with forecasting
+- [Local disk space](#local-disk-space) - downloads via hefty can use up a lot of storage space
+- [Troubleshooting](#troubleshooting) - common issues and possible solutions
+- [Data attribution](#data-attribution) - for using ECMWF data in particular
+- [References](#references)
+
+---
+## Installation
+
+A virtual environment is strongly recommended. You can install from PyPi with:
+
+```
+pip install hefty
+```
+
+To run the example Jupyter notebooks, you also need `jupyter`:
+
+```
+pip install jupyter
+```
+
+If you want to use ECMWF CAMS, you also need `cdsapi` (and an API key, see https://ads.atmosphere.copernicus.eu/how-to-api):
+
+```
+pip install cdsapi
+```
+
+## Quick example
+
+Here's a quick example of getting a solar resource data forecast, assuming you have already determined the dates/times needed:
+
+```python
+from hefty.solar import get_solar_forecast
+
+latitude = 33.5
+longitude = -86.8
+init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
+resource_data = get_solar_forecast(
+    latitude,
+    longitude,
+    init_date,
+    run_length=18, # 18 hours are included in the forecast
+    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
+    model='hrrr', # use NOAA HRRR
+)
+resource_data[
+    ['ghi','dni','dhi','temp_air','wind_speed']
+              ].plot(drawstyle='steps-mid')
+```
+
+with this output:
+
+<img src="images/output.png" width="500"/>
+
+<!-- Here's a wind resource forecast:
+
+```python
+from hefty.wind import get_wind_forecast
+
+latitude = 33.5
+longitude = -86.8
+init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
+resource_data = get_wind_forecast(
+    latitude,
+    longitude,
+    init_date,
+    run_length=18, # 18 hours are included in the forecast
+    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
+    model='gfs', # use NOAA GFS
+)
+resource_data[
+    ['wind_speed_10m', 'wind_speed_80m',
+    'wind_speed_100m', 'temp_air_2m', 
+    'pressure_0m']
+    ].plot(secondary_y=['pressure_0m'], drawstyle='steps-mid')
+```
+with this output (note that pressure is on the secondary y-axis):
+
+<img src="images/output_wind.png" width="500"/> -->
+
+## Example notebooks
+
+The [examples](examples) folder contains several example Jupyter notebooks. 
+
+- [solar_example.ipynb](examples/solar_example.ipynb): Example with multiple weather models, and includes power modeling with `model_pv_power()`.
+- [more_solar_examples.ipynb](examples/more_solar_examples.ipynb): Expanded examples, including multiple sites and multiple forecast initialization times.
+- [cams_example.ipynb](examples/cams_example.ipynb): Solar resource forecasting with CAMS IFS.
+- [ensemble_example.ipynb](examples/ensemble_example.ipynb): Examples of multi-member ensembles with IFS, AIFS, and GEFS.
+- [wind_example.ipynb](examples/wind_example.ipynb): A basic wind resource forecast example using a few models, including converting the data to a format compatible with `windpowerlib`*.
+- [erbs_vs_dirindex.ipynb](examples/erbs_vs_dirindex.ipynb): A comparison of Erbs and DIRINDEX irradiance decomposition models using SURFRAD measurements.
+
+\* https://github.com/wind-python/windpowerlib/
 
 ## Supported forecast models
 
@@ -39,7 +141,7 @@ Custom forecasts use the `period`, `product`, and `search_str` arguments
 passed to `get_custom_forecast()`, rather than the model-specific
 forecast-hour formatter used by the solar and wind tools.
 
-### Handling dates and times
+## Handling dates and times
 
 Handling dates and times can get a bit complicated when it comes to forecasts. hefty tries to match conventions used in the Solar Forecast Arbiter (https://forecastarbiter.epri.com/definitions/), such as "_lead time to start_" and "_run length_". However, the Arbiter uses the term "_issue time_" to represent the time that a forecast is issued/delivered, but that time is not necessarily directly relevant to NWP/MLWP outputs.
 
@@ -98,70 +200,59 @@ Model delays are more than just a fixed time: they can vary by lead time and by
 
 Delays calculated in `adjust_forecast_datetimes` are based on experiments in this gist https://gist.github.com/williamhobbs/9585ff5d1248ab5de4d9e8665d7c8ea6 (which will hopefully one day be cleaned up and added to this repo somehow), documentation published by ECMWF, and this cool dashboard by dynamical.org https://dynamical.org/status/.
 
-## Quick examples
+## Local disk space
+The current version of hefty keeps copies of downloaded grib files on your local storage. This can result in a large amount of disk space being used up. Future versions of hefty may change this (see [issue #70](https://github.com/williamhobbs/hefty/issues/70)), but for now, users may need to monitor storage space and manually delete files if needed. 
 
-Here's a quick example of getting a solar resource data forecast, assuming you have already determined the dates/times needed:
+hefty uses the directory configured by Herbie for storing files. See Herbie documentation here for details https://herbie.readthedocs.io/en/stable/user_guide/configure.html. The default `~\data` folder on Windows is `C:\Users\[username]\data`.
 
-```python
-from hefty.solar import get_solar_forecast
+## Troubleshooting
 
-latitude = 33.5
-longitude = -86.8
-init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
-resource_data = get_solar_forecast(
-    latitude,
-    longitude,
-    init_date,
-    run_length=18, # 18 hours are included in the forecast
-    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
-    model='hrrr', # use NOAA HRRR
-)
-resource_data[
-    ['ghi','dni','dhi','temp_air','wind_speed']
-              ].plot(drawstyle='steps-mid')
+### GRIB file issues
+GRIB files can occasionally download with missing/incomplete artifacts. This has been known to cause errors like:
+
+```
+TypeError: objects must be an iterable containing only DataTree(s), Dataset(s), DataArray(s), and dictionaries: ['t2m']
 ```
 
-with this output:
+If forecasts contain unexpected missing/incomplete values, try deleting cached GRIB files from your
+Herbie cache. See the Herbie cache configuration docs:
+https://herbie.readthedocs.io/en/stable/user_guide/configure.html. Navigating to the corresponding `~\data` folder, e.g., `C:\Users\[username]\data\ifs\20240605`, and deleting the contents may fix this.
 
-<img src="images/output.png" width="500"/>
+If deleting the cache does not resolve the issue, try downloading the same
+forecast from a different Herbie source, such as Azure, Google, or AWS.
 
-Here's a wind resource forecast:
 
-```python
-from hefty.wind import get_wind_forecast
+### Server issues
+ECMWF IFS/AIFS data have known issues via AWS that can result in 503 SlowDown responses. See https://forum.ecmwf.int/t/503-slowdown-errors-for-requests-to-s3-ecmwf-forecasts/14345, https://github.com/blaylockbk/Herbie/discussions/487. Using `priority='google'` (or `'azure'`) will likely help. 
 
-latitude = 33.5
-longitude = -86.8
-init_date = '2024-06-05 6:00' # datetime the forecast model was initialized
-resource_data = get_wind_forecast(
-    latitude,
-    longitude,
-    init_date,
-    run_length=18, # 18 hours are included in the forecast
-    lead_time_to_start=3, # forecast starts 3 hours out from the init_date
-    model='gfs', # use NOAA GFS
-)
-resource_data[
-    ['wind_speed_10m', 'wind_speed_80m',
-    'wind_speed_100m', 'temp_air_2m', 
-    'pressure_0m']
-    ].plot(secondary_y=['pressure_0m'], drawstyle='steps-mid')
-```
-with this output (note that pressure is on the secondary y-axis):
+Conversely, AWS may be more reliable than Google or Azure for NOAA models. 
 
-<img src="images/output_wind.png" width="500"/>
+### Install issues, Python version
 
-## Troubleshooting
+If you have problems installing dependencies or get errors related to `eccodes` (e.g., `RuntimeError: Cannot find the ecCodes library`), one possibility is that you are using a version of Python that is not yet fully supported by some dependencies. Among other possibilities, ECMWF appears to sometimes get behind in publishing wheels for all platforms. If you are using one of the latest versions of Python, downgrading to an earlier version that is till in "bugfix" status, or even "security", may fix these issues. 
 
-GRIB files can occasionally download with missing/incomplete artifacts. If forecasts
-contain unexpected missing/incomplete values, try deleting cached GRIB files from your
-Herbie cache. See the Herbie cache configuration docs:
-https://herbie.readthedocs.io/en/stable/user_guide/configure.html.
+### Firewall/certificate issues
+If you are using `hefty` behind a firewall, you might run into SLL/certificate issues. Making sure that Python knows where to find valid local certificates might help. _Potential_ solutions include the following, but check with your IT/security resources first:
 
-If deleting the cache does not resolve the issue, try downloading the same
-forecast from a different Herbie source, such as Azure, Google, or AWS.
+**Option 1**: Install `pip-system-certs`:
+
+```bash
+pip install pip_system_certs
+```
+
+**Option 2**: Use `certifi` and set environment variables at the beginning of each script/notebook:
+
+```python 
+import certifi
+# Set requests to use the certificates in your current environment
+os.environ['REQUESTS_CA_BUNDLE'] = certifi.where()
+os.environ['CURL_CA_BUNDLE'] = certifi.where()
+```
 
-## Attribution
+### Intermittent SSL errors
+In some instances, intermittent SSL errors (`Exception has occured : Processing failed:`... `[SSL: UNEXPECTED_EOF_WHILE_READING]` ...) _might_ be fixed by upgrading urllib3, e.g., `pip install --upgrade urllib3`.
+
+## Data attribution
 ### ECMWF
 If you use models from ECMWF, you may need to include attribution language with the results. 
 
@@ -178,25 +269,7 @@ A possible example attribution and citation for the CAMS version of IFS:
 > Contains modified Copernicus Atmosphere Monitoring Service information [2026]. Neither the European Commission nor ECMWF is responsible for any use that may be made of the Copernicus information or data it contains.  © 2026 European Centre for Medium-Range Weather Forecasts (ECMWF), www.ecmwf.int. This data is published under a Creative Commons Attribution 4.0 International (CC BY 4.0). https://creativecommons.org/licenses/by/4.0/.
 >
 > Copernicus Atmosphere Monitoring Service (2021): CAMS global atmospheric composition forecasts. Copernicus Atmosphere Monitoring Service (CAMS) Atmosphere Data Store, DOI: 10.24381/04a0b097 (Accessed on DD-MMM-YYYY).
-## Installation
-
-A virtual environment is strongly recommended. You can install from PyPi with:
-
-```
-pip install hefty
-```
-
-To run the example Jupyter notebooks, you also need `jupyter`:
-
-```
-pip install jupyter
-```
 
-If you want to use ECMWF CAMS, you also need `cdsapi`:
-
-```
-pip install cdsapi
-```
 
 ## References
 This project uses several Python packages, including pvlib, an open-source solar PV modeling package [1, 2], and Herbie [3, 4], a package for accessing weather forecast data from NOAA. `pv_model.py` (with the `model_pv_power()` function used here) comes from [5] which leverages some functions from [6].

{hefty-0.1.5 → hefty-0.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hefty"
-version = "0.1.5"
+version = "0.2.0"
 description = "Some (relatively) lightweight short-term energy forecasting tools for solar, wind, and load."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -19,7 +19,7 @@ classifiers = [
     "Topic :: Scientific/Engineering",
 ]
 dependencies = [
-    "herbie-data[extras] >= 2026.3.0",
+    "herbie-data[scikit-learn] >= 2026.3.0",
     "pvlib >= 0.13.1",
     "pandas >= 3.0.0",
     "urllib3 >= 2.6.0",