Closed ChaelKruip closed 11 years ago
Opening up that pry-debugger, and looking up inland = @m.participant(:energy_power_wind_turbine_inland)
tells:
inland.full_load_hours
=> 8322.00
But apparently, the full load hours where never inputted for this participant:
inland.instance_variable_get(:@full_load_hours)
=> nil
So, because it hasn't been input, Merit calculates the full_load_hours
by the following rule:
production / (effective_output_capacity * number_of_units * 3600)
Which evaluates to something close to 8760 hours.
Fixed with quintel/etengine@e85f8a5
Well spotted! Kudos!
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...