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
Curiously, the full_load_hours (and, therefore, productions) of wind turbines are much higher than they should be. The the full_load_hours are input to the MO module, and should be constant regardless.
This could very well be the reason for the discrepancy of production and demand when injecting the MO the full_load_hours into the ETM:
NOTE: the the full_load_hours in the table are correct again! They also look to be correct when using a stub with the MO module to reproduce the exact scenario. Only when printing the values inside the 'pry' session, do these weird values show up...
The text was updated successfully, but these errors were encountered:
When using pry-remote with a 'binding.remote_pry' in between these lines, the merit order info table looks like this:
Curiously,
the full_load_hours
(and, therefore, productions) of wind turbines are much higher than they should be. Thethe full_load_hours
are input to the MO module, and should be constant regardless.This could very well be the reason for the discrepancy of production and demand when injecting the MO
the full_load_hours
into the ETM:NOTE: the
the full_load_hours
in the table are correct again! They also look to be correct when using a stub with the MO module to reproduce the exact scenario. Only when printing the values inside the 'pry' session, do these weird values show up...The text was updated successfully, but these errors were encountered: