Hourly energy share requirement modeling

[dharik13]

In branchH2_PTC_hourly_modeling , we have modified the energy_share_requirement function to model a constraint that is applied at the hourly level rather than at the annual level. However this implementation needs to be generalized in the following ways:

• We should update the code to allow for toggling between annual or hourly energy share requirement constraint based on user specification ("EnergyShareRequirement" flag e.g. flag could be 1 for annual and 2 for hourly matching). Based on this flag an If condition can be implemented into the energy_share_requirement function to activate the relevant constraint.
• The current implementation of the hourly energy share requirement constraint needs to be generalized to be useful for systems with multiple zones. Right now constraint hard coded for z=1
• The functions for writing outputs related to energy share requirement, in particular prices (dual of constraint) and revenues from meeting this requirement, is commented out since it is not compatabile with writing ouputs for the hourly form of the constraint. This needs to be revised and generalized to work for both annual and hourly constraints.

[dharik13]

After having thought about it more, I think we should model two types of energy share requirements.

1. energy share requirement for exogeneous electricity demands , which can be implemented as described above .
2. energy share requirement for endogeneous electricity demands, such as related to electrolytic h2 production. I think this constraint would be best placed within the H2 supply chain scripts under policy folder similar to how it is structured in GenX. Then we can use a flag in hsc_settings.yml to enable activation/deactivation of this constraint. We should probably call it a time-matching requirement constraint rather than an energy share requirement to make it clear what we are actually modeling.

[dharik13]

This issue has been addressed in develop_tmr branch