Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make waste incineration emissions part of chemicals MAC curve #1662

Closed
wants to merge 15 commits into from

Conversation

JakobBD
Copy link
Contributor

@JakobBD JakobBD commented Apr 22, 2024

Purpose of this PR

Addresses issue #274 by adding incineration emissions to vm_emiIndBase, such that they can be abated with the chemicals mac curve.

Remove parameters p37_wasteIncinerationCCSshare, p37_regionalWasteIncinerationCCSshare and the switch cm_wasteIncinerationCCSshare accordingly.

Type of change

(Make sure to delete from the Type-of-change list the items not relevant to your PR)

  • Bug fix
  • Refactoring
  • New feature
  • Minor change (default scenarios show only small differences)
  • Fundamental change
  • This change requires a documentation update

Checklist:

  • My code follows the coding etiquette
  • I performed a self-review of my own code
  • I explained my changes within the PR, particularly in hard-to-understand areas
  • I checked that the in-code documentation is up-to-date
  • I adjusted the reporting in remind2 where it was needed
  • I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
  • All automated model tests pass (FAIL 0 in the output of make test)
  • The changelog CHANGELOG.md has been updated correctly

Further information (optional):

  • Test runs are here:
    /p/tmp/jakobdu/remind_wasteIncinerationMAC

  • Comparison of results (what changes by this PR?):

@JakobBD
Copy link
Contributor Author

JakobBD commented Apr 22, 2024

Test runs have only been started just now; implementation might still have bugs. And we should definitely adjust MAC curve parameters to account for different costs & capture rates in waste incineration.

v37_plasticWaste(t,regi,entySe,entyFe,emiMkt)
* pm_incinerationRate(t,regi)
) * (1 - p37_regionalWasteIncinerationCCSshare(t,regi))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I currently don't understand this - won't this mean that vm_incinerationEmi will always show the FULL carbon content burned, even if part of that is captured?
if yes, it would be good to adjust the description of vm_incinerationEmi to highlight this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you are absolutely right. And more importantly, we have to update remind2.
We could do this with a postsolve parameter which applies the same capture rate on this as on the rest of the chemicals subsector, but I'd have to also check the implications of the now increased vm_emiIndCCS.
This will take a while, an I'm on holidays next week.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking forward to Ctrl+F through 3000 lines of reportEmi...

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its just four lines with vm_incinerationEmi, quit the whining.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do it then :)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@robertpietzcker
Copy link
Contributor

Hi Jakob, what is the status of the runs to check the implementations?
(just to make sure they look reasonable before approving the PR)

@JakobBD
Copy link
Contributor Author

JakobBD commented Apr 25, 2024

Runs converged. I haven't checked the results yet. But in order to get meaningful and easy to interpret results, we need to adapt remind2.

…_incineration_mac

separate incineration emi before and after CCS to ease reporting
@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

Probably not what was intended …
image

@robertpietzcker
Copy link
Contributor

if some comment/ review from me is needed, please ping me - the way I interpret it this is still under work, right?

@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

Current state:

Emi|CO2|+|Energy >                                                            
   + Emi|CO2|Energy|+|Supply                                               
   + Emi|CO2|Energy|+|Demand                                               
   + Emi|CO2|Energy|+|Waste                                                
Relative difference between -1207% and 1648%, absolute difference up to 454 Mt CO2/yr.

Emi|CO2|Gross|Energy >                                                        
   + Emi|CO2|Gross|Energy|+|Supply                                         
   + Emi|CO2|Gross|Energy|+|Demand                                         
   + Emi|CO2|Gross|Energy|+|Waste                                          
Relative difference between 0.00533% and 31%, absolute difference up to 454 Mt CO2/yr.

Emi|GHG|+++|Energy >                                                          
   + Emi|GHG|Energy|+|Supply                                               
   + Emi|GHG|Energy|+|Demand                                               
   + Emi|GHG|Energy|+|Waste                                                
Relative difference between -3388% and 112%, absolute difference up to 454 Mt CO2eq/yr.

Emi|GHG|++|ETS >                                                              
   + Emi|GHG|ETS|+|Energy Supply                                           
   + Emi|GHG|ETS|+|Industry                                                
   + Emi|GHG|ETS|+|Transport                                               
   + Emi|GHG|ETS|+|non-BECCS CDR                                           
   + Emi|GHG|ETS|+|Extraction                                              
   + Emi|GHG|ETS|+|Energy Waste                                            
   + Emi|GHG|ETS|+|Waste                                                   
Relative difference between -56.4% and 14972%, absolute difference up to 454 Mt CO2eq/yr.

Emi|GHG|Gross|Energy >                                                        
   + Emi|GHG|Gross|Energy|+|Supply                                         
   + Emi|GHG|Gross|Energy|+|Demand                                         
   + Emi|GHG|Gross|Energy|+|Waste                                          
Relative difference between 0.00431% and 30.3%, absolute difference up to 454 Mt CO2eq/yr.

@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

Back to the drawing board.
Emi|CO2|Energy|+|Demand is computed subtracting non-energy FE demand, and subtracting industry CCS. By putting part of the emissions from non-energy FE use into industry CCS, they get subtracted twice.

@JakobBD
Copy link
Contributor Author

JakobBD commented May 8, 2024

I faintly remember someone saying

but I'd have to also check the implications of the now increased vm_emiIndCCS

and someone else replying to

quit the whining

😇

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not convinced anymore that this is a desirable solution.
For one thing, it mixes two hitherto separate categories of energy and emissions in the chemicals subsector, FE use and non-FE use, in a way that makes it almost impossible to disentangle afterwards.
For another, what is the justification for applying the MAC curve for chemicals CCS to waste incineration?

@robertpietzcker
Copy link
Contributor

Hm.
do we have anyone joining the REMIND team in the near future for whom "implementing an explicit waste incineration CCS MAC" would be a good starting task to get to know REMIND?

@JakobBD
Copy link
Contributor Author

JakobBD commented May 17, 2024

It was always a trade-off between implementation time and outcome.
You can disentangle the two if you assume equal capture rates for waste incineration and chemicals production.
If you want to, you can adapt the parameters in the MAC curve to squeeze waste incineration between the production points, assuming a constant share of incineration to production.
Of course an explicit waste incineration MAC curve would be better, if someone wants to do it.
We have a person coming to PIK early July who is going to implement a waste incineration CC process along with process-based chemistry. I will support this implementation.

@robertpietzcker
Copy link
Contributor

so the question is "what are the requirements until maybe September/October, when we can hope for an updated implementation?"

for the projects I am involved with, we need to have stringent mitigation scenarios where there is no large amount of fossil waste emissions remaining in 2050, but we don't need a lot of subsectoral detail.

I think this "putting waste emissions into industry chemicals MAC" approach was an idea to achieve this aim.

However, if there is a project that requires information on sub-industry-sector level, this approach will clearly not be sufficient. Now the question is: Is there any such project with runs needed in the next 5 months?

if not, I would still propose to go for "use the chemicals MAC" as a short-term solution, knowing full well that this needs to be cleaned up by the person coming in July.

If there are other ideas about rather easy solutions for getting rid of the sizable fossil waste incineration emissions in 2050 NetZero scenarios, I am also open for it.

@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

  1. Copy the chemicals CCS MAC curve, name it co2waste. Implement plastic waste CCS using that.
    This would put us at the point that was intended from this PR, minus the reporting mess.
  2. Figure out propper parameters for the waste CCS MAC curve and change them.

@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

I would still propose to go for "use the chemicals MAC" as a short-term solution,

Putting waste CCS into the same bucket as chemicals CCS, when the FE streams are in different buckets, disqualifies this solution for every project in which somebody might take even a cursory glance at industry results, in my view.

knowing full well that this needs to be cleaned up by the person coming in July.

We usually guestimate that people need six months to get up to speed with REMIND. We never guestimated how long it takes to get up to speed with reportEmi().
I strongly advise against making this hot mess the first assignment for anybody you actually want to keep on the REMIND team.

@robertpietzcker
Copy link
Contributor

robertpietzcker commented May 21, 2024

Putting waste CCS into the same bucket as chemicals CCS, when the FE streams are in different buckets, disqualifies this solution for every project in which somebody might take even a cursory glance at industry results, in my view.

which is exactly why I asked if you know of any project that needs this.
In ECEMF we will be staying at the aggregated industry level, so there having substantial fossils remaining is much more relevant than having the chemicals subsector wrong.

but your proposal anyway sounds better, if it is relatively easy to implement. (it sounds quite easy to simply copy the code and change the name, but as I never really worked with the MACs I can't really comment on that)

I think the second step shouldn't be challenging - we can ask Jess' group for a rough estimation of waste CCS costs, and if they don't have a clue, I can provide some estimations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants