Originally Posted by Hubb777
See:
1. There is event A and event B - they run 24//7/365
2. Event A has an interval of 1 hour and a duration of 4 minutes (Start at 1709615040, interval 3600 and event time 240).
3. Event B interval 6 hours, duration 2 hours. (Start at 1709629200, interval 21600 (6 hours) and event time 7200 (2 hours))
4. If event B occurs, event A does not occur.
5. There is no need to take into account the time of different regions.
Below I have outlined the rotation for 24 hours
00:05 - Event А
01:05 - Event А
02:05 - Event А
03:05 - Event А
04:00 - Event B
05:00 - Event B
06:05 - Event А
07:05 - Event А
08:05 - Event А
09:05 - Event А
10:00 - Event B
11:00 - Event B
12:05 - Event А
13:05 - Event А
14:05 - Event А
15:05 - Event А
16:00 - Event B
17:00 - Event B
18:05 - Event А
19:05 - Event А
20:05 - Event А
21:05 - Event А
22:00 - Event B
23:00 - Event B
|
Given you can't see the inconsistency between what you described and what you listed there's little chance of getting a result. It can't all be just translation because you are not addressing each step (process) as being seperate and different.
- Describing Event A intervals 1 hours, listing 1 hour intervals
- Describing Event B intervals 6 hours, listing 1 hour intervals.
- Describing Event A duration 4 minutes, listing 1 hour intervals
- Describing Event B duration 2 hours, listing 1 hour intervals
In the code listed, the datablock is just a list of what looks like map pin locations, nothing to do with time.
Suspiciously cropped picture is suspicious, and not saying what you think it is...
Maybe it's because of the difference between the way the addon works and the way the event you want track works is why it's not included in the addon.
Just to finish up, another guess at what you are looking for (more actual processes being tracked with their own names and times). Still guessing you want to track the running/waiting periods of the same actual event.
1 Event, runs for 4 minutes.
1 Session, totaling 6 hours, repeating
2 Sub-Sessions (A and B)
Sub-Session A: Event lasts 4 minutes and interval between Events is 1 hour (4 minutes + 56 minutes repeating 4 times). Sub-Session A runs for 4 hours total
Sub-Session B: Event lasts 4 minutes and interval between Events is 2 hours (4 minutes + 1 hour 56 minutes no repeats). Sub-Session B runs for 2 hours total
Code:
Session Start (6 hours):
00:05 - Sub-Session А -- Event for 4 minutes
01:05 - Sub-Session А -- Event for 4 minutes
02:05 - Sub-Session А -- Event for 4 minutes
03:05 - Sub-Session А -- Event for 4 minutes
04:00 - Sub-Session B -- Event for 4 minutes
05:00 - Sub-Session B -- extended wait time
Session End:
Repeat (6 hours):
06:05 - Sub-Session А -- Event for 4 minutes
07:05 - Sub-Session А -- Event for 4 minutes
08:05 - Sub-Session А -- Event for 4 minutes
09:05 - Sub-Session А -- Event for 4 minutes
10:00 - Sub-Session B -- Event for 4 minutes
11:00 - Sub-Session B -- extended wait time
Repeat (6 hours):
12:05 - Sub-Session А -- Event for 4 minutes
13:05 - Sub-Session А -- Event for 4 minutes
14:05 - Sub-Session А -- Event for 4 minutes
15:05 - Sub-Session А -- Event for 4 minutes
16:00 - Sub-Session B -- Event for 4 minutes
17:00 - Sub-Session B -- extended wait time
Repeat (6 hours):
18:05 - Sub-Session А -- Event for 4 minutes
19:05 - Sub-Session А -- Event for 4 minutes
20:05 - Sub-Session А -- Event for 4 minutes
21:05 - Sub-Session А -- Event for 4 minutes
22:00 - Sub-Session B -- Event for 4 minutes
23:00 - Sub-Session B -- extended wait time
The addon you posted could work with the 6 hour session repeating. It doesn't "understand" sub-sessions or their variable nature (or differing running times of the actual event if the above is not correct in assuming it's only ever 4 minutes long).
I've spent too much time on this and I'm sure you're sick of hearing from me. I will leave it to you and others to try and find a workable solution for whatever it is you are wanting to do.
Have Fun!