Cannot get res policy working for power sector in GCAM v6.0

[robbieorvis]

I am trying to run a RES policy for the power sector in GCAM v6.0. As far as I can tell the file (attached) is configured correctly, but when running this I get an error about a nonexistant market:

“Called for price of non-existant market USA_CES_Credit-fixed-output in region USA”

The market name is USA_CES_Credit. I ‘m not sure where fixed output is coming into play. I have removed hydro from the market since it is a fixed output source but the problem persists.
RES_file.zip

[mbins]

Hey Robbie, have you run this type of RES policy with the endogenous cooling technologies (and associated pass-through-sectors) before? This is a bit of a guess, but I think the pass-through-sectors might create a fixed output associated with the output of their previous vintages to pass to the associated pass-through-technology in the electricity sector. I'm not totally sure what this policy is meant to accomplish, but you might be able to accomplish it using the technologies in the electricity sector, without having to deal with all the pass-through-sectors.

[robbieorvis]

I haven’t but was wondering the same thing. It seems like we’ll have to try it that way and then just ignore the calibration warnings that now come up when trying to just use electricity.xml On May 19, 2023, at 5:25 PM, mbins ***@***.***> wrote:  Hey Robbie, have you run this type of RES policy with the endogenous cooling technologies (and associated pass-through-sectors) before? This is a bit of a guess, but I think the pass-through-sectors might create a fixed output associated with the output of their previous vintages to pass to the associated pass-through-technology in the electricity sector. I'm not totally sure what this policy is meant to accomplish, but you might be able to accomplish it using the technologies in the electricity sector, without having to deal with all the pass-through-sectors. — Reply to this email directly, view it on GitHub<#284 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK5N6SNJ3LSHQDQ2W3POG2DXG7QLBANCNFSM6AAAAAAYIHKKZQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[robbieorvis]

This was an absolute doozy to get working, but I did it.

I had to revert to the old electriicty.xml file. It seems that the new pass-through-sectors broke the ability to use the .
RES_file.zip

I uploaded the file I used. I had to do a few things:

1. Every year needed its own credit system due to the vintaging system and the fact that GCAM would only pick up the final year coefficient (as an side it would be really useful if you could update the coefficient node to allow for the use of the year attribute, which would let users set different coefficients in different years...
2. I had to set the constraint for each credit just in the year it was used, even though it was carried throughout.
3. Technologies then have res-secondary-outputs for every year covering every credit year, again due to vintagin.

See the uploaded file for more.

For folks at the lab:

• With the latest updates for the cooling techs, we've lost the ability set an RPS/RES/CES policy in the power sector. This is one of the most important global policies for cutting down on GHG emissions, so it would be really awesome if this could be addressed in a future release. Seems important.
• Per note above, it would be very helpful if you could have coefficients read the year attribute and allow for variation across years. Rich had previously asked for this ability and I thought @pralitp said it made its way into the code, but I couldn't get it working. I might just have something wrong. Because of the way the power sector is vintaged, I had to have coefficients for the 2015 vintages, but GCAM would only read the final year (perhaps the last chronologically in the code) coefficient and apply it for all years.
• Note the requirement for the constraint in the policy-portfolio-standard. The current documentation online for energy intensity standards doesn't say anything about the need for this, but it is required or the policy does nothing. I suggest updating the documentation to make this clearer.

Also tagging @rjplevin for work in updating pygcam and how the RES policy will need to be updated (and noting that it cannot currently be used with the shipped config file...).