Topic: why the CO2 of transformation branch gap so large between 2019 and 2020Subscribe | Previous | Next
Zigan Zhou 2/28/2022
Dear Professor Charlie:
I am modelling a energy transition passway by LEAP. There are two questions for you to answer.
First, why the CO2 of transformation branch gap so large between 2019 and 2020.
Secondly, I want to research the whole social cost of energy transition. According to the help of LEAP, if you want to use Optimation ,the dispatch rule should choose "Running cost".While the "Running cost" refers to the overall running costs (defined as variable cost + fuel cost). cost optimation,not the whole social cost. The whole social cost include capital costs for building new processes，salvage values (or decommissioning costs) for decommissioning processes ,fixed and variable operating and maintenance costs , fuel costs ,environmental externality values. So how to reflect the optimation of the whole social cost in the LEAP?
The attachments are LEAP files and two results of the YZRD model.
Best Regards!
.jpg)
Jason Veysey 3/4/2022
1 Like Dear Prof. Zhou,
Please allow me to respond to these questions.
First, I'll note that both questions are related. With respect to the second question, LEAP's documentation states that process-level dispatch rules are not relevant when a module is optimized. See the first paragraph here. Rather than only considering running costs, optimization in LEAP always accounts for all of the cost components you mentioned: capital costs, salvage values, fixed and variable O&M costs, fuel costs, and environmental externalities. So, in your model, all of these costs are determining the results in your optimized scenarios.
This said, LEAP never uses optimization for the years in the Current Accounts scenario, as these years are assumed to be for a historical period. Instead, the process-level dispatch rules (and first simulation years) specified in Current Accounts control dispatch. In your model, you're using the RunningCost dispatch rule for all processes and all years in Current Accounts. With the costs you've specified, this leads to a dispatch result in which there's significant participation by coal generation in 2019. In 2020, your first scenario year, optimization takes over and dispatches only gas generation. This causes greenhouse gas emissions to fall.
One reason why the optimizer may prefer gas is that the fuel cost for your natural gas process is 0. This may be a data entry error.
One other note – we recommend using NEMO rather than OSeMOSYS for optimization in LEAP. It's faster and offers more functionality, and it's the main focus of our development and support efforts.
Thanks,
Jason
Shimin Jia 3/7/2022
First of all I want to apologize because what I said next may not be very relevant to what you said.I am also a college student in China. I am currently using LEAP to conduct energy consumption and emission statistics. There are many problems in the learning process. I clicked every button I could find on the website, but I still don't know how to do it on the forum. I posted my own question in , so I thought of getting an answer this way. How did you post your question on the website? ? Hope to wait for the answer, I wish you a happy life and smooth learning
Jason Veysey 3/7/2022
Dear Xu Zhixin,
I'm sorry to hear you've had difficulty posting a new question in this support forum. You should be able to post a new question by logging in to the website, going to Discuss -> LEAP Support, and pressing the New Topic button.
Before posting a question, please search the forum to see if someone else has asked a similar question (you can do this with the search box on the right after you've clicked on Discuss -> LEAP Support).
Thanks,
Jason
Jason Veysey 3/7/2022
Dear Prof. Zhou,
A quick follow-up on this thread. On looking more closely at your model, I saw there was an error in the calculation of GHG emissions in Current Accounts due to a LEAP bug. The bug shows itself when the transformation module property "Meet auxiliary fuel use from this module's outputs (where possible)" is enabled, as it is for your "Electricity plant" module.
The bug will be fixed in the next release of LEAP. In the meantime, you can work around the problem and get the correct GHG emission results by turning off that transformation module property.
Thanks,
Jason