Hello, Anthony!
The board for this post is correct.
1) Please open the fet file with an XML editor or text editor. Search for <Time_Constraints_List> and </Time_Constraints_List>. Between these two are the time constraints, such as: <ConstraintTeacherNotAvailableTimes> ... </ConstraintTeacherNotAvailableTimes>. Please see an example of how this constraint is written in XML. Just add new constraints in this section, anywhere, but not inside an existing constraint.
2) Min days between activities constraints accumulate weight (the weight is stronger on two or more constraints for the same activities). You need to enable level 1, XOR level 2, XOR level 3, not two or more simultaneously. The reason for accumulation is that FET checks each constraint in turn.
You can activate/deactivate all constraints of a level with an advanced filter for comments, select all of them, and click activate/deactivate.
Activities preferred times constraints: for each activity, each cell of a table n_days x n_hours takes the maximum of each constraint as the final weight of not allowed, and FET only checks once the constraint for each activity.
You're welcome!
The board for this post is correct.
1) Please open the fet file with an XML editor or text editor. Search for <Time_Constraints_List> and </Time_Constraints_List>. Between these two are the time constraints, such as: <ConstraintTeacherNotAvailableTimes> ... </ConstraintTeacherNotAvailableTimes>. Please see an example of how this constraint is written in XML. Just add new constraints in this section, anywhere, but not inside an existing constraint.
2) Min days between activities constraints accumulate weight (the weight is stronger on two or more constraints for the same activities). You need to enable level 1, XOR level 2, XOR level 3, not two or more simultaneously. The reason for accumulation is that FET checks each constraint in turn.
You can activate/deactivate all constraints of a level with an advanced filter for comments, select all of them, and click activate/deactivate.
Activities preferred times constraints: for each activity, each cell of a table n_days x n_hours takes the maximum of each constraint as the final weight of not allowed, and FET only checks once the constraint for each activity.
You're welcome!
