Comments (13)
Thanks for this suggestion @znicholls - we will include this data in the next release.
from ipcc_sr15_scenario_analysis.
Ok great.
So simply adding this information risks confusion of non-expert users
I agree let's not do that if it's already there. Can you talk me through how to get hold of it? At the moment there's a couple of problems.
- If I go into the scenario explorer, some variables are greyed out (e.g. "Emissions|PFC|C2F6")
- The data on the database doesn't seem to be harmonised see e.g. CO2 emissions from MESSAGE-GLOBIOM 1.0 and AIM/CGE 2.0 for the ADVANCE_2020_1.5C-2100 scenario (while the data I sent is harmonised perfectly).
from ipcc_sr15_scenario_analysis.
@znicholls, I looked at the data you sent bilaterally in preparation for release 2.0 (following to the release of the IPCC SRCCL), and it seems to me that most it is actually already available - just in different units or naming conventions (carbon vs. carbon dioxide, Gt vs Mt, SOx vs. Sulfur, etc.). After conversion, I could not identify any significant data difference.
So simply adding this information risks confusion of non-expert users. Therefore, I would prefer to not include duplicate data entries in the data - instead, we could make the MAGICC input file in the native MAGICC convention available as a separate file in the 'Downloads' section of the Scenario Explorer.
@znicholls @chrisroadmap @rgieseke @svenwillner @gidden, any comments?
from ipcc_sr15_scenario_analysis.
The timeseries variables Emissions|*
are the data as submitted by modelling teams. If the specific data is greyed out, no data is available for the chosen models/scenarios in the previous tab.
The timeseries variables Diagnostics|MAGICC6|Harmonized Input|Emissions|*
are the data after harmonisation and filling from background scenarios.
See this workspace for an illustration.
from ipcc_sr15_scenario_analysis.
The timeseries variables
Diagnostics|MAGICC6|Harmonized Input|Emissions|*
are the data after harmonisation and filling from background scenarios
Ahah beauty thanks! All good from my end then
from ipcc_sr15_scenario_analysis.
All good from my end then
Almost... Is there a reason the following scenarios have a different harmonisation to all the other scenarios (in 2010) in the workspace you shared?
MESSAGE-GLOBIOM 1.0-EMF33_1.5C_cost100
MESSAGE-GLOBIOM 1.0-EMF33_1.5C_full
MESSAGE-GLOBIOM 1.0-EMF33_Baseline
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_cost100
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_full
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_limbio
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_nobeccs
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_nofuel
MESSAGE-GLOBIOM 1.0-EMF33_Med2C_none
MESSAGE-GLOBIOM 1.0-EMF33_WB2C_cost100
MESSAGE-GLOBIOM 1.0-EMF33_WB2C_full
MESSAGE-GLOBIOM 1.0-EMF33_WB2C_limbio
MESSAGE-GLOBIOM 1.0-EMF33_WB2C_nofuel
MESSAGE-GLOBIOM 1.0-EMF33_tax_hi_full
MESSAGE-GLOBIOM 1.0-EMF33_tax_hi_none
MESSAGE-GLOBIOM 1.0-EMF33_tax_lo_full
MESSAGE-GLOBIOM 1.0-EMF33_tax_lo_none
MESSAGEix-GLOBIOM 1.0-CD-LINKS_INDCi
MESSAGEix-GLOBIOM 1.0-CD-LINKS_NPi
MESSAGEix-GLOBIOM 1.0-CD-LINKS_NPi2020_1000
MESSAGEix-GLOBIOM 1.0-CD-LINKS_NPi2020_1600
MESSAGEix-GLOBIOM 1.0-CD-LINKS_NPi2020_400
MESSAGEix-GLOBIOM 1.0-CD-LINKS_NoPolicy
In the data I sent through they've been adjusted so they do have the same harmonisation as all the other scenarios. I tried to work out how this was done but the two obvious choices didn't work (it's neither a constant scaling factor nor a constant offset...)
from ipcc_sr15_scenario_analysis.
@danielhuppmann any thoughts on this one if you have a minute?
from ipcc_sr15_scenario_analysis.
I have also run into this issue, today in fact. Perhaps the harmonized emissions for these scenarios didn't get picked up in v2.0 - related to #1 possibly?
from ipcc_sr15_scenario_analysis.
I have also run into this issue, today in fact. Perhaps the harmonized emissions for these scenarios didn't get picked up in v2.0 - related to #1 possibly?
Unfortunately not related to #1 or release 2.0 (which didn't change any of these data points). I'll investigate.
from ipcc_sr15_scenario_analysis.
@danielhuppmann just a quick ping here to see if anything has come of your investigations, could be helpful learning for other work which is ongoing.
from ipcc_sr15_scenario_analysis.
@danielhuppmann was there ever an update on this (fine if not, we can implement a custom solution on our side)?
from ipcc_sr15_scenario_analysis.
I didn't have a chance to do another release of the IAMC 1.5°C Scenario Ensemble and, to be honest, unless any critical inconsistencies are discovered, I won't be able to spend time on it in the coming months.
from ipcc_sr15_scenario_analysis.
Ok will close now then
from ipcc_sr15_scenario_analysis.
Related Issues (20)
- SSP Scenarios - Missing climate variables HOT 2
- Provide file sr15_specs.yaml in repository HOT 1
- Cross-reference the github repository in the notebooks HOT 2
- SSP data with zero carbon prices HOT 5
- Regional prices are incorrect HOT 3
- "Comment" capability for the scenario database? HOT 1
- Re-executability - notes from my journey HOT 4
- Include figure on CO2 contribution in illustrative pathways of SPM3b in notebook
- Unit labels for hydrofluorocarbons are set to 'kt HFC23'
- API change HOT 4
- MESSAGE-GLOBIOM_1.0 EMF33 scenarios are from MESSAGEix-GLOBIOM_1.0 HOT 1
- release 2.0 notebooks still load release 1.1 data by default HOT 1
- Data reporting bug for EMF33 REMIND-MAgPIE
- Shell Sky scenario CO2 emissions classification
- aggregation issue with Capital Cost variables HOT 1
- possible error in POLES ADVANCE onshore/offshore wind capacities HOT 5
- POLES Fossil CCS may be in the wrong units HOT 1
- HFC units incorrect in the Diagnostic|* variables
- Regression errors thrown in notebooks on recent/updated (Dec 2021) package environment (pyam 1.0+, possibly other packages also implicated) HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ipcc_sr15_scenario_analysis.