Repository navigation
TimeProfile addition/subtraction #91
Description
Activity
The proposed approach would work at least the way I see it. What are your thoughts @trulsf ? I do not see any issue with incorporating these, except for cases in which the profiles have different lengths.
In this case, we would need to have also
@assertto check that the profiles have the same length. The error message for different length is:prof_1 = OperationalProfile([1, 2, 3]) prof_2 = OperationalProfile([1, 2, 3, 6]) prof_1 + prof_2 ERROR: DimensionMismatch: arrays could not be broadcast to a common size: a has axes Base.OneTo(3) and b has axes Base.OneTo(4)
Do we consider the error message to be sufficiently descriptive?
I have also felt had the need for this quite recently, so maybe there is a need to add it.
For me the logical behavior is to ensure that
(prof1 + prof2)[t] == prof1[t] + prof2[t]
With the current practice of handling too short operational profiles by repeating the last entry, we need to consider this also when adding, e.g. we should have
OperationalProfile([1, 2, 3]) + OperationalProfile([1, 2, 3, 6]) == OperationalProfile([2, 3, 6, 9])We should also think through whether we should support combinations of profiles like
OperationalProfile + FixedProfile.There may also be some challenges if presented with more complex profiles on a strategic, scenario or representative level, e.g.
op = OperationalProfile([1, 2, 3]) rp = RepresentativeProfile([op, op]) sp1 = StrategicProfile([rp, op]) sp2 = StrategicProfile([op, op]) sp1 + sp2
The suggested implementation would generate a MethodError, but it is possible to imagine ways to define this by adding the
OperationalProfileto each of the profiles of theRepresentativeProfileWith the current practice of handling too short operational profiles by repeating the last entry, we need to consider this also when adding, e.g. we should have
I am more inclined to remove this and instead provide an error if the profile is too short for the time structure. The current approach can, especially in the case of
OperationalProfile, lead to potential problems if people are not aware of this behavior.
Can support for addition and subtraction for TimeProfile's be added?
One could implement this by
or one could implement
length(::TimeProfile)anditerate(::TimeProfile)with the.+and.-convention.