**Lecturer: Lucian Busoniu. Lab TAs: Mihalis Maer, Maria Ceapa. Project TA: Zoltan Nagy**

Navigation: [Versiunea romana|Evaluation rules|Schedule|Lectures|Labs|Lab tests|Project|Contact] [Back to Lucian Busoniu's webpage]

The course introduces system identification methods including time-domain and correlation analysis, prediction error methods and instrumental variables techniques. Input signals, online recursive variants, closed-loop identification, and model validation are also discussed. The material is described at an appropriate BSc level, and builds in a self-contained manner the required mathematical background. The course is based on the book *System Identification* by Soderstrom and Stoica.

This year, we will teach everything on-site (lectures, labs, and projects), but we will use online platforms for discussions with students (Microsoft Teams) and to take quizzes (ClassMarker). As a unique ID for each student, we will use use an email address that is associated to a ClassMarker account. Microsoft Teams may be associated with a different, Didatec email address (or you can of course use the Didatec email for everything). Details on how we are using these platforms can be found under the specific type of activity below.

This course is part of the Bachelor program of the Automation Department, UTCluj (3rd year 1st semester). Prerequisites: linear dynamical systems and linear algebra.

Grading:

- 30%=2x15% two lab tests, see their section below for details.
- 10% lab quizzes: a short quiz with two questions, at the start of each lab except the first, from the material relevant to that lab.
- 30% final exam.
- 30% project (15% part 1 + 15% part 2), see below for details.
- 10% lecture quizzes: short quizzes during each lecture, from the material discussed during that particular lecture.
- 0.1 points bonus for each lab between 2 and 10 handed-in during the actual lab class.

Eligibility conditions: Solutions to all labs except the first one; the two lab tests; and solutions to both parts of the project, presented in the interactive sessions, are all required before being admitted to the exam. More details about each component (labs, lab tests, project evaluation) are found at the appropriate places in their separate descriptions below.

Lectures are Wednesdays from 8AM, labs and projects on Mondays and Tuesdays. Please look at the schedule below carefully to determine exactly when you should be in class, and see the overall schedule on http://www.aut.utcluj.ro/ for when your time slots are allocated.

Due to interdependencies between lectures, labs, and project classes; public holidays; and other constraints, the actual schedule is slightly different from the official one. Notably:

- Since we need lecture 2 for lab 2, and labs come before lectures, we postpone lab 2 to week 3.
- We skip the lecture in week 6 but recover this by working on two lectures in week 9.
- 6-7 Jan are public holidays, so no labs or project in that week.
- Some slots are held in backup for lab tests and project presentations that may "spill over" the usual lab and project slots.

The lecture slides are mandatory reading; they will be written down in detail to give a self-contained, complete picture of the topics. They are made available here in time for each lecture.

- Part 1: Introduction to System Identification (PDF).
- Part 2: Mathematical Background: Linear Regression. Probability Theory and Statistics (PDF).

At a random point during each lecture, a short quiz will be given from the material of that lecture, using the ClassMarker platform. A list of email addresses will be collected beforehand and you will be invited to ClassMarker. The quizzes are graded! So, you should pay attention during the lectures. If you answer all the questions in every lecture correctly, you get 1 point in your grade; lower scores scale linearly to between 0 and 1 points in the grade.

In addition to the slides, followers may optionally consult the following books:

- T. Soderstrom and P. Stoica.
*System Identification*. Prentice Hall, 1989. The full text of this book is available at: http://user.it.uu.se/~ts/bookinfo.html. This book forms the basis of the course. - L. Ljung,
*System Identification: Theory for the User*, 2nd ed., Prentice Hall, 1999. An advanced graduate-level textbook.

Labs will be developed using Matlab. PDF descriptions of the labs are given on this website.

Lab solutions are required starting from lab 2. It is not enough to be present at the lab in order to be marked present; a complete, working, and original solution must be developed during the lab, see below for how we check whether the solution is working and its originality. At most two labs in total can be recovered before the exam; hence, accumulating three or more missing labs means you can no longer become eligibile for the exam. At most one copied lab can be recovered at any time during the year. Copying more than one lab automatically means you forfeit the discipline and retake it next year.

Half-group boundaries are strict, for example you cannot access the quiz to the lab unless you are present during the lab slot of your halfgroup.

Each lab except the first starts with a 2-minute quiz containing 2 short questions, which tests you on the lecture material relevant to that particular lab. If you answer everything correctly for all the labs, you get 1 point in your grade; lower scores scale linearly, as for the lecture quizzes. So, you should arrive prepared.

The validation that the lab is complete and working, as well as a first test of originality, is performed during a discussion with the TA. We will ask thorough questions to make sure that you were the source of the code (as opposed to some code generation tool such as ChatGPT). If you fail to answer these questions successfully, the lab may already be declared copied at this step. If you pass this validation step, you are allowed to submit your solution to a Teams assignment that will be created for each lab.

We very much prefer that students validate their lab as working and upload it to Teams during their nominal 2-hour slot. To promote this, for each lab that satisfies this condition, the submitting student gets 0.1 points bonus in their final grade.

The *final* deadline to validate and submit the lab is the Tuesday of the week after the lab, at 11:59PM. After that, the assignment is closed.

Once the assignment closes, the solutions to each lab are run through an automated plagiarism check to defend against copying between students. Each suspicious case is examined by the teachers, and if it becomes clear that the lab is copied, both the source and the destination lab are marked copied.

As pointed out above, we are imposing a "two strikes - you're out" rule. Namely, the first lab copied is only invalidated, and you can recover it at the end. The second lab copied invalidates the full set of solutions, you forfeit the discipline and have to take it next year.

- Lab 1: (Re)Introduction to Matlab. Using the DC motor (PDF) -- an exercises to get re-acquainted with Matlab and at the same time learn how to use the DC motor (see the guide above). For a brief intro to Matlab, have a look at the following document (with thanks to Paula Raica for allowing us to use it) ST_Lab1.pdf. You may also use the automated Matlab tutorial, with thanks to Tassos Natsakis who developed it.
- Lab 2: Linear Regression for Function Approximation (PDF). The data files are: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12, #13, #12, #15, #16.

- 6 points: code for redoing a (part of a) lab between 2 and 5, i.e., linear regression, transient analysis, or correlation analysis.
- 4 points: one-on-one question(s), both on the code and testing the higher-level insight about the methods in the labs.

**Lab test 2:** The same structure as for test 1, except now from labs 6 to 10.

The grade at each lab test is added with a 0.15 weight to the final grade, irrespective of its value.

See the project description (PDF) for the topic, rules, and deadlines. Please read it carefully. A detailed description of the linear regression method needed in the first part of the project can be found in lecture 2 (for now link the link points to the slides from the previous year, it will be updated).

Guidelines for writing a report and developing and giving your presentation are also available. We will not be using reports this year but many of the principles there are also applicable.

Comments, suggestions, questions etc. related to this course or website are welcome; please contact either the lecturer or the TAs via Teams or email.