Karim Osman, Sven van Hal

Automated timetable generator.

Prerequisites: a MS SQL database with a compatible schema.

1. Clone this repository
2. Rename Implementation/connection.config.example to Implementation/connection.config and configure the database connection string.
3. Open BEP.sln in Visual Studio.
4. Right click on the Implementation/connection.config and choose Properties. Change "Copy to Output Directory" to "Copy always".
5. Build the solution and run the Implementation project.

To generate timetables, include the Timetabling project in your solution. To fully utilize this library, the following four classes are relevant:

• Timetabling.TimetableGenerator
• Timetabling.DB.DataModel
• A Timetabling.Algorithms.TimetablingStrategy subclass, e.g. Timetabling.Algorithms.FetAlgorithm
• Timetabling.Helper.DatabaseHelper (optional, to save the generated timetable)

The timetabling algorithm runs asynchronous and is wrapped in a Task<Timetable> (docs). To create the task, execute the TimetableGenerator.RunAlgorithm(strategy, model) method with a TimetablingStrategy and a DataModel:

using (var model = new DataModel(StageId))
using (var generator = new TimetableGenerator())
{
    Task<Timetable> task = generator.RunAlgorithm(new FetAlgorithm(), model);
}

The algorithm has now started running in the background. By attaching task continuation handlers, the task output can be processed:

task.ContinueWith(OnSuccess, TaskContinuationOptions.OnlyOnRanToCompletion);
task.ContinueWith(OnCanceled, TaskContinuationOptions.OnlyOnCanceled);
task.ContinueWith(OnError, TaskContinuationOptions.OnlyOnFaulted);

Use DatabaseHelper to save the timetable to the database. The OnSuccess handler could be used for this purpose:

public static void OnSuccess(Task<Timetable> task)
{

    using (var db = new DatabaseHelper())
    {
        Timetable tt = task.Result;
        db.SaveTimetable(tt);
    }

}

By default, the DatabaseHelper operates on a new database connection. A DataModel can be passed to its constructor to override that behavior.

All algorithm tasks created by TimetableGenerator.RunAlgorithm(strategy, model) can be canceled by calling TimetableGenerator.StopAlgorithm().

Currently, not all required meta data about the timetable (e.g. AcademicYearId, SectionId and QuarterId) is retrieved from the database. This data can therefore optionally be set (and consequently saved to the database) by altering the OnSuccess handler:

public static void OnSuccess(Task<Timetable> task)
{

    Timetable tt = task.Result;

    // Set meta data
    tt.AcademicYearId = 1;
    tt.QuarterId = 2;
    tt.SectionId = 3;

    // Save to database here

}

An example implementation (aptly named Implementation) project is included in the solution.

The FET algorithm is configured by an XML file containing all resources, activities to schedule and constraints. To add a new constraint, perform the following steps:

1. Add a constraint class which extends AbstractConstraint in Timetabling.Objects.Constraints. Please refer to existing FET input files and the documentation at this page for the correct XML constraint output.
2. Update Timetabling.Algorithms.FET.FetInputGenerator to include your new constraint.
3. Add tests in Timetabling.Tests.Objects.Constraints for the new constraint.

N.B.: the FET constraint system is rather complicated and its behaviour might not be intuitive when combining constraints. Make sure to test a new constraint thoroughly before using it in production.

The project currently bundles FET 5.36.0. To upgrade FET, perform the following steps:

1. Download the latest FET release from the download page.
2. Upgrade the FET binaries in Implementation project by replacing the relevant files in lib/fet/.
3. Upgrade the FET binaries in Timetabling.Tests project by replacing the relevant files in lib/fet/.
4. If the FET file structure has remained unchanged, the version number in Timetabling.Algorithms.FET.FetInputGenerator should be changed as well.

This project uses the command-line version of the open source timetable generator FET. The Windows binary in bundled with the project.

A separate Timetabling.Testing testing library is available containing unit tests. The tests can be run with NUnit 3.