Max Hours for a room(s)

Benahmed Abdelkrim · June 17, 2022, 11:34:26 AM

Quote from: Liviu Lalescu on June 17, 2022, 10:19:56 AMHello, dear Benahmed,

I will try in the future. Please remind me how this version worked and show me how do you suggest MTR in FET interface. Were these "MHPW, MHPD, MTR, MSPD" comments for each room? Should I make MTR a global variable and disable in rooms comments?

I think it is better to integrate the nsrt version of FET by adding a new mode; called: nsrt mode, to better guide users. this mode is reserved only for making exam timetables...

The most important constraint is MTR, for the others (MHPW, MHPD, MSPD) I suggest leaving them as they are in the comments. the future will show us their destinies. personally I use the constraint: "a room's not available times" instead of them..

This solution I found it using set theory, the solution became simpler without the use of these 3 variables (constraints: MHPW, MHPD, MSPD) except MTR.

I think this way made coding easier(!?)
what do you think?

Benahmed Abdelkrim · June 17, 2022, 12:32:15 PM

I forgot to say; this version works very well, it has transformed the timetables of exams easy to design. I suggest adding MTR to each room individually, and to all rooms at once.

Liviu Lalescu · June 17, 2022, 04:11:21 PM

I am sorry, but I think I cannot add a new mode for this. Your method is not universal and seems a bit weird to me, switching teachers with rooms. It is not FET style, and I think there are only a few users.

I could:

1) Update your NSRT custom version to the latest FET, and keep all the mode of operation. I am sorry, but switching from comments to the interface is difficult now, especially since there are data files using the comments structure.

or

2) We could collaborate and use the official FET to design exam timetabling for your precise needs. I had another idea in my previous posts, but it seems that you did not like it.

I am very tired now, just arrived. But we will work on this a few hours later from now, if you want.

Benahmed Abdelkrim · June 17, 2022, 05:33:48 PM

OK you convinced me. I think we should leave things as they are, at least for now and just update -if you want- the NSRT custom version to the latest FET.

Thank you dear Liviu for your interest

Liviu Lalescu · June 17, 2022, 06:12:42 PM

I will try a bit later to update, it shouldn't be difficult.

Thank you for your understanding, and I am sorry!

Benahmed Abdelkrim · June 17, 2022, 06:24:05 PM

Quote from: Liviu Lalescu on June 17, 2022, 06:12:42 PMI will try a bit later to update, it shouldn't be difficult.

Thank you for your understanding, and I am sorry!

No problem at all. Thank you to you too dear Liviu:-)

Liviu Lalescu · June 17, 2022, 09:41:17 PM

It is done: https://lalescu.ro/liviu/fet/download/custom/nsrt/

Also search for updates will work, it is special for NSRT.

Benahmed Abdelkrim · June 17, 2022, 09:52:45 PM

Great, thank you so much dear Liviu:-)

Liviu Lalescu · June 17, 2022, 09:54:49 PM

You are welcome!

Benahmed Abdelkrim · November 09, 2024, 01:00:55 PM

Hello dear Liviu
only if you have time, and if you are willing to update FET-nsrt to the latest FET version.

Liviu Lalescu · November 09, 2024, 01:21:26 PM

Hello, dear Benahmed,

I am willing, but I have no time, because I am working on massively converting all time/space constraints to shorter and better code. I worked on this ~5 days and maybe I have 3 more to work. After I will hopefully release a new official version, 6.28.0, I will also try to update NSRT.

I will combine 2628 files in only 4, simpler, and compilation time will be much shorter. Also, translation will go from >20k fields to maybe only 5000, without major repetitions.

I will, after I hopefully finish, put a snapshot and ask users to test. I hope in 3-5 days I'll have a snapshot.

If it is very important and urgent, I can try to update NSRT to 6.27.0 now, but I hope not.

Benahmed Abdelkrim · November 09, 2024, 01:36:55 PM

Thank you for your detailed response, as always... no, it's not urgent, we can leave the update until the next release. 🙂

Liviu Lalescu · November 09, 2024, 01:39:21 PM

You are welcome! Thank you! Please, if I forget, remind me after I hopefully release official FET-6.28.0.

Benahmed Abdelkrim · November 09, 2024, 01:48:23 PM

Quote from: Liviu Lalescu on November 09, 2024, 01:39:21 PMYou are welcome! Thank you! Please, if I forget, remind me after I hopefully release official FET-6.28.0.

Ok sure!

Quote from: Liviu Lalescu on November 09, 2024, 01:21:26 PMHello, dear Benahmed,

I am willing, but I have no time, because I am working on massively converting all time/space constraints to shorter and better code. I worked on this ~5 days and maybe I have 3 more to work. After I will hopefully release a new official version, 6.28.0, I will also try to update NSRT.

I will combine 2628 files in only 4, simpler, and compilation time will be much shorter. Also, translation will go from >20k fields to maybe only 5000, without major repetitions.

I will, after I hopefully finish, put a snapshot and ask users to test. I hope in 3-5 days I'll have a snapshot.

If it is very important and urgent, I can try to update NSRT to 6.27.0 now, but I hope not.

I read good news, I hope that these major changes will have good repercussions on the translation, which would be simple and would allow a significant saving of time.

Liviu Lalescu · November 09, 2024, 01:55:19 PM

Indeed, quote from the ChangeLog: shorter compilation time, smaller package sizes, less fields to translate, nicer looking constraints dialogs. The first three are with "much"

If you want to help me with testing, please stay tuned. The time/space constraints' dialogs should have the exact same functionality - this is the test.

I am ready with time constraints - remaining are space, which are much less and easier. I hope in maximum 2-3 days to have a snapshot for you. I will announce on the Snapshots section here, and maybe put a link on the main FET page for test, which I did not do until now.