Open Micr0mega opened 3 weeks ago
Also have Infeasible result with 0.10.1. Optimal with 0.10.0. Optimal with 0.10.1 when passing pv_power_forcast.
The following change produced infeasible results. https://github.com/davidusb-geek/emhass/commit/dd00d438df95d78210fef52638ce472aafaf1805#diff-73fdad90feda707a91a77eb0a3628bf4346268f4ae70160850a06b29ce32024bL317-R317
This was caused by scrapper returning negative values. Something like the following will stop any negative PV values from producing infeasible results
constraints.update({"constraint_curtailment_{}".format(i) :
plp.LpConstraint(
- e = P_PV_curtailment[i] - P_PV[i],
+ e = P_PV_curtailment[i] - max(P_PV[i],0),
sense = plp.LpConstraintLE,
rhs = 0)
for i in set_I})
Describe the bug I have just updated from 0.9.1 to 0.10.1, and my day ahead optimization produces an infeasible result.
I have dynamic energy prices and solar panales, so I am using
load_cost_forecast
andprod_price_forecast
parameters. It did produce a P_deferrable0 value of 1 instead of the specified 2000.When I reverted to 0.9.1 a few minutes later, the result with the exact same parameters was optimal.
To Reproduce See above.
Expected behavior Optimal result.
Home Assistant installation type
Your hardware
EMHASS installation type
Additional context
Logs for both versions, INFO level, not DEBUG.
0.10.1:
0.9.1
If you need any more info, I can provide screenshots of the plots if needed, but I thought it might be a bit too much clutter for now.
Edit, found the full YAML config. Note I use 60 minute steps instead of the default 30.