Validation

Top  Previous  Next

No matter how meticulously we prepare and enter the timetable information, there could be typos, or oversights that creep in. These problems could make a timetable unsolvable if not corrected. In the example below:

 

ValidationErr1

 

This highlights potential problems that we might face in trying to solve the table. Examining T.Jones further:

 

ValidationErr2

 

The image above reflects T. Jones' timetable configuration. T. Jones' teaching schedule:

 

ValidationErr3

 

This shows that we need a minimum of 7 periods per day to cater for this constraint. In this case above, we could actually get away with this!!!

Looking at the required periods per cycle, we see LO and the Zulu/Tsonga/Sotho groups requirements of 2 and 3's respectively in a 5 day cycle, so there is the possibility that we can overlook this validation error.

 

Here is a list of the Validation Errors currently spotted by the program.

 

No days or periods entered.
No Educators, Classes, Rooms, or Subjects defined.
Orphaned Groups removed.
Not enough periods for Educators, Classes, Rooms, or Subjects.
No Educators, Classes, or Subjects in a group.
No Periods per Cycle for a Group.
No Maximum Periods per Day for a Group.
The Maximum Periods per Day for a Group is too low for the number of Periods per Cycle.
The Minimum Periods per Day for a Group is too high for the number of Periods per Cycle.
Not Enough days in the Cycle for the way the exclusions are set.
Not enough Periods per day based on the Minimum Periods per Day.
Not enough Periods per day based on the Maximum Periods per Day.