Soft conflicts of BDS-NOV-2025.fet
Generated with FET 7.1.7 on 11/11/25 12:09 PM

Number of broken soft constraints: 10
Total soft conflicts: 9.2

Soft conflicts list (in decreasing order):

Time constraint min days between activities broken: activity with id=66 (    1/5 - Reetika - MAT - C7) conflicts with activity with id=64 (2/5 -     Reetika - MAT - C7), being 1 days too close, on days Mo and Mo, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=218 (    1/5 - Nikita,Annu - PE - BEG) conflicts with activity with id=214 (1/5 -     Nikita,Annu - PE - BEG), being 1 days too close, on days Fr and Fr, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=222 (    1/5 - Nikita,Annu - PE - L1) conflicts with activity with id=220 (    1/5 - Nikita,Annu - PE - L1), being 1 days too close, on days We and We, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=228 (    1/5 - Nikita - PE - L2) conflicts with activity with id=227 (    1/5 - Nikita - PE - L2), being 1 days too close, on days Tu and Tu, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=258 (    2/7 - Saloni - R2 HIN - C2) conflicts with activity with id=257 (    2/7 - Saloni - R2 HIN - C2), being 1 days too close, on days We and We, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=267 (    1/7 - Deepak - EVS - C2) conflicts with activity with id=265 (    2/7 - Deepak - EVS - C2), being 1 days too close, on days Mo and Mo, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=312 (    1/5 - Saloni - VE - C8) conflicts with activity with id=310 (2/5 -     Saloni - VE - C8), being 1 days too close, on days Sa and Sa, conflicts factor increase=0.95. The activities are placed consecutively in the timetable, because you selected this option in case the activities are on the same day
Time constraint min days between activities broken: activity with id=16 (    2/4 - Ashutosh - PE - OG - C8) conflicts with activity with id=15 (2/4 -     Ashutosh - PE - OG - C8), being 1 days too close, on days Mo and Tu, conflicts factor increase=0.85.
Time constraint min days between activities broken: activity with id=30 (    2/4 - Nisha - R1 ENG - C6) conflicts with activity with id=29 (2/4 -     Nisha - R1 ENG - C6), being 1 days too close, on days We and Tu, conflicts factor increase=0.85.
Time constraint min days between activities broken: activity with id=230 (    2/4 - Saloni - ARTS - BEG) conflicts with activity with id=229 (2/4 -     Saloni - ARTS - BEG), being 1 days too close, on days Mo and Tu, conflicts factor increase=0.85.

End of file.