Durata elaborazione

[henozzo]

Se lancio la generazione di un orario mi sembra che i progressi più significativi si abbiano nei primi secondi. Se non ottengo una generazione vale la pena lasciar lavorare FET per ore o dopo i tentativi iniziali la possibilità di soluzione è scarsa o nulla?

[Liviu Lalescu]

Scusi l'inglese:

It depends on the file. There are most files which do not require a restart, and some files which require restart. This is to be appreciated by the user.

You might want to share with us your file, for an appreciation.

[henozzo]

Eccolo

[Liviu Lalescu]

Indeed, it seems like a file where restarting is useful. I generated on 8 threads (I have 8-core processor), and after a few minutes I got 6 360/361 and 2 359/361. I will try now automatic restarting after 3 minutes.

I am not sure, is your timetable possible or not?

I saw that the only constraints with weights <100% are min days between activities. Maybe these are posing problems. One of my methods were to inactivate all min days between activities constraints and see if the timetable is possible. If yes, enable all back and lower weight of the constraints min days between activities for the impossible activity.

Hmm... your timetable seems impossible. I will try to find the problem. If you managed to obtain a solution let me know.

[Volker Dirr]

I guess restarting after only 3 minutes might be too less.
I got 360 after a minute on all cores. It might be possible. I suggest to run it on multiple cores with maybe a time limit of 20 minutes and run it over the whole night.

[Liviu Lalescu]

Sorry to disagree, Volker, but if after less than a minute it goes to 360/361, I think 3 minutes is enough. Maybe say 5, or 10.

I think the file is impossible; I further deactivated all min days between activities constraints and is still impossible, after less than 30 seconds I got 360/361 on each of the 8 threads.

[henozzo]

I've never succeeded so it's possible it's impossible

[Liviu Lalescu]

I deactivated all space constraints and it solves very easily (first solution after 13 seconds or so, in generation on 8 threads).

I deactivated only the home room for Zanca (because activity ID 520 is the last), but unfortunately the timetable is impossible. So it is the combination of space constraints, not only for the last activity.

So, please try to make easier your space constraints. Add more rooms. Or better: lower the weights of preferred and home rooms, to maybe 99% or 99.75% or something, and see, if you obtain a solution, where you get a soft conflict for space constraints, and there is the culprit.

[Volker Dirr]

Maybe, to speed up, the warning about similar subgroups should be fixed first.

[henozzo]

In your opinion what can I do to try to complete the timetables. I use 90% a lot of space constraints, but doesn't work

[Liviu Lalescu]

I removed all your space constraints and min days between activities time constraints and it goes very fast to 357/361. Please check the other constraints. Remove some of them, try again, and so on.