You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
I've noticed a few small mistakes in the OSeMOSYS pyomo code, see my pull request for proposed corrections.
Thomas Heggarty OSeMOSYS_2020_06_08.txt
The text was updated successfully, but these errors were encountered:
Line 231: The RETotalDemandOfTargetFuelAnnual variable doesn't appear in the OSeMOSYS documentation (see https://osemosys.readthedocs.io/en/latest/manual/Structure%20of%20OSeMOSYS.html ), however the pyomo code is missing the RETotalProductionOfTargetFuelAnnual variable, which is present in the documentation. My guess is that its name has changed in the problem description at some point, but wasn’t conveyed in the pyomo code. Note that, along with the storage constraints (see Contribution to OSeMOSYS_pyomo #1 and Update to storage equations #2 ), the pyomo code is also missing the "RE Production Target constraints", despite being in the official OSeMOSYS problem description. I do not know if this is deliberate; I have written the associated pyomo code and can upload it if need be.
Line 537: I think the same thing happened here: the variable name TotalAnnualCapacity must have been changed to TotalCapacityAnnual in the problem description at some point. The pyomo code was modified accordingly in most sections of the code, but not in the reserve margin equations, hence the proposed correction.
Line 538, 542 and 546: the final lines of each constraint is missing the term “model.” in front of each constraint name. If the term is missing, these constraints aren’t added to the model.
Line 541: The parameter ReserveMarginTagFuel is missing the sets on which it is defined. If missing, python throws an error.
Hi all,
I've noticed a few small mistakes in the OSeMOSYS pyomo code, see my pull request for proposed corrections.
Thomas Heggarty
OSeMOSYS_2020_06_08.txt
The text was updated successfully, but these errors were encountered: