User`s guide

38 Scheduler
Double Occupancy: When Two Events Occupy
the Same Slot
If you plan on having a fairly complicated show, you may want to be sure you
don’t have events competing with each other for execution when their time and
date come around. This discussion looks at what happens when to events end up
on the same time and date. It explains the rules used to determine which event
wins.
¾ Definitions
The following are previously undefined terms used in the Scheduler Rules
discussion below
• Timestamp - time portion of the event's starting point (T: and D: )
• Datestamp - date portion of the event's start point (T: and D: )
• Slot - the event's timestamp + datestamp.
• Startslot - slot when the event begins (required)
• Endslot - slot when the event ends (not required)
• Profile - an event’s startslot, endslot, type (defined below)
• Double Occupancy - two events in the same slot.
The following types of events exist in the DVMHD:
• One-shots -One time events with no repeat
• Loops - Repeating events
• Finites - loops that have an end time and end date
• Infinites - loops with no end time or end date
• Active Event - events with today's datestamp that have been or will be
loaded into the queue
• Executable Event - events with the current timeslot.
• Start Time Bootups - events with start time listed as BOOT.
• Repeat Period Bootups- events with repeat period listed as BOOT.