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
During the cost update project, a new method for cost calculation has been written. The new method does not use the fixed and variable costs anymore, but considers the CAPEX and OPEX. Part of the old method is still included in the code (/app/models/qernel/node_api/cost.rb), and should be cleaned up. The old total cost calculation should especially be removed, since this does not reflect on the new total costs anymore.
When the total cost calculation is removed from the file, and the energy graph is opened locally, error messages show up in the node information. This should be updated as well.
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
ChaelKruip
added
Pinned
Will never be marked as stale or auto-closed.
and removed
Stale
Issue had no activity for 60 days and will be, or has been, closed.
labels
Jun 20, 2022
Unfortunately no. I keep on hitting roadblocks: many of the merit order calculations rely on the methods we wanted to remove because they were deemed redundant.
During the cost update project, a new method for cost calculation has been written. The new method does not use the fixed and variable costs anymore, but considers the CAPEX and OPEX. Part of the old method is still included in the code (
/app/models/qernel/node_api/cost.rb
), and should be cleaned up. The old total cost calculation should especially be removed, since this does not reflect on the new total costs anymore.When the total cost calculation is removed from the file, and the energy graph is opened locally, error messages show up in the node information. This should be updated as well.
Notifying @DorinevanderVlies
The text was updated successfully, but these errors were encountered: