Add DuckDB query layer and benchmark visualizations for Quartz Solar Forecast #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Pull Request
Description
This PR introduces DuckDB as a query layer for Quartz Solar Forecast, enabling fast SQL-based aggregation and filtering on Parquet/CSV forecast data without loading entire files into memory. It also provides a benchmark suite comparing DuckDB vs Pandas performance, with integrated Seaborn plots for execution time and memory usage.
Currently, forecast outputs and historical weather data are stored in Parquet and CSV files. Users need to load entire datasets into memory or write custom aggregation scripts, which is inefficient for large datasets.
Fixes #323
How Has This Been Tested?
pip install duckdbexamples/duck_db_benchmark.py.benchmarks_option_b/all_benchmarks.csv.Check that Seaborn plots for execution time and memory usage display Pandas vs DuckDB side by side
If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?
Checklist: