maartenbrinkerink
commented
6 months ago Just some thoughts after a quick check;
- Besides SUR, we have more overlapping names. It's worth checking whether a model run with one of these countries (and vice versa with one of the regions) to see if the incorrect data is being pulled here as well. I suspect that we use e.g. .str.contains in parts of the workflow rather than == 'SUR' which can pull the incorrect entry.
- ARE and USARE
- ARM and USARM
- NGA and CHNGA
- SUR and RUSUR
- Besides SUR, there are other countries that are not included in the PLEXOS-World 2015 dataset but are included in the datasets with demand profiles and renewable timeseries.
-BLZ -TCD -HTI -MLT -SOM -SUR -TLS
- Given that in the next months we will start linking to the GEM datasets (through TZ) and will remove the links to the PLEXOS-World datasets, i'm not sure if it's worth the effort to try to go through the full workflow to try to tackle this. It might be easier to use the custom user inputs to load the required data for the time being.
Conda environment check
osemosys-globalconda environment.Current Behavior
Running Suriname (SUR) does not work for two related reasons:
Expected Behavior
Suriname model runs.
Steps To Reproduce
Set country to SUR and run the model.
Operating System
WSL on Windows 10.
Log output
No response
Anything else?
No response