Skip to content

Add wildfire baseline forecasting workflow for AI013#186

Merged
tarunkumaratla merged 2 commits into
ai-ml/ai013-forecastingfrom
ai-ml/ai013/abin-forecasting
May 15, 2026
Merged

Add wildfire baseline forecasting workflow for AI013#186
tarunkumaratla merged 2 commits into
ai-ml/ai013-forecastingfrom
ai-ml/ai013/abin-forecasting

Conversation

@thewonderworking
Copy link
Copy Markdown
Collaborator

Summary

This PR adds my AI013 wildfire baseline forecasting contribution inside the time-series model folder.

Work Completed

  • Added a wildfire baseline forecasting notebook under ai-ml/models/time-series
  • Used acq_date as the timestamp
  • Used region as the location field
  • Used frp_mw as the target variable for daily fire intensity
  • Filtered the wildfire data for Australia
  • Aggregated wildfire observations into a daily time series
  • Created a continuous daily date range
  • Created calendar, lag, and rolling average features
  • Tested three baseline forecasting models:
    • Naive forecast
    • Seven-day moving average forecast
    • Linear Regression with lag features
  • Evaluated the models using MAE, RMSE, and MAPE

@SunainM
Copy link
Copy Markdown
Collaborator

SunainM commented May 9, 2026

W work, but mostly irrelevant to Project.

Copy link
Copy Markdown
Collaborator

@SunainM SunainM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is useful standalone baseline work, but it should not be merged yet as-is.

Required fixes:

  1. Add the dataset path properly or document exactly where wildfire_multi_region_dataset.csv comes from. (use universal naming)
  2. Share any locally used csv/dataset with team
  3. Add a short README inside ai-ml/models/time-series/abin-wildfire-baseline/ explaining:
    • dataset source
    • target variable
    • how to run
    • expected outputs
    • model purpose
  4. Connect the notebook back to AI013/ADCRS by explaining how the forecast output can support risk scoring.
  5. Preferably convert the reusable parts into a small Python module or pipeline-compatible script instead of notebook-only code.
  6. If this is only exploratory work, label it clearly as baseline_experiment and not final AI013 integration.

Good work technically, but currently it is not integrated enough with the PHOENIX AI/ML pipeline or ADCRS purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants