RMI-PACTA / pacta.executive.summary

Repo containing the code to generate charts in the PACTA COP executive summary document.
https://rmi-pacta.github.io/pacta.executive.summary/
Other
2 stars 2 forks source link

update weighting for the Aggregate score based on WEO2023 #327

Closed Antoine-Lalechere closed 5 months ago

Antoine-Lalechere commented 5 months ago

@jdhoffa @MonikaFu here are the lines of code to update the weighting for WEO2023 for the Aggregate Score.

Scenario raw data are stored on the following link in Azure but I don't know how to link Azure and GH, so the link used is on my machine for now - can you help me with it? https://portal.azure.com/#view/Microsoft_Azure_FileStorage/FileShareMenuBlade/~/browse/storageAccountId/%2Fsubscriptions%2Ffeef729b-4584-44af-a0f9-4827075512f9%2FresourceGroups%2FRMI-SP-PACTA-PROD%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fpactarawdata/path/scenario-sources/protocol/SMB

codecov[bot] commented 5 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 9.69%. Comparing base (b61c49d) to head (9740ede).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #327 +/- ## ===================================== Coverage 9.69% 9.69% ===================================== Files 27 27 Lines 2187 2187 ===================================== Hits 212 212 Misses 1975 1975 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

MonikaFu commented 5 months ago

thanks @Antoine-Lalechere. Reviewing now. If you want to use a path to azure storage instead of your local path, I don't think that this is possible. We could add a location of the file in a comment maybe. @jdhoffa do you have any input here?

jdhoffa commented 5 months ago

Yeah, I would just comment the line out, and add a comment pointing to the relevant file on azure I guess it's somewhere here: https://portal.azure.com/#view/Microsoft_Azure_FileStorage/FileShareMenuBlade/~/browse/storageAccountId/%2Fsubscriptions%2Ffeef729b-4584-44af-a0f9-4827075512f9%2FresourceGroups%2FRMI-SP-PACTA-PROD%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fpactarawdata/path/scenario-sources/protocol/SMB

jdhoffa commented 5 months ago

More specifically, here: https://pactarawdata.file.core.windows.net/scenario-sources/weo_2023-20240222/WEO2023 extended data/WEO2023_Extended_Data.xlsx

MonikaFu commented 5 months ago

The last link did not work for me @jdhoffa. Should it work in a browser? My experience with azure is that you can point to a directory but not a specific file. So you need to give a file location in the directory next to the link in the comment.

MonikaFu commented 5 months ago

In general, I would prefer that this dataset is an external dataset created in workflow.prep.* and passed to the relevant function as it will change with each COP and I don't think it makes much sense for it to be an internal dataset in this package. But given the time sensitivity I'd leave it as it is for now and add an issue for the next time we touch this repo (if we are going to be running more COP projects with executive summaries in the future).

MonikaFu commented 5 months ago

Closes #318

jdhoffa commented 5 months ago

The last link did not work for me @jdhoffa. Should it work in a browser? My experience with azure is that you can point to a directory but not a specific file. So you need to give a file location in the directory next to the link in the comment.

Hmm indeed, it doesn't work for me either that's odd... that is the URL i get as a result of "copy link", but anyway, the files are here: https://portal.azure.com/#view/Microsoft_Azure_FileStorage/FileShareMenuBlade/~/browse/storageAccountId/%2Fsubscriptions%2Ffeef729b-4584-44af-a0f9-4827075512f9%2FresourceGroups%2FRMI-SP-PACTA-PROD%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fpactarawdata/path/scenario-sources/protocol/SMB

and the specific file is: WEO2023_Extended_Data.xlsx

I suppose so long as those two pieces of information are tracked for posterity, we are good

jdhoffa commented 5 months ago

@MonikaFu @Antoine-Lalechere I leave it to you two to decide exactly how you want to achieve that. Agreed that for this project we shouldn't overthink where the data is stored, but probably in the long-term having it in workflow.* would make sense.

MonikaFu commented 5 months ago

@jdhoffa I requested a review from you since it was me who finished the PR in the end and I don't want to be reviewing my own code 🙃 FYI @Antoine-Lalechere