Do we need to redesign the top-level interface and/or the input datasets? #541
Replies: 1 comment
-
|
Dear @maurolepore, There are two ways how to derive at the tilt_subsector column. One is via the mapping of europages products and Ecoinvent products. When we do this, we derive the isic_digit from the mapping process and then map to the isic_digit the tilt_subsectors. The other way is via sector resolving with the use of GPT. Here we take the sector categories from the companies. As each company can be in more webscraped categories we use GPT to choose the right tilt_subsector. Long story short - there are two ways of how to get the tilt_subsector and this is conceptually wanted. To your note that sector profiles don’t have a CO2 datapoint. As the sector profiles are not matched with Ecoinvent you also don’t find a CO2 datapoint in the sector profiles. So this should also conceptually correct. However, the code should not be messy. But I cannot judge about positions. Please note that I also saw that in the CSV files that we got as an output there a a lot of missing NAs for the sector profiles for the tilt_sector and tilt_subsector column. I am opening a new issue for this today. The issue could lie in the sector resolving part or somewhere else - I will tag you and Kalash to it. So here we see that somewhere needs to be a bug. Hope that helped already a bit. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Relates to https://github.com/2DegreesInvesting/TiltDevProjectMGMT/milestone/15
@AnneSchoenauer and @kalashsinghal, I would appreciate your opinion about an inconsistency I see in the source of the "isic" and "sector" columns. This is not urgent but it could eventually make our code more user friendly and easier to maintain.
--
An important goal of the "Integration" milestone is to add the columns
*isic_4digitandtilt_*sectorto the outputs of tiltIndicatorAfter. For that we need to identify which inputs to tiltIndicator have those columns.Here I find that the source of those columns is a little messy. In general they come from the
productsorinputsdataset (globally calledco2) but the mess is this:co2dataset sometimes is in position 2 (e.g.emissions_profile(companies, co2)and sometimes in position 3 (e.g.sector_profile_upstream(companies, scenarios, co2).sector_profile()doesn't even have aco2argument so those columns come fromcompanies(e.g.sector_profile(companies, scenarios).This apparent inconsistency may be conceptually unavoidable, but it might also signal that we could improve the design of the tiltIndicator functions and/or the datasets it takes, so that the packages is easier to use and maintain.
Here is the code from which I derive these insights.
Created on 2023-09-26 with reprex v2.0.2
Beta Was this translation helpful? Give feedback.
All reactions