Messages

Now I have a new problem - the dataset is too large. We have one year with 6 categories each with 6 or 7 groups. 7*7*6*6*6*6 = 63504 subgroups for just a single year. How do I get around that problem?

Thank you so much - this makes a lot more sense now and it seems to be working as expected.

I've read a few different documents about groups and sub groups and I still don't understand how to use them correctly in my case.

I've attached a cut down version of our timetable.

• Year 8 is a group of students of the same age
• The groups are sets of students that attend classes
• I thought sub groups were possible combinations of groups which could run at the same time but that is obviously wrong

This is how year 8 is split:

• There is a maths line (8MA1 - 8MA5). If a maths group runs then all the maths groups should run and no other year 8 group should run
• The year is then split in to the top and bottom of the year
• The top students are split into 3 different lines: 8A, 8B or 8CAPA1, 8CAPA2, 8CAPA3 or 8TM1, 8TM2, 8TM3
• So if 8A is running in a time slot then 8B should also run but not 8CAPA1 - 8CAPA3 or 8TM1 - 8TM3. If 8TM1 runs then the other TM classes should run but not the CAPA classes or 8A or 8B
• The bottom of year 8 is split similarly with 8M, 8R, 8U or 8CAPA4 - 8CAPA7 or 8TM4 - 8TM7

I don't understand how I'm meant to enter this information in to FET. Last year I used ConstraintActivitiesNotOverlapping to make sure these groups didn't over lap but there must be another way. What would be really useful is a student constraint that defines groups that can't overlap - that would make more sense to me.

Thanks for any help.