Remove capacity factor flexibility in steel sector#2323
Conversation
68d5948 to
d7c7026
Compare
fschreyer
left a comment
There was a problem hiding this comment.
Thanks for this change!
Do you have some before/after plots for H12 Npi and PkBug to see what changes?
|
Adding here a quick overview of how this changes H12 NPi and PkBudget runs. Steel production
Short-term
Long-term
PE|CoalSlight increase across all regions and scenarios (only in the short term to 2050) |
|
I've now added the bf / bof lifetime change to this PR. |
|
|
||
| *' for primary steel, the iterative bounds used above are too restrictive | ||
| *' due to small inconsistencies in steel production input data. | ||
| *' we add the option to use the previous time step's pm_cesdata value instead. | ||
| $offOrder | ||
| vm_cesIO.up(t,regi,"ue_steel_primary")$(t.val gt 2005) | ||
| = max( | ||
| pm_cesdata(t-1,regi,"ue_steel_primary","quantity"), | ||
| !! more flexible upper bound, can be set by the previous time step's data | ||
| (pm_cesdata(t,regi,"ue_steel_primary","quantity") | ||
| *(2.5 + max(0, (sm_CES_calibration_iteration - 1) / sm_tmp)) | ||
| ))$( sm_CES_calibration_iteration le sm_tmp ) | ||
| + INF$( sm_CES_calibration_iteration gt sm_tmp | ||
| ); | ||
| $onOrder | ||
|
|
There was a problem hiding this comment.
Woah, nice! Looks like that took a while to find/fix.
Does this fix the calibration issue that @whitenightZhang also encountered for process-based chemicals?
If so, it would be good to FYI @leonieschweiger about this.
There was a problem hiding this comment.
Thank you! It did :)
I am not sure (I sent this fix to @whitenightZhang when he was having issues and can't remember the outcome). But it will be a step in the right direction. Happy to check with @leonieschweiger if it's enough, or if we should adjust it further for chemicals.
|
My apologies, but having a closer look, I am having second thoughts: The PR changes our messaging around steel drastically, as BF-BOF-CCS now is the dominant technology until 2050. I see further refinement capabilities:
I am sorry if this causes further work, but I'm really not sure if the current results are better than the previous. |
|
Maybe you missed this:
I don't know to what extent this will make a difference, but it will reduce the amount of BF-BOF-CCS. What I suggest: I will check how big a difference it makes to add the biomass fix. If we still think it's a lot of CCS, we can introduce some earlyReti. My two cents on CCS in PkBudg750: I actually don't think it's unrealistic to have quite a bit of CCS in an ambitious scenario with high carbon prices. I know CCS in steel is difficult to scale up, but so is reaching a PkBudg750 .. that's a more philosophical question though! |
Overview of changes@JakobBD , here are the runs with two changes:
Overall, I would imagine you'd be happier with these results. Worth noting: in both cases, the transition to H2-DRI in EUR is even faster than before, so we probably need to add some adjustment costs to H2-DRI and CCS on top of my changes. Next stepsWhat I would need from you:
CS2 resultsWith 25% lower earlyReti rate
With 50% lower earlyReti rate
|
|
I don't understand what's going on: In the first plot you're comparing 75% defaultER (no suffix) to 0% dER (.1 suffix), and in the second plot 75 % dER (no suffix) to 50 % dER (.1 suffix)? Which also means that in PkBudg750, EUR has more DRI in 2040 if less BF/BOF can be retired?? If you give your scenarios a custom suffix (first column in scenario_config), they are easier to distinguish. It's easiest to only do it for PkBudg (if you do it to NPi, you also have to change some later columns). Important: For a fair model, I think the bfcc tech should also be added there. Apologies if I didn't spell this out. This might change the results quite a bit.
Yes, I think so. Unfortunately, that requires quite some parameter fiddling. Especially the seed, since it has different units than the energy tech. let's talk. And just to double check: The bio limit has no effect, right?
I don't have a preference on joint or separate PR's, but I'll comment my bio questions on the bio one as long as it's open. |
|
Guideline of what could be next steps from my point of view:
|





Purpose of this PR
Up to now, steel production could be ramped up or down by the model freely by implicitely changing the capacity factor (production was set to be less than
vm_capFac * vm_cap). This means e.g. coal-based steel production can be scaled down (unrealistically) fast with rising carbon prices. Typically, steel plants always operate at high capacity factor as they are capital-intensive, so this parametrization is not ideal.Production is now fixed to be equal to
vm_capFac * vm_capafter 2020. Now, for more control over the phase-out of coal-based steel, we should use earlyReti switches. The default parameters work fine, but in a very ambitious scenario, we could consider allowing some early retirement in the steel sector, especially in Global North countries + China.We also change the default lifetime of
bfandbofto 35 years (from 20 previously). This corresponds to a BF-BOF plant undergoing one BF relining before retiring. While steel plants could technically be retired after 20yr already, this is not financially attractive in most cases. Combined with the other changes made to the steel module, this change means a bit more coal remains locked in, even in ambitious scenarios (see below). Very ambitious scenarios could switch on some measure of earlyReti forbfandbof.Type of change
Indicate the items relevant for your PR by replacing ◻️ with ☑️.
Do not delete any lines. This makes it easier to understand which areas are affected by your changes and which are not.
Parts concerned
Impact
Checklist
Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge.
make test) after my final commit and all tests pass (FAIL 0)remind2if and where it was neededforbiddenColumnNamesin readCheckScenarioConfig.R in case the PR leads to deprecated switchesCHANGELOG.mdcorrectly (added, changed, fixed, removed, input data/calibration)