Open cozzolinoac11 opened 1 month ago
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
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.
@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 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.
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:
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.
For requirement 2 and 3 please have a look at https://www.green-algorithms.org/.
Thank you @robknapen. Did you directly use (or had direct experience of) any of the tools described?
@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.
Ok @robknapen. Let's have a look first and then let's exchange here ideas for possible implementations. ;)
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.
2. Implement the selected option.
- Update the current tool to include the selected additional libraries.
- 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
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.
2. Implement the selected option.
Feedback welcome!