Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impact Framework Project Updates 2024-09-12 #1013

Open
jmcook1186 opened this issue Sep 12, 2024 · 1 comment
Open

Impact Framework Project Updates 2024-09-12 #1013

jmcook1186 opened this issue Sep 12, 2024 · 1 comment
Assignees
Labels
project-update Used to flag project progress updates. Core team only

Comments

@jmcook1186
Copy link
Contributor

Who

Sponsor: @jawache (GSF)
Product owner: @jmcook1186 (GSF)
Leads: @navveenb (Accenture), @srini1978 (Microsoft)

Overview

We made some important updates to IF in the last fortnight.

I have been working on creating manifest files for our own websites, and also started trying a scope 3 LCA using Impact Framework. Generating manifests for real projects has been a good test of our product - I uncovered some fairly subtle but important bugs that led to some feature redesigns, and some tweaks to try to reduce friction for the manifest writer.

The most important change is the separation of the aggregation method for each parameter into components for time and component, making it possible to aggregate by averaging within a time series and then sum across multiple time series in a tree. This is really important for metrics such as SCI that are expressed as rates - if we have to aggregate using the same method within a time series and across multiple time series then we will always under or overestimate the true value. The 'split aggregation' fix resolves this issue and makes it much easier to configure SCI calculations for multi-component trees.

This change is merged into our main branch but not yet included in a release.

We also added support for inline arithmetic. This will help to make manifests more concise, since simple arithmetic operations don't necessarily require their own dedicated instance of a plugin anymore - instead you can do the arithmetic inline in the manifest instead, such as passing sums as arguments to plugins or as values in input data (e.g. a plugin parameter can now accept an expression such as some-value * 3 .

This will be available in the main branch very soon but it is currently awaiting an update in a dependency repository before we merge it in..

We also had a substantial feature added by @jamescrowley that allows a computed manifest to be re-run with new config and the results appended to the existing output data rather than overwriting it. This is going to be really useful for people that want to use the same manifest for repeated observations - maybe you want to observe daily but generate one manifest per month - well now you can just use the --append feature to build up your monthly report. I can imagine this being extra useful in combination with the if-merge feature.

The embodied carbon plugin got an overhaul too - now we mimic the CCF model for embodied carbon, taking some basic information about the server setup as arguments.

Other updates include reworking the explainer feature so that the response is primarily ordered by parameter rather than by plugin, which makes the list more easily searchable.

We are also putting the finishing touches on a new manifest visualizer that runs in the browser and allows to you more easily interrogate your output files.

Updates

Here's the links to more details about the most significant changes made over the last fortnight.

Issues

We have had a good fortnight, with no notable blockers.

Outlook

  • @jawache is doing an IF demo at OSS Summit in Vienna
  • IF team are creating more new manifests
  • some cleanup and tech debt tasks!
@jmcook1186 jmcook1186 added the project-update Used to flag project progress updates. Core team only label Sep 12, 2024
@jmcook1186 jmcook1186 self-assigned this Sep 12, 2024
@jmcook1186 jmcook1186 added this to IF Sep 12, 2024
@NAMRATA-WOKE
Copy link

NAMRATA-WOKE commented Sep 24, 2024

@jmcook1186 can we amplify these updates on social and in an article?

@zanete zanete moved this to Done in IF Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project-update Used to flag project progress updates. Core team only
Projects
Status: Done
Development

No branches or pull requests

2 participants