01-08-2019, 10:01 PM

In TIMES, the DAYNITE timelices within each season (or its parent timeslice) are by default assumed to correspond to a representative day in that season. The timeslices of the representative day form a cycle, where the cycle is assumed to be repeated as many times as there are days within the season. The set of those timeslices can be said to be arranged in a Cyclic order, and the sequence is repeated like in a Periodic sequence.

Taking your example, it seems you have 24 equal length timeslices in each season, and they thus correspond to the hours of the representative day. The sequence of the timeslices is ordered exactly as defined by you, and form a cycle, such that hour 01 follows hour 24, hour 02 follows hour 01, and so on, hour 24 follows hour 23, and hour 01 again follows hour 24, just like in a 24-hour clock. The 24-hour cycle is assumed to be repeated so many times that all the hours in the full season are covered.

I would thus confirm that the operation of DAYNITE storage follows the ordered sequence of the timeslices, where no unique start/end timeslice can be identified.

Taking your example, it seems you have 24 equal length timeslices in each season, and they thus correspond to the hours of the representative day. The sequence of the timeslices is ordered exactly as defined by you, and form a cycle, such that hour 01 follows hour 24, hour 02 follows hour 01, and so on, hour 24 follows hour 23, and hour 01 again follows hour 24, just like in a 24-hour clock. The 24-hour cycle is assumed to be repeated so many times that all the hours in the full season are covered.

I would thus confirm that the operation of DAYNITE storage follows the ordered sequence of the timeslices, where no unique start/end timeslice can be identified.