Remove property CostFunction

[mattiaspalmqvist]

The CostFunction property may lead to more misunderstanding than it actually helps. It might me unnecessary to have this property at all.

It is only a pseudo code field and have often been misunderstood by developers that it should be used in code. It is probably better to provide som documentation with examples and only provide data in the API.

[larwa99]

Sounds like a good idea. In our case we only use the values "sum(price(c))", "sum(energy(c)*price(c))" and "sum(peak(c)*price(c))" for the costFunction in fixedPrice, energyPrice and powerPrice respectively. So it does not really add anything.

A bit related: The peakFunction is used by us to describe our reactive power model.

[mattiaspalmqvist]

Yes, I think we should remove the peakFunction as well, if we remove costFunction. So we remove this whole pseudo code concept. And instead add some documentation of how the calculation is made.

[larwa99]

I see peakFunction as an indicator of special handling as well as documentation of how it is made (together with description). If it is removed there needs to be another property added that signals that special handling/logic is needed to accurately calculate the component cost. Perhaps a boolean RequiresComplexCalculation is a good way of getting a programmatic signal that extra/manual attention is required?