Dividing into years, groups, subgroups

[mimooh]

Hi again!

Still preparing my data for FET, can't wait to finally run it for real. I am
reading the FET documentation and as it says the concepts for years, groups,
subgroups are a bit vague. So perhaps I could ask you to name the entities I
have in our University:

ABC is the name of the largest group of students. They sometimes meet on
lectures. ABC.2018 starts their studies in 2018 and stays for 4 years under the
same name.

ABC.2018 (60 students meet during lectures)

   ABC.2018.ex1 (30 students meet during exercises)

      ABC.2018.ex1.lab1 (15 students meet during laboratories)
      ABC.2018.ex1.lab2 (15 students meet during laboratories)

   ABC.2018.ex2 (30 students meet during exercises)

      ABC.2018.ex2.lab3 (15 students meet during laboratories)
      ABC.2018.ex2.lab4 (15 students meet during laboratories)


DEF.2018
   (...)

ABC.2017
   (...)

DEF.2017
   (...)


Hopefully the schema is self explaining. I assume this is how I should organise
the data:

ABC.2018 is a FET year
ABC.2018.ex1 is a FET group
ABC.2018.ex1.lab1 is a FET subgroup

is this correct? Just to make sure: students having lab3 now cannot have ex2 or
lecture at the same time.

Also, in case it matters for how to organise my schema: in our university each
student is fixed to his group and to the subjects he will learn. He doesn't have
an option to go for optional courses (as in most of universities).

Also, am I supposed to call my subjects: Math.lecture, Math.exercises?
Otherwise, if I just publish the schedule with just the name "Math", how would
students make distinctions between all the forms (lectures, exercises, labs)?

Thanks in advance,
Regards!
Karol

[Volker Dirr]

The concept itself is not vague. It is only vague to underatnd for some users.

Your idea of years, groups and subgroups is only correct as long as for example there is no student in ABC.2018.ex.lab1 and the same guy is not in ABC.2018.ex2.lab3.
Because that activities might be at the same slot.

Did you read only the FET internal help or also my manual? ( https://www.timetabling.de/manual/FET-manual.en.html#id_12 )
Please also watch https://www.youtube.com/watch?v=qEuujWuu0oI . You will understand the concept hopefully better than.

About the "Math" question:
There are 2 variants:
1) The variant you already wrote: Adding several subjects like "Mathe.lecture" and "Math.exercises"
2) Add only subject "Mathe", but tag the activities with activity tag "lecture" and "exercise"
Both variants will generate the same timetables. The only difference is that the constraint must be added a bit different, printing the tables look a bit different, the statistic and activity planning look a bit different.
It is difficult to say which variant is better, because we don't know your exact dataset and needs.

[Liviu Lalescu]

is this correct? Just to make sure: students having lab3 now cannot have ex2 or
lecture at the same time.

Also, in case it matters for how to organise my schema: in our university each
student is fixed to his group and to the subjects he will learn. He doesn't have
an option to go for optional courses (as in most of universities).

It is exactly like this. You don't need advanced students' divisions.

Also, am I supposed to call my subjects: Math.lecture, Math.exercises?
Otherwise, if I just publish the schedule with just the name "Math", how would
students make distinctions between all the forms (lectures, exercises, labs)?

I would prefer "Math" and activity tags "Lecture", "Exercises", and "Labs".

[mimooh]

The concept itself is not vague. It is only vague to underatnd for some users.

Yeah, that's what I meant.

Did you read only the FET internal help or also my manual? ( https://www.timetabling.de/manual/FET-manual.en.html#id_12 )
Please also watch https://www.youtube.com/watch?v=qEuujWuu0oI . You will understand the concept hopefully better than.

I've seen the videos, but I like your docs better. I know how hard it would be to communicate the ideas of my programs. I feel like FET must be a simple thing, but the user must understand things properly. I go back to the FET docs and then go back to producing the rest of the FET XML. I will surely let you know when I succeed with this FET thing

Regards and thanks!
Karol