Bei dieser Namensähnlichkeit, muss man fast so ein Banner machen :)

TU Wien:Deep Learning for Visual Computing VU (Hermosilla Casajus)

Aus VoWi
Zur Navigation springen Zur Suche springen
Ähnlich benannte LVAs (Materialien):

Daten[Bearbeiten | Quelltext bearbeiten]

Vortragende Pedro Hermosilla CasajusMartin KampelLisa Magdalena Weijler
ECTS 3,0
Letzte Abhaltung 2024S
Sprache English
Mattermost deep-learning-for-visual-computingRegisterMattermost-Infos
Links tiss:183663, eLearning, Homepage
Zuordnungen
Masterstudium Data Science Modul MLS/EX - Machine Learning and Statistics - Extension (Gebundenes Wahlfach)
Masterstudium Business Informatics Modul DA/EXT - Data Analytics Extension (Gebundenes Wahlfach)
Masterstudium Visual Computing Modul AI for Visual Computing (Gebundenes Wahlfach)


Inhalt[Bearbeiten | Quelltext bearbeiten]

noch offen, bitte nicht von TISS/u:find oder Homepage kopieren, sondern aus Studierendensicht beschreiben.

Ablauf[Bearbeiten | Quelltext bearbeiten]

SS2024: Lecture only started a few weeks into the semester. There were 2 assignments where you had ca. a month each. Exam was relatively early in June

Benötigte/Empfehlenswerte Vorkenntnisse[Bearbeiten | Quelltext bearbeiten]

Knowledge in machine learning/AI in general is recommended but not required. TISS says that you need Machine Learning is Visual Computing, but that is not the case IMHO

Vortrag[Bearbeiten | Quelltext bearbeiten]

SS24: The lecture itself was good to follow for the most part. The slides are okay, but in some cases, they are hard to understand without the lecture. Questions are normally answered in a timely manner.

Übungen[Bearbeiten | Quelltext bearbeiten]

SS24:

Some of the worst and unclear exercise assignments I have ever seen. There were random code snippets to fill in, but there was no clear explanation of the existing package structure, what classes we have and how they should be used. Function documentation was bad, parameters were unclear and not explained anywhere. There was just no logical thread to follow. Information was rather randomly spread out across the assignment document, the (3rd party) dataset documentation or the source code, but often not in the place where you would expect it. Most of the time it feels like the assignment wants you to implement the architecture/classes in a certain way, but it gives you no pointers on how to do that. There are some function stubs with TODOs and a rough explanation on what the function should do and some (verbal) limitations on data types and stuff, but that's mostly not very helpful in pointing you in the right direction. Having at least some data types/fields pre-defined would be tremendously less frustrating for finding the clearly intended solution. The assignment document itself also doesn't provide any guidance or overview on what it's about. There is nothing to give you a hint about what you're actually going to be doing other than "becoming familiar with pytorch usage". "Read the code and make sure to understand what the individual classes and methods are doing" is not very helpful when we have to write half the classes and methods ourselves, and the documentation does not tell you what the class should be doing, but rather just gives some vague hints on how to implement it. There is no high-level overview, and the supposed "good starting point" ("train.py" file) is a file where every second line is incomplete and has to be filled in. So in other words, it's not a good starting point AT ALL. You basically have to read through the entire assignment first to try and piece together what it's even about.

There was A LOT of boilerplate code to implement (file loading/writing, datatype conversion to the required format, field initialization, __init__ methods, etc.) which has basically zero learning effect for the topic at hand. And little to no provided verification/test code that you can run to make sure that what you implemented is behaving correctly. Comparing this with the recommender systems lecture in the same semester, which had a similar style of fill-in-code assignments, but where you had the expected output for verifying the correctness of your code at basically every corner of the jupyter notebook, the difference is night and day. And this isn't really about difficulty either, it just makes the assignment frustrating to solve and vague, because you have no idea whether you're on the right track, or if your basic data structure/format is completely wrong, since there is clearly an intended solution, but nothing to make sure you don't veer off the correct path.

In terms of time investment, the course suggests 34h for all 3 assignments. This is hopelessly, ridiculously out of touch with reality. You will probably use most of this time on the first assignment alone. I ended up dropping the course during the first exercise, because it just wasn't worth the time that I would have to put into it.


SS24 different opinion:

The temporal expenditure was about 5-10h per assignemnt. At the first look it was confusing as so much code was already provided, but in the end the in code comments where clear on what to implement and where to do so. Much of the tasks can be done using ChatGPT, the learning effect will stagnate accordingly.

Prüfung, Benotung[Bearbeiten | Quelltext bearbeiten]

SS24: The exam consisted of three parts: True/False questions, MC questions, and open questions. There were quite many T/F questions (like 30 or so) and also many MC questions (like 10 or so). There were only 3 open questions. IMHO they asked really into detail for some of technologies and not really asked about general understanding of the material. p.s. If you use the question catalog from the other vowi page you are at least prepared for the open questions

Dauer der Zeugnisausstellung[Bearbeiten | Quelltext bearbeiten]

noch offen

Zeitaufwand[Bearbeiten | Quelltext bearbeiten]

noch offen

Unterlagen[Bearbeiten | Quelltext bearbeiten]

noch offen

Tipps[Bearbeiten | Quelltext bearbeiten]

noch offen

Highlights / Lob[Bearbeiten | Quelltext bearbeiten]

noch offen

Verbesserungsvorschläge / Kritik[Bearbeiten | Quelltext bearbeiten]

noch offen


Materialien

Diese Seite hat noch keine Anhänge, du kannst aber neue hinzufügen.