The Min Days between activities constraint has a weight percentage which I set to 95%.
I think that there should be another weight percentage for the option "if activities in same day, force activities consecutive" (when checked) because you handle it as a 100%.
If this is possible, then the word force should be replaced by something else.
I think what you suggest would complicate things too much. I am not exactly sure why in the past I came up with the present design, but it was a long-thought solution.
I could add your suggestion in the TODO, if you like.
You can do something similar already.
Just uncheck the forced consecutive checkbox and add an 2 activities are consecutive constraint with an lower weight.
But like i always said:
I highly don't recommend to use weight lower then 100%.
Example of my school dataset:
I added all activities and constraints with 100%. As always.
The first run running with only 100% failed, because there was one imposible min n day constraint.
I wasn't sure if it is a min n day constraint bug or not. So i set all min n day constraint to 0%. FET solved the data in less then 2 minutes. So it was clear, there must be at least a min n day bug.
I searched and found that bug and solved it by removing a single 100% weight constraint.
Then the data is solved in around 3-6 hours without a single conflict.
Then, just for fun i done one more test. I done it like many guys do it. They are to lazy to search a bug and simply use 95% weight constraint. So I set all min n day constraint to 95%.
I run it 4 times always 24 hours long.
Result: 3 times doen't found a result in 24 hours. One time it found a result after 2 hours with 20 conflicts.
So i hope you understand why i always recommend using only 100% weight. Of course you need to think a bit, but overall you will be much faster and get a much better result!
Quote from: Volker Dirr on February 08, 2014, 01:32:40 PM
You can do something similar already.
Just uncheck the forced consecutive checkbox and add an 2 activities are consecutive constraint with an lower weight.
No, it is not the same as what he needs, because he wants them consecutive only if they are on the same day. You constrain too much.
i know it is not 100% the same. but it is similar to what he want: not 100% consecutive.
But never the less:
Like i said: Everyone should use only 100% weight, because that is much faster and better. I don't get why guys always want to save 5 minutes of searching a bug and set constraint to lower then 100%. They must wait much longer and don't get perfect results. Just spending 5 minutes bug hunting with 100% weight constraint and you will get perfect timetable in less time.