Understanding new constraints

Started by maxi_mus, February 06, 2026, 05:08:07 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

maxi_mus

Hi, I have a question regarding new constraints that are added to FET:

Let's take as an example the new constraint that was added in 7.5.1 on 1.10.25:

Activities occupy max sets of time slots from selection
(initially max = 1 or 2)


I think I understand what this means, but I'm not quite sure. What is the best way in your opinion to understand new constraints like this?

In the documentation, this rule is still listed as TODO. So is the text in the release notes basically the only information available? Is the best way to understand it to just try it out in FET?

Thanks for any help.


Liviu Lalescu

Hello, maxi_mus,

I hoped the name of the constraints and options are self-explanatory.

Please tell me the TODO item number which needs removal/update!

Yes, the (only) information is in the ChangeLog, in the code, trying it practically in FET, or asking on the forum.

maxi_mus

The following rules are still TODO in the manual:

A set of activities occupies max time slots from selection
Max simultaneous activities from a set in selected time slots

But there's no need to expedite the manual for me, I was only trying to find out what the best course of action would be. I will try it out in FET and get back to you in the forum if I don't understand, thank you  :)

Liviu Lalescu

You are welcome!  :)

I thought you were talking about the TODO file from the FET distribution. It has a list of suggestions.