Dear Pierre,
I am not sure what you want to accomplish. It is possible to define alternative date patterns (e.g., every other week date pattern allowing the solver to choose either even weeks or odd weeks). If there is only one class, there can be only one combination of date pattern, time pattern, day(s) of week and start time however.
You can create a date pattern of type alternative pattern set and than attach different date patterns to it (a date pattern can be in multiple sets). So, for instance, I can create an "Every Other Week" date pattern:
And that edit Event Weeks and Odd Weeks date patterns and add them to the Every Other Week date pattern:
(see the Alternative Pattern Sets drop down).
Similarly, I can create a "1x" date pattern that contains all the single week date patterns Week 1, Week 2, ...
Now, when such a date pattern is selected on a class or a scheduling subpart, this will mean that the class must choose one of the date patterns of the set. Here is an example for the Every Other Week date pattern:
You can even put preferences on each date pattern (e.g., even weeks could be preferred to odd weeks) -- see the Date Pattern Preferences section.
It is also possible to let UniTime timetable all meetings individually, but it means that multiple classes have to be set up for the course. Here is an example:
The ART 105 is a distance study class that meets three times a semester (Friday or Saturday), it has two meetings of 10 hours and one of 9 hours. Is is also possible to set (in the solver configuration, parameter Automatica hierarchical constraints) that classes of 1x date pattern that are nested like on the screen shot above have to be on different weeks (prohibited same weeks distribution), and preferred to be placed in the same room and in given order (preferred same room and preferred precedence distributions).
Regards,
Tomas