Messages

After careful consideration, I think it's normal, because the generation lags due to several factors,
including the algorithm and the set of mathematical combination, since it can't be the same running in both files.

Don't you agree with me on that?

The file was sent, via e-mail because of its size, which is kind of not ideal in using constraints, especially with the case I'm dealing with.

I've tried the version and can say it works as it should be:
The experiment was carried out with constraints of the type:
- Max zero gaps per afternoon.
- Max gaps per week.
- Max gaps per day (with 1 gap per day, with the new rule, the generation process was delayed a lot, but it was completed without any problems or errors in the outputs.)


BTW, You're literally a hero!

once again, thank you very much, dear liviu.

dear liviu,
As usual I was sure you would be able to do it, take your time
Thanks again my friend.

Aha I get it now, it will be included by default without needing to add the condition.
Yes, the condition needn't be for students only for teachers, because we always have condition 0 gaps in student schedules.

I wish it was somehow built into the official release, because you might be releasing new updates in the official app and I wouldn't be able to use it if I needed that condition.

Hello liviu,
Do you mean that the rule only has a max 1 and the number cannot be incremented?
If so, then it is really required, as the most important condition we have here in Algeria for good timetables is to adopt one gap per day (morning+afternoon), and of course this does not affect the gaps throughout the week.

Waiting for the implementation

If i am well aware of the first solution, the problem is that you do not know the teacher who has this issue, and allocating these conditions to a group of teachers will complicate matters.

I wish you could provide an implementation, which would be beneficial to many, and the priority of the proposed solution and its efficacy is far from how much I need it soon. The important thing is that you can achieve it, my dear friend.

have a nice rest first, I am well aware of how difficult it is to implement, and how complicated things are, thank you for every second you are taking for this project.

The problem is in my case and perhaps in many cases it is very difficult to put max 1 gaps per week, that hinders production and makes it very long hours.

Also, as for the use of the max gaps in the afternoons, I think that it may hinder the maneuvering process in the generation, especially that the gap can occur in the morning or afternoon, but the worst is that it occurs in morning and afternoon.

Of course, you know best what the situation requires, my friend, and your point view is often the correct one.

Hello dear Liviu,
I hope you are always well.

I have a little issue which is the number of gaps in the Morning + Afternoon.
If we choose the max gaps per week, for example, two gaps, it can put the first gap in the morning and the other gap in the evening in the same day, which is rather bad.

So I suggest adding a new rule named Max gaps Morning + Afternoon.

Of course, this is different from the max gaps per real day, as it is worth renaming it the length of the gap, and here the number can be chosen from zero, so the timetable is stacked between morning and evening, and among other numbers as desired.

congratulations dear Liviu,
Today, I downloaded the new version, and I also built it , for theme's integration in linux with GNOME environment.
You surprised me, dear, with my name in the "thanks to" window, this is a great honour for me.
Thank you very much for your amazing work.

Hello dear Liviu.
Thank you very much for the compliment, as usual you are doing an amazing job and my participation it is just a small drop in the ocean of your great work.
I understand you very well especially at the point that you may add new modes in the future, it really should be in the user interface.
Also for the first suggestion you are right, in case many tables are desired you can put the number of tables once and wait

Thank you for the explanation and for your hard work.

I suggest adding settings to choose the default mode of operation.
Meaning instead of choosing the The mode of operation every time through the menu New, just I go once to settings and i set my default option.
Why should this preferance exist? Because the Custom FET versions are basically each one belonging to a specific country or group, so I think it is better for me to choose the mode once in the settings instead of choosing every time I create a new file!
Thus, your work is wonderful in the endeavor to collect all copies in one copy, and at the same time it is easy to use the program as if it is directed to a specific mode.
Of course, these settings are optional, they can be edited by the user, or they can be left as they are now.
What do you think?

I think I understood the reason for the delay in the case of a single schedule, on N threads.
Fet does not launch parallel execution. Rather, it launches the same file to execute in N threads, and the one that ends the first is the one that is taken into consideration. Correct me if I am wrong?
In the case of multiple generation of N timetables, of course, it waits for each thread to end on its own and then gives all the results!

After several tests on the file that i sent above, with the new version, the execution time with 4 threads takes a long time (12 minutes) more than the normal execution (7 minutes)!?
Could this happen normally?

Practically I did not encounter the crash issue again.
I think the issue is solved.
Only I have a suggestion in the case of multiple timetables why I should delete the output folder every time, why the files are not output in new folders with the same name with a number's suffix , 1,2,3 etc.

Well my friend, good night and sweet dreams.
Tomorrow we will complete the qt investigations 

Don't be sorry my friend, you are doing an amazing job and we have a duty to help as we can.
I am currently doing different tests on multiple files, so far the problem has gone, it's working perfectly, I will run more tests and tell you.
Thank you for your precious time