GWP discrepancy between ga and dev versions of api #222
-
If I query the ga version of the api for gwp impacts for, say c5.4xlarge, I get this response for the lifetime manufacturing gwp: Explanation for 290 vs 202? I would guess embedded > manufacture because dev docs say: Queries used (verbose on or off makes no difference): Thanks for any help. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thanks for your issue. This difference is due to the evolution in the way we complete data:
In the case of a c5.4xlarge instance, the difference comes from the ``density'' of the ram. The information is not disclosed by AWS. If you look closely into the verbose : prod "density": {
"value": 0.625,
"unit": "GB/cm2",
"status": "DEFAULT",
"source": null
}, dev"density": {
"value": 1.2443636363636363,
"status": "COMPLETED",
"unit": "GB/cm2",
"source": "Average of 11 rows",
"min": 0.625,
"max": 2.375
}, Hope it solves your issue |
Beta Was this translation helpful? Give feedback.
Thanks for your issue.
This difference is due to the evolution in the way we complete data:
In the prod version, when we didn't know a piece of data and couldn't complete it based on the information we had, we used a conservative value (that will lead to the maximal impact).
In v1, we introduce the notion of min and max impact. When we don't know a data and we can't complete it based on the information we have, we use the average of the data available in our dataset and set a minimum and a maximum data which will be used to evaluate the min and max impacts.
In the case of a c5.4xlarge instance, the difference comes from the ``density'' of the ram. The information is not disclosed by…