You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Electricity Maps is a third-party API that provides Marginal Carbon Intensity Rates as well as breakdown information on where the Carbon is being generated (nuclear, solar, etc). Electricity Map has consistently been proven to provide more accurate Carbon Intensity rates in Europe.
For the Carbon Aware SDK project involving Electricity Maps, there are two goals
Provide another data source to the Carbon Aware SDK so that it can be more widely adopted.
Prove that the architecture designed by the CSE team works and can be reused.
Success Metrics
Provide the Average Carbon Intensity over the Azure Batch duration using Electricity Maps Data
Provide the lowest Forecasted Average Carbon Intensity Rate over the Azure Batch duration using Electricity Maps Data
While not required by the current customer for the MVP, we do expect to implement the batch functionality so that future customers can provide reports on both the Actual and Forecasted data.
Goal
Electricity Maps is a third-party API that provides Marginal Carbon Intensity Rates as well as breakdown information on where the Carbon is being generated (nuclear, solar, etc). Electricity Map has consistently been proven to provide more accurate Carbon Intensity rates in Europe.
For the Carbon Aware SDK project involving Electricity Maps, there are two goals
Success Metrics
While not required by the current customer for the MVP, we do expect to implement the batch functionality so that future customers can provide reports on both the Actual and Forecasted data.
Work Items
Design and Specification 📔
Design Document [Design] : Add Electricity Maps as a Data Source to the Carbon Aware SDK #155
Architectural Decision Record(s)
Data Source Registration
Data Source Interfaces
Data Source Configuration
Engineering ⚙️
Release Planning
The text was updated successfully, but these errors were encountered: