• 346 views | 9 messages Discussion: LEAP
    Topic: Transformation - availability issueSubscribe | Previous | Next
  • Filip Opetuk 8/25/2020

    Hello.

    I've come across an issue with the transformation calculation. As you can see in my screenshots, the Exogenous capacity of transformation module Refineries is set to 100 PJ/year. Since maximum availability is set to 80%, net production capacity (= output because dispatch is set to FullCapacity) should be 80 PJ/year if I am not mistaken. However, when I run the simulation, the output calculated by LEAP is 80,00002022(...). Is it a bug or an error on my side?

    Best regards,
    Filip







  • Charlie Heaps 8/25/2020
      Best Response

    Hi Filip,

    Please send me your data set so I can investigate. Please send as a .leap file (you can create these using the Backup function) then send via Dropbox or Google Drive to leap@sei.org.

    Thanks,

    Charlie

  • Charlie Heaps 9/7/2020
      Best Response

    Hi again Filip,

    I've now had a chance to look at this but so far I don't see a problem. In the sample data you sent, you entered a capacity of 100 million GJ/Year measured in terms of the feedstocks going in to the refinery and you also specified a maximum availability of 80%, so the plant could only handle 100 x 0.8 = 80 million GJ of feedstock. That's what I see in the results when I look at them.

    A couple of possible points of confusion:
    1. Whether capacity is specified per unit of output (as would be normal for a power plant) or in this case per unit of feedstock. Outputs = feedstocks x process efficiency/100
    2. The local number formatting can sometime be confusing (commas vs. decimal points). LEAP uses whatever settings are local to your computer when showing values.
    3. Careful also for units conversion. I tried things out with different data and results units and as far as I can tell things were working OK.

    Let me know what you think. I hope this helps.

    Charlie

  • Filip Opetuk 9/8/2020
      Best Response

    Mr. Heaps,

    I agree with you - when I enter 100 million GJ/year of production capacity and 80% availability, I expect to get 80 million GJ/year of inputs in the Results view. However, the Results view returns the value of 80.000020224 million GJ/year of inputs. If I use, for example, 2000 million GJ/year with the same availability, one expects to get 1600 million GJ/year of inputs. However, LEAP calculates 1600.00040448 million GJ/year of inputs. Given the efficiency of 100%, this also translates to 1600.00040448 million GJ/year of outputs. My question is where does this difference come from and is it intentional? Note: I'm using LEAP 2020.1.0.18. to produce these results.

    Best regards,
    Filip

  • Charlie Heaps 9/8/2020
      Best Response

    Thanks for bringing this to my attention Filip!

    I think the difference probably comes from some small rounding errors in the definition of the power units (see the General: Units screen for these). Some of these are user editable but others are read-only. These were created many years ago when we used single precision values in LEAP, but I think we now use double precision storage, so I should be able to improve the precision of these units. I will look at this for an upcoming release of LEAP. This should be straightforward when using GJ/time units but is slightly more tricky for TOE/time and particularly TCE/time units since they are not always standardized and the power units need to be consistent with how they are defined as energy units. That is way they are user editable.

    One other possible issue is how we define a year for the units (i.e. as 8760 hours or 8760.25 hours on average to account for leap years). Given the changes I made to time slicing in LEAP2020 (where we now always assume a year is a nominal 8760 hours), it is possible that this is not consistent with some of the older power units. Either way, I will investigate and get this fixed.

    Charlie

  • Filip Opetuk 9/9/2020
      Best Response

    Charlie,

    Thank you very much.
    I am looking forward to the new update.

    - Filip

  • Charlie Heaps 9/10/2020
      Best Response

    Hi again Filip - please can you get the latest version (2020.1.19 or later). I've updated some of the units definition for power units to make them more precise. Hopefully that should address the issue you faced. Please can you let me know (here by reply) what you find out?

    Thanks,

    Charlie

  • Filip Opetuk 9/11/2020
      Best Response

    Mr. Heaps,

    After updating to 2020.1.0.19. I am no longer experiencing the issues - it looks like the improved unit definitions fixed it. Thank you very much!

  • Charlie Heaps 9/11/2020
      Best Response

    Great!