-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assignment of capacity_factor
is not properly working for subannual time slices
#409
Comments
@behnam-zakeri could you please help us interpret here:
|
capacity_factor
is not properly working for subannual time slices
However, now that we have tests for |
Thanks! Adjusted the milestone accordingly. |
When I tried to understand the problem here, I found the following: basically, the existing
in the test (and look at pytest's output for this test by running with the
So I don't see any addition beyond the two specified season. Is this issue obsolete, then, @behnam-zakeri ? Because if no arbitrary value for |
@glatterf42 thanks, for checking this. Indeed, as you noted, there is no problem in the input data of |
The workaround for resolving this issue is proposed in this commit. But we need to extend |
In
message_ix\model\MESSAGE\data_load.gms
, there are two equations (see the links below) related to the assignment ofcapacity_factor
:The first equation assigns
capacity_factor = 1
to the missing entries forcapacity_factor
in any time slice.message_ix/message_ix/model/MESSAGE/data_load.gms
Line 141 in 6f3d0b2
The second equation calculates an average yearly value for
capacity_factor
:message_ix/message_ix/model/MESSAGE/data_load.gms
Line 145 in 6f3d0b2
The problem is that, in a scenario with sub-annual time slices, e.g., two seasons of winter and summer; when a technology is active only in sub-annual time slices, it has no
capacity_factor
defined for timeyear
. As such, Eq. No. 1 above adds acapacity_factor
with the value of 1 foryear
. Then, Eq. No 2 above makes an average yearly capacity factor by considering all time slices, including winter, summer, andyear
. This results in an averagecapacity_factor
higher than 1, which is not correct.To tackle this issue, it seems the solution is to reverse the order that these two equations appear in the formulation, i.e.,:
capacity_factor
, and then,year
, assiging the value of 1 to that.The text was updated successfully, but these errors were encountered: