Inclusion of computational resources information in a/p resources metadata

[cozzolinoac11]

As an outcome of the common topic seminar held on 21.05.2024 (see presentation), below the proposed requirements for inclusion of computational resources information in a/p resources metadata.

More details about the tool for calculate of computational resources here.

Req. Id	Requirement	Plan	Deadline
1	Include the possibility to query the information related to the consumed resources (always combined with the information about the environment configuration) in combination with the other parameters. (Suggested by Stefan)	1. Investigate the best implementation solution, i.e. if creating a new Query Tool to perform the new type of queries (leaving the current Query Tool to perform the current queries) or to upgrade the existing Query Tool to optionally query also the computational resources 2. Implement the selected option.	31.12.2024
2	Consider additional libraries for water/energy consumption (Suggested by Rob)	1. Investigate the feasibility to implement the requirement, focusing on the existence and added value of new libraries. If feasible, then: - Update the current tool to include the selected additional libraries.	31.12.2024
3	Assign “labels” (as done for buildings, products, etc.) to a/p resources to classify them in terms of “energy efficiency” or “energy performance”. (Suggested by Rob)	1. Investigate the feasibility to implement the requirement. If feasible, then: - Define criteria to assign “labels” (as done for buildings, products, etc.) to a/p resources to classify them in terms of “energy efficiency” or “energy performance” - Implement the criteria to calculate the label - Add a new attribute in the md profile	31.12.2024
4	1. Create a new metadata for the new version of the a/p resource, including the version in the title (as it happens for the name of sw versions and allowing to keep previous versions). 2. Add in the description field an explanation of what the new version is bringing. Original suggestion (by Kathi) was to include versioning of a/p resource metadata, to be used each time a new version of the resource is released.	If the requirement is approved, it is immediately applicable	N/A
5	Display information in a more user-friendly way, e.g. using graphs (Suggested by Rob)	1. Investigate the best implementation solution. 2. Implement the selected option.	31.12.2024

Feedback welcome!

[KathiSchleidt]

What I miss is the first step, linking info on computational resources to the a/p metadata.

Generally I'd like a step between the steps "1. Investigate ..." & "2. Implement ...", something along the lines of Present options and discuss with partners

[gmartirano]

What I miss is the first step, linking info on computational resources to the a/p metadata.

Generally I'd like a step between the steps "1. Investigate ..." & "2. Implement ...", something along the lines of Present options and discuss with partners

Dear @KathiSchleidt, the first step you correctly mention here should be described in the slides 2, 3 and 4 of the presentation. Should you think that it is not enough, could you please help us better understand what is missing?

Regarding your second valuable comment, we implicitly thought that opening issues like this is exactly the best way to collect feedback.
Well receiving your final recommendation to provide specifications rather than minutes ;), we thought that adding a proposed implementation plan alongside the draft requirement could be an added value for the discussion, which should ultimately lead to finalise the requirement and the plan.

[KathiSchleidt]

@gmartirano I'd missed the steps mentioned in the presentation, had assumed that the table is complete. Think it would be possible to integrate the steps described in the presentation in the table above, just to make sure we have all steps together?

On collecting feedback from UC partners, my impression is that you'd get better feedback if you set up a call with the UC partners to discuss this.

[gmartirano]

@gmartirano I'd missed the steps mentioned in the presentation, had assumed that the table is complete. Think it would be possible to integrate the steps described in the presentation in the table above, just to make sure we have all steps together?

Sure @KathiSchleidt, we will do.
Initially we thought with @cozzolinoac11 about how to ensure that readers have the full picture in one place, without switching across applications. At the end we opted for the current version, but now, looking also at your comment/request, we will integrate everything here.

On collecting feedback from UC partners, my impression is that you'd get better feedback if you set up a call with the UC partners to discuss this.

Ok, we will set up a call.

[gmartirano]

Sure @KathiSchleidt, we will do. Initially we thought with @cozzolinoac11 about how to ensure that readers have the full picture in one place, without switching across applications. At the end we opted for the current version, but now, looking also at your comment/request, we will integrate everything here.

@KathiSchleidt, with @cozzolinoac11 we made 2 attempts:

• we integrated only the relevant text present in slides 2, 3 and 4, but, in our opinion, only the text extracted (without images), doesn't help
• we integrated all the text + images, but, in our opinion, it comes too long and it is also difficult to maintain the pptx formatting which should better help understand.

Therefore, should not be too inconvenient to click on the presentation link and quickly see the slides to get the full picture, we think that it is better to keep things as they are.
Please let us know.

[robknapen]

For requirement 2 and 3 please have a look at https://www.green-algorithms.org/.

[gmartirano]

Thank you @robknapen.
Did you directly use (or had direct experience of) any of the tools described?

[robknapen]

@gmartirano Unfortunately not, I only recently found out about this initiative (and it is fairly new itself I think). Still have to read their methods paper. But I thought it could already be a good inspiration for possible visualisations.

[gmartirano]

Ok @robknapen. Let's have a look first and then let's exchange here ideas for possible implementations. ;)

[cozzolinoac11]

Hi,
the integration between consumed resources and the Knowledge Base is now implemented.

To upload the csv file containing the information about the resources used, obtained using the tool, there are two ways in the Resource Metadata Ingestion Form:

1. while compiling a new metadata
2. using the Upload consumed resources button where it is possible to upload a csv file for each existing a/p resource in the Knowledge Base

It is possible to view consumed resources using Knowledge Base Query Tool. In the results table there is a new column with a lens for each a/p resource where, if clickable, information about consumed resources can be found.

For example, regarding the ResNet Classifier, you can view the resources consumed in two different tests using two different machines at this link.

[KathiSchleidt]

@cozzolinoac11 question on the query interface - I first select an entry from the pulldown list, then have to confirm this entry via the Add to query button. Any (technical) reason why we need the additional Add? Why isn't selecting enough?

The Add button would make sense if multiple entries can be selected, but this way seems like just an additional click

[KathiSchleidt]

@cozzolinoac11 out-of-the-box idea - I'm assuming we have the consumption in something resembling kW/hr. I'm wondering if we could transform this to something more graspable to a user, e.g. how long this would power a light-bulb?

Some of the inspiration is stolen from Jurgen Tack's Biodiversity Cookbook De heerlijke keuken, where he first calculates the environmental footprint of each recipe. However, as a number of m² doesn't really say much to non-scientists he then takes this calculation a step further, transforms to kg cooked potatoes (a quantity one can relate to!). Stunning to see a shrimp cocktail for 4 translate to 200kg cooked potatoes (you could feed a whole village!!!).