Caiso integration

[elmartinj]

Caiso integration is identical to current CENACE's development state.

It is important to note that the OASIS API will only provide 39 months of history, prior data is available but would involve redesign of extraction and data flow structure.

General diagram of workflow is as follows:

CAISO OASIS API
↓
src/data/caiso/extract/core.py
Downloads DAM LMP ZIP files in date chunks
Saves raw files under data/caiso/raw/
...
src/data/caiso/transform/core.py
Filters total LMP rows
Converts data to: unique_id | ds | y
Saves data/caiso/processed/caiso.csv
...
src/data/caiso/aggregate/core.py
Creates daily Parquet partitions under:
data/caiso/processed-events/hourly/
...
src/data/caiso/utils/caiso_data.py
Loads training windows and actuals from partitioned data
...
src/forecast/caiso/core.py
Runs the existing Impermanent forecasting flow
...
src/evaluation/caiso/core.py
Evaluates forecasts using the existing Impermanent metrics

src/data/caiso/config.py contains the selected CAISO nodes, market configuration, start date and local storage paths.

For future S3 deployment
The current implementation uses local paths, but the pipeline stages are already separated cleanly enough for S3 deployment:

OASIS

• s3://bucket/caiso/raw/
• transformation job
• s3://bucket/caiso/processed/
• daily Parquet partitions
• forecast and evaluation jobs

The main change will be replacing direct Path and local filesystem operations with a storage abstraction supporting both local and S3 locations. Extraction, transformation, forecasting and evaluation logic should remain unchanged.