boaviztapi
boaviztapi copied to clipboard
Boavizta
🛠 Giving access to BOAVIZTA reference data and methodologies trough a RESTful API
## Problem ```usage_location``` can only be given in the NATO trigram (see: https://github.com/Boavizta/boaviztapi/blob/main/boaviztapi/data/electricity/electricity_impact_factors.csv). When the API is used to retrieve the impacts of cloud instances it could be easier for...
## Problem Add a API route that returns current version of the API. ## Solution ## Alternatives Return API version in the API output. ## Additional context or elements
At the moment, the coefficient value 0.284 W/GB is used in the implementation. Source code: https://github.com/Boavizta/boaviztapi/blob/4af9f116170be39e919b1d95dc4bd02b65afd93b/boaviztapi/model/consumption_profile/consumption_profile.py#L30 Docs: https://doc.api.boavizta.org/Explanations/components/ram/#determining-the-parameters In the paper that was recently published during the HotCarbon conference a...
## Bug description Using the verbose output, the usage impacts of individual components are higher than the total usage impact. I would expect that the total usage impact is the...
Sourced from TEADS, unclear what their source is. Didn't have a die size and inferred release date from the date of AWS's [announcement] of the r7iz where this CPU is...
## Problem The documentation states that for usage impacts, the PE factor comes from IRENA (2016). API doc link https://doc.api.boavizta.org/Explanations/usage/elec_factors/ However the wikipedia article states that data is from 2021...
## Problem ISO has just released the 21031 specification, which is just a copy-paste of the [SCI methodology of the Green Software Foundation.](https://sci.greensoftware.foundation/) The methodology is quite easy to follow...
## Problem Github is deprecating Node 16, we need to upgrade the github actions that use it to newer version. https://github.com/Boavizta/boaviztapi/actions/runs/8921036143 For example we have warning in current workflows: ```...
**Problems** The CPU consumption profile endpoint: - Does not currently use the family and TDP parameters from the name completion - Returns a 500 error if the CPU name fuzzy-match...
