Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Liviu Lalescu

#1
Dear Victor,

I will check tomorrow the code, or on Monday, and do the customization for you probably on Monday or a bit later. The constraints of type min gaps per real day will consider only from morning to afternoon. I think it is an easy change, and this is a bug fix/small feature change for you, absolutely free. It will be a customization for you.

The most elegant way would be to modify the official FET to include these 2*2*2=8 new constraints in the Mornings-Afternoons mode. This is probably simple, but long and tedious work. If other users/entities reading this post consider FET deserves a sponsorship contract for this or for other features, please feel free to contact me. I don't know if it's appropriate to talk about price publicly, but I can do this if it is.

Anyway, these 8 constraints will be added in the official FET TODO list.
#2
Dear Victor,

I deeply apologize for this problem. I think you lost much time until you discovered this problem. You assumed FET to be more intelligent than it is.

I will make you a customization, so that min gaps per real day will consider in fact from morning to afternoon only. I hope it is possible in the code. I am not home and on my usual computer. I will arrive home on Sunday evening, most probably. If it is urgent, I can try it tomorrow, but this computer takes 1 hour for a full compilation, and the internet is slower. Do you compile FET from sources? I could modify the file generate.cpp and email it to you, in this case.

The most elegant solution would be to add new constraints in the official FET: teacher(s)/students (set) min gaps between activity tag/ordered pair of activity tags between morning and afternoon. If any institutions are interested into a sponsorship contract for this new feature, I will try it. Otherwise, I will add this in the TODO list.
#3
Dear Victor,

I have doubts I understand correctly your suggestion:

1) You need this change because your situation is incorrectly handled, meaning FET will constrain the timetable more than it is needed? Or it is just a cosmetic suggestion you are making?

2) I think we cannot make the official FET consider "per real day" for this constraint to consider "between morning and afternoon". If it is really needed (see 1), I could think of maybe a new constraint, teacher(s)/students (set) min gaps between ordered pair of activity tags between morning and afternoon. But the name is long, I doubt other users would need it, and I think and hope it is not really needed (see 1).

Or a customization, just for you.
#4
You are welcome, szachariah. I'll wait, then. For CSV, I will need the students.csv and activities.csv (and maybe the rest of the CSV files, if you want).

If the initial file is private, you can send it by email and it will remain private. But I completely understand if you only want to send anonymous data.
#5
Hello, Victor,

Indeed, per real day means that FET will consider for instance Monday=Monday morning+Monday afternoon, and check the constraint min gaps between order pair of activity tags for this whole Monday. This is how all the FET constraints for the Mornings-Afternoons mode for real days work. Think for instance of max hours daily per real day, or max gaps per real day. I cannot make, logically, this constraint (min gaps), to consider only from start=morning and end=afternoon.

I hope this is not a problem for you; otherwise, maybe a customization is possible, or we need to talk about the official FET modification, but I hope not. But your custom version worked OK before I added this new constraint in FET, isn't it?

Please let me know.
#6
Hello, @szachariah ,

Thank you for your flattering words! Over 100 hours of learning is impressive!

You should be able to use activities with duration 3, and your preferred starting times should be OK, and your CSV. Please send me your CSV files and fet file, so I can have a look (here, archived, if public, or by my email). FET will never put 3 or more subactivities on the same day if they have a min days between activities constraint, so it can put 3+3=6 hours on a day.

Also, in your first approaches, if a teacher crosses divisions, maybe you could use some constraints which were added recently, the constraint of type teacher(s) max hours daily in hourly interval. But I would prefer 15 minutes "FET hours" if possible.

Please let me know.
#7
Buonasera, Fabrizio,

Scusi per l'inglese:

Unfortunately, I cannot find it either, also I searched on the internet for other mirrors but could not find it. You might want to check the English manual by Volker, and maybe translate it to Italian with Google translate.
#8
You are welcome! Thank you for your kind words! I hope FET will be helpful.

Note: FET allows 1440 "hours per day", but I would recommend you to use a FET hour = 20 real-life minutes, so you don't have too many FET hours per day. We did not test I think more than 90 FET hours per day, or have reports from users about this. But it might work.

Also, I might have been wrong with my suggestion regarding the tutorials. You don't know ahead of the time which 3 tutorials should be consecutive. We might need to think of something else, in this case, maybe even a customization. You could use a constraint teacher activity tag max 3 hours consecutive, but this will not guarantee that FET will try to group the 3 of them together.

I think CELCAT is another timetabling package? May I ask why you decided to use FET for generation and then import into CELCAT?
#9
Hello,

FET does usually a weekly timetable. But the number of allowed days per week is very large (1000), so you can implement the timetable for a whole year. Also, for this purpose we developed the Terms mode (used in Finland), having 4 additional types of time constraints (you can see them last, in the activities time constraints for this mode).

You could add each separate student as a FET subgroup, in a group/year.

There is a constraint type 3 activities grouped, or activities same starting day and max hourly span between a set of activities.

If you decide to add 365 FET days per week, it might work, but the timetable for each real week will be different, unless you add many constraints to take care of this.
#10
Arabic / عربي / Re: suggestion
May 13, 2024, 12:14:35 PM
You are welcome!
#11
Arabic / عربي / Re: suggestion
May 12, 2024, 05:06:36 PM
If the interval is a,b, it is considered like in mathematics: [a, b), meaning that a is included and b not included. Please try on a small example to check that it will allow room in b to be different than the room in a or a+1.
#12
Arabic / عربي / Re: suggestion
May 12, 2024, 03:20:00 PM
Please add as I suggested, 1,3, it is like you need. 3 is not included.
#13
Arabic / عربي / Re: suggestion
May 11, 2024, 07:22:42 PM
Please add [1,3) and [3,end of day).
#14
You are welcome!

If you have only Building 3 and Building 4 in your data, or you can reduce all your buildings to these two buildings (like ignoring Building 1, 2, 5, 6, ...), you can use the official FET with a constraint students min 1 gap between building changes.

Otherwise (if in your timetable you need to consider all the buildings, for other buildings constraints), you need a customization.

Or, another possibility to avoid the customization would be to add a tag AT3 to all the activities in Building 3 and a tag AT4 to all the activities in Building 4, if this is possible (if you know the building of each activity before generating), and use 2 constraints students min gaps between ordered pair of activity tags, one between (AT3, AT4) and the other between (AT4, AT3).
#15
On Wednesday, 8 May 2024, FET-6.19.5 was released. From the ChangeLog:

  - Corrected the two Windows batch files which start the program in the Fusion / Windows styles, to take care of possible spaces characters in the path to the FET executable (bug reported by Khafallah Oualid).
  - Minor corrections.