Posts: 59
Threads: 23
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Apr 2012
I'm attempting to write a user constraint that requires a minimum of 33% of H2 to be "renewable" H2. It is not quite a share constraint because of the way I'm designating renewable H2. Since electrolysis may or may not produce renewable H2, I'm making a secondary commodity (called REN_H2) that is produced when renewable H2 is produced, but I'm calling it an ENV commodity, just for ease of process specification. So 1 kt of REN_H2 is made when 1 PJ of H2PROD* is produced.
My Scen file looks like this:

Two processes can produce REN_H2 (Biomass gasification and a distributed electrolyzer). And since REN_H2 is in kt and H2Prod is in PJ, constraint is that (sum REN_H2)/(sum of H2Prod*)>=.33 kt/PJ
any help would be greatly appreciated. Thanks!
Posts: 59
Threads: 23
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Apr 2012
Seems there was a model error that didn't show up until I tried running with this scenario (it was a problem with how electrolyzers produced REN_H2). Anyway, I fixed this and and now this scenario is working fine and I can get it to require 33% renewable H2.
Posts: 1,063
Threads: 42
Likes Received:
20 in 16 posts
Likes Given: 27
Joined: May 2010
Reputation:
20
Apologies for not responding earlier; glad you got things working. One observation though: UC_* coefficients inherit interpolation rules from UC_RHS* (Antti, please make it more precise...). So, you can omit columns UC_FLO~0 and UC_COMPRD~0 in this table.
Posts: 1,988
Threads: 26
Likes Received: 68 in 59 posts
Likes Given: 20
Joined: Jun 2010
Nice to see you around here again, Amit!
A bit more precisely: The UC_NCAP, UC_CAP, UC_ACT,
UC_FLO, UC_IRE, and UC_COMxxx coefficients do not actually inherit the interpolation rules from UC_RHS*, but the default interpolation rule for them is "full
interpolation/extrapolation".
Therefore, because the UC constraint will be generated only for the years that have an UC_RHS* attribute defined, it is usually most "economical" to use an interpolation option only for the UC_RHS* parameters. When doing so, there should be no need to restrict the inter-/extrapolation of those other UC_* attributes, and thus no need to specify an I/E option for them.
Posts: 59
Threads: 23
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Apr 2012
thank you Amit and Antti for your tips. That is helpful information. This is perhaps a basic question but since I modeled my user constraint file after an analogous constraint from a colleague, I think I still have some questions about how it is set up.
Specifically, how do I know whether to use UC_FLO or UC_COMPRD for a given environmental or energy commodity?
thanks again,
Chris
Posts: 59
Threads: 23
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Apr 2012
Amit,
thanks for the response and clafirication.
Chris
Posts: 28
Threads: 9
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Nov 2012
Hi, I still cannot understand the UC_FLO and the UC_COMPRD. DEMO model, scenario Scen_UCTest, middle of the sheet Simple_UC for an example. What is the value "1" for UC_FLO and "-0.01" for UC_COMPRD means? Would you explain them?