Tablix distribution includes several example problem definition files that are based on information from real schools. This page contains links to example solutions to some of those problems that were found with Tablix.
The first example file, sample2.xml, describes a relatively simple timetable problem for a middle-sized four year high school.
Students in the first and second year (classes 1 A through 2 D) have fixed timetables. Students in the third and fourth year (classes 3 A through 4 D) have fixed timetables with one exception: each student can choose to attend one extended course on natural sciences and one extended course on social sciences.
Fixed part of the timetable includes several lectures, for example mathematics (MAT) and English (ANJ). Some lectures can be held in any classroom, while others, like chemistry (KEM), biology (BIO) and physics (FIZ), must be scheduled in specialized laboratories.
Extended courses, like physics (MA-FIZ), chemistry (MA-KEM) and sociology (MA-SOC) are shared between all students of the same year.
This school has 40 general-purpose classrooms, 11 special-purpose labs and employs 28 teachers. Lectures start on Monday morning and end on Friday afternoon. There is a maximum of 7 lectures per day.
The second example, tough2.xml, also describes a high school. This timetable is more complicated than the previous one because this school resides in a very small building. Most lectures have dedicated classrooms, but some lectures can be scheduled in any classroom that isn't a specialized lab.
Similarly to the previous example, students in the first three years have fixed timetables while students in the final year attend a number of mandatory courses and can additionally choose to attend one of available optional courses (defined in the "4 MA-" classes in this file).
All students have three hours of mandatory physical exercise (SVZ) per week. Because of the lack of space some classes share the use of the gym with other classes. Groups for physical exercise are divided into groups for girls and groups for boys.
The final example, uni.xml, is an example of university scheduling. It also shows how a large timetable can be separated into multiple HTML pages.
This file contains a complicated timetable problem for two faculties sharing the same building. The solution shown here took approximately 33 hours to compute on a single computer with an AMD Athlon XP 2500 processor.
"class" type resources with names "Class ..." represent groups of students that share the same timetable. Two events for one "Class ..." resource must not happen at the same time. The groups include for example "1. year of study of subject X, 1. faculty", "4. year of study of subject X, 2. faculty", and so on. Sometimes there are too many students in the 1. year. In that case these groups are divided even further into subgroups that have the same curriculum, but visit lectures at different times. These subgroups are also included in the "Class ..." resources.
Each group of students attends several different lectures. Lectures have their own "class" type resources with names like "Title ...". If a group of students "Class 000" attends lecture "Title 000", this means that "Class 000" conflicts with "Title 000" in this XML file.
Some groups of students share the same lecture if the size of the classroom permits (for example, groups "Class 000" and "Class 001" share the lecture "Title 000 P Cikel:1") A lecture can be composed of individual blocks, each block taking one time slot. Blocks are represented with events. Some lectures take only one block per week, other take three or more.