is the ACM Special Interest Group for Computer Graphics and Interactive Techniques.
is the Association for Computing Machinery.
List of topics ideas:, current topics, photorealistic rendering for master students, thesis topics for talented computer graphics students.
Dear Master students, have you successfully passed or are you currently studying the following courses?
Then we will be happy if you contact Tomáš Iser and we can discuss thesis topics with you concerning photorealistic rendering!
Inverse sandblasting for fun and profit.
After printing an object using a Polyjet 3D printer, postprocessing is applyed to create the final surface finish. Sandblasting and tumbling are common postprocessing techniques. In order to not “eat” into the object geometry during this polishing, the printer can add a padding layer around the object. However, due to the object geometry, the abrasive processes removes material in a non-uniform way.
The goal of this thesis is to use standard erosion simulation techniques to find spatially varying, optimal object wraps, such that, after a certain amount of abrasion, the resulting object exactly matches the specified measurements.
Towards steerable surface reflectance.
The surface finish greatly impacts the appearance of an object. If it is smooth, light is reflected almost mirror-like whereas roughening surfaces lets them appear more glossy and eventually completely matte. Current 3D printing techniques achieve such high resolutions, that it might become possible to influence the surface roughness and thus the directionally dependent reflectance.
Luongo et al. [2019] demonstrated promising results in their paper on a SLA printer . They encoded directional information in the surface by overlaying it with a random noise pattern that was informed by a model of the curing process inside the 3D printer.
We would like to get a similar understanding about our Prusa SL1 printer and want to extend the amount of control one has over the surface reflectance. In particular, we want to know how subsurface structures filled with air could affect the directionality of the reflectance? Can multi-material printing allow for more variety in the effects one can replicate on a single surface together?
Mobile app for object detection in video, discover the objects in museum virtual tour.
Process a video stream on a mobile phone to detect objects in a museum. Identification is possible through a lightweight neural network. The model should offer sufficient accuracy and speed in recognizing different types of exhibits (size, material) in diverse conditions (lighting, location, background, viewing angles). At the same time, it should consider the limitations of the mobile device, particularly the limited computing power, memory, and battery capacity.
Illustration taken from https://viso.ai/wp-content/uploads/2022/06/mediapipe-object_tracking_android_gpu.gif https://i.giphy.com/uULru6cnBO4gM.webp
What clouds are we looking at.
Weather webcams continuously take pictures of the sky and landscape for meteorologists and the general public to get an impression of the current weather situation. They are a great tool to verify the forecast and see the local deviation.
For this project we would like to classify the types of clouds that are visible in the images and what the weather situation currently is. Is it sunny? Are we seeing rain clouds? You will be using machine learning (eg. auto-encoders) and dimensionality reduction techniques (eg. t-SNE, PCA) to find clusters in the images. These groupings mean that similar clouds / weather conditions are depicted in the images. You will look at self-supervised techniques in order to minimize the amount of manual labelling necessary.
We have a large collection (16+ million) of webcam images from the Czech Meteorological Service (CHMI) that covers 98 locations over 18+ months in 5 minute intervals. This dataset can be a valuable asset to the research community, if there is proper annotation and meta-data for each image available. Your thesis will contribute to this list of additional knowledge we have over the images and help researchers to train better models with this data in the future.
In architecture visualization, physically-based rendering allows for the accurate prediction of the irradiance levels in different parts of the building. This helps architects, for example, to maximize the use of natural light in their designs. Current rendering systems, however, do not model the dynamics of the human visual systems when it comes to light-dark-adaptation. This is important in the design of areas with brightness transitions, like entrance areas and hallways.
For example, consider a highway tunnel: To allow for a more graceful brightness-adaptation when entering, tunnel lights are more powerful around the entrance than they are further in. The goal of this thesis is the design and implementation of a physiologically correct camera model for light-dark adaptation.
Can gans learn to generate good textures via differentiable rendering.
Differentiable/inverse rendering can find input parameters such as camera position, object’s shape, or its texture from a target image. Using a simple differential rasteriser, available e.g. in PyTorch3D, the goal is to train an image-based Generative adversarial network (GAN) to produce textures, which (after applying to a known object shape and rendering) produce plausible appearance of the object. The resulting GAN+rasteriser network can be trained on a large dataset of textured 3D models of furniture.
Ultimately, the network should be able to create a texture for a 3D model that does not have a texture nor its mapping to the 3D object’s surface – for this an existing unwrapping tool will be used.
(intended as an implementation+experimental thesis)
Where's the sky.
Task: Build a modular system that takes a big resolution HDR image and semantically segments it. Already existing networks can be modified and used. The number of semantic classes must include but is not limited to sky (clouds possibly), buildings, vegetation. Preferred tools: Python or Matlab
Hack a 360 degree camera.
In Rendering spherical (360°), high dynamic range ( HDR ) images are used as backgrounds and for lighting 3D objects with a realistic light source. For most cases, outdoor captures are used to mimic a realistic sky and sun illumination.
Traditionally, a capture setup for these images consists of a heavy tripod with a panoramic head that can rotate a high-end DSLR around its central point. This gear allows for capturing several pictures in different directions with several exposures that are all taken from one single point. Later in post-processing step, these get stitched to a single panoramic and HDR image. We possess such a setup and use it frequently to capture images of clouds.
Unfortunately all this gear is very heavy and bulky to carry around. We are looking for a more portable solution, that can be setup quickly and delivers not as precise, but reasonable images. For this we bought a state-of-the-art, 360°, pocket camera that is easy to setup and can be controled wirelessly. The factory app does not allow for an easy capture of HDR images though, which is why we started looking for a custom software solution. Initial tests on reverse-engineering the communication protocol showed it is possible to communicate with the camera using a few tricks.
We would like to develop a platform-independent (mobile/web) app that can talk to the camera and capture time lapses as well as exposure-varying sequences. This would allow for the camera to be taken on daily trips and capture environment images wherever you are in the background. This data is supporting machine-learning efforts in our other sky related projects. This project is intended as an individual software project (NPRG045).
Cut the pdf.
Task: Build a modular system that takes a PDF of a scanned journal, extracts pictorial and textual data, performs an analysis of the various data types, and saves the results for later statistical analysis. Preferred tools: Python or Matlab
Create the little world.
Apply an intelligent tilt-sift transform on images to get a realistic picture of “the little world”. Use DL for depth estimation and apply blur filter accordingly. Standalone app or GIMP plugin.
Eye is the window to the disease.
Detect optic disc in retinal images. Use CV methods, compare them with deep learning results.
Do the nets see what we see.
Is there a difference in the visual activation in humans and in deep networks when selecting the category of an object?
Send the professor an e-mail. When you write a professor, be clear that you want a meeting regarding a senior thesis or one-on-one IW project, and briefly describe the topic or idea that you want to work on. Check the faculty listing for email addresses.
*Updated August 1, 2024 | |||
Table Legend: X = Available | N/A = Not Available | |||
X | X | X | |
X | X | X | |
X | N/A | N/A | |
X | X | X | |
N/A | N/A | N/A | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | N/A - at capacity | |
X | X | X | |
X | X | N/A - at capacity | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | N/A - at capacity | |
X | N/A | N/A | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | N/A - at capacity | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
N/A | X | N/A | |
X | X | X | |
X | X | N/A - at capacity | |
X | X | X | |
X | X | X | |
N/A | N/A | N/A | |
X | X | X | |
N/A | N/A | N/A | |
X | X | X | |
X | X | X | |
X | X | X | |
N/A | X | N/A | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | N/A | |
X | X | X | |
X | X | X | |
X | X | X | |
X | X | X |
Available for single-semester IW and senior thesis advising, 2024-2025
Research areas:
Available for Fall 2024 IW advising, only
Not available for IW or thesis advising, 2024-2025
Available for single-semester IW, 2024-2025. No longer available for senior thesis advising.
Note: I am happy to advise any project if there's a sufficient overlap in interest and/or expertise; please reach out via email to chat about project ideas.
Research areas: computational cognitive science, computational social science, machine learning and artificial intelligence
Note: I am open to projects that apply ideas from computer science to understanding aspects of human cognition in a wide range of areas, from decision-making to cultural evolution and everything in between. For example, we have current projects analyzing chess game data and magic tricks, both of which give us clues about how human minds work. Students who have expertise or access to data related to games, magic, strategic sports like fencing, or other quantifiable domains of human behavior feel free to get in touch.
Research Areas:
Available for Fall 2024 single-semester IW advising, only
Advisees typically have taken one or more of COS 226, COS 324, COS 423, COS 424 or COS 445.
Available for Spring 2025 single-semester IW, only
Research Areas: fair machine learning (and AI ethics more broadly), the social impact of algorithmic systems, tech policy
My primary research work is in Theoretical Computer Science.
* Research Interest: Spectral Graph theory, Pseudorandomness, Complexity theory, Coding Theory, Quantum Information Theory, Combinatorics.
The IW projects I am interested in advising can be divided into three categories:
1. Theoretical research
I am open to advise work on research projects in any topic in one of my research areas of interest. A project could also be based on writing a survey given results from a few papers. Students should have a solid background in math (e.g., elementary combinatorics, graph theory, discrete probability, basic algebra/calculus) and theoretical computer science (226 and 240 material, like big-O/Omega/Theta, basic complexity theory, basic fundamental algorithms). Mathematical maturity is a must.
A (non exhaustive) list of topics of projects I'm interested in: * Explicit constructions of better vertex expanders and/or unique neighbor expanders. * Construction deterministic or random high dimensional expanders. * Pseudorandom generators for different problems. * Topics around the quantum PCP conjecture. * Topics around quantum error correcting codes and locally testable codes, including constructions, encoding and decoding algorithms.
2. Theory informed practical implementations of algorithms Very often the great advances in theoretical research are either not tested in practice or not even feasible to be implemented in practice. Thus, I am interested in any project that consists in trying to make theoretical ideas applicable in practice. This includes coming up with new algorithms that trade some theoretical guarantees for feasible implementation yet trying to retain the soul of the original idea; implementing new algorithms in a suitable programming language; and empirically testing practical implementations and comparing them with benchmarks / theoretical expectations. A project in this area doesn't have to be in my main areas of research, any theoretical result could be suitable for such a project.
Some examples of areas of interest: * Streaming algorithms. * Numeric linear algebra. * Property testing. * Parallel / Distributed algorithms. * Online algorithms. 3. Machine learning with a theoretical foundation
I am interested in projects in machine learning that have some mathematical/theoretical, even if most of the project is applied. This includes topics like mathematical optimization, statistical learning, fairness and privacy.
One particular area I have been recently interested in is in the area of rating systems (e.g., Chess elo) and applications of this to experts problems.
Final Note: I am also willing to advise any project with any mathematical/theoretical component, even if it's not the main one; please reach out via email to chat about project ideas.
1. Quantum algorithms and circuits:
2. Information Based Complexity:
3. Topics in Scientific Computation:
Available for Fall 2024 single-semester IW, only
Opportunities outside the department.
We encourage students to look in to doing interdisciplinary computer science research and to work with professors in departments other than computer science. However, every CS independent work project must have a strong computer science element (even if it has other scientific or artistic elements as well.) To do a project with an adviser outside of computer science you must have permission of the department. This can be accomplished by having a second co-adviser within the computer science department or by contacting the independent work supervisor about the project and having he or she sign the independent work proposal form.
Here is a list of professors outside the computer science department who are eager to work with computer science undergraduates.
Center for Information Technology Policy.
Select a Senior Thesis Adviser for the 2020-21 Academic Year.
Potential research topics
Office of Sustainability, Phone:(609)258-7513, Email: cs35 (@princeton.edu)
The Campus as Lab program supports students using the Princeton campus as a living laboratory to solve sustainability challenges. The Office of Sustainability has created a list of campus as lab research questions, filterable by discipline and topic, on its website .
An example from Computer Science could include using TigerEnergy , a platform which provides real-time data on campus energy generation and consumption, to study one of the many energy systems or buildings on campus. Three CS students used TigerEnergy to create a live energy heatmap of campus .
Other potential projects include:
Computing, Operating Systems, Sustainable Computing.
Javascript is disabled in your browser. Please enable it for full functionality and experience.
Seeing, modelling and animating humans.
Realistic human modelling is a challenging task in Computer Vision and Graphics. We investigate new methods for capturing and analyzing human bodies and faces in images and videos as well as new compact models for the representation of facial expressions as well as human bodies and their motion. We combine model-based and image-and video based representations with generative AI models as well as neural rendering.
Read more about current research projects in this field.
We have a long tradition in 3D scene analysis and continuously perform innovative research in 3D capturing as well as 3D reconstruction, ranging from highly detailed stereo as well as multi-view images of static objects and scenes, addressing even complex surface and shape properties, over monocular shape-from-X methods, to analyzing deforming objects in monocular video.
We perform innovative research in the field of video processing and computational video opening up new opportunities for how dynamic scenes can be analyzed and video footage can be represented, edited and seamlessly augmented with new content.
Our research combines computer vision, computer graphics, and machine learning to understand images and video data. In our research, we focus on the combination of deep learning with strong models or physical constraints in order to combine the advantages of model-based and data-driven methods.
Our experience in tracking dynamic scenes and objects as well as photorealistic rendering enables new augmented reality solutions where virtual content is seamlessly blended into real video footage with applications e.g. multi-media, industry or medicine.
We have performed various research projects in the above fields over the years.
Read more about older research projects here.
For more information about diploma theses , projects , and bachelor theses please see the respective pages - this page just lists topics for these projects.
The best way to obtain a topic for a Computer Science Project, a Bachelor Thesis or a Diploma Thesis is to contact the supervisor of one of the topics listed below by email. For other topics, contact the heads of the main research directions best fitting your interest listed in the following.
The Computer Science Projects may also be completed in cooperation with a company. Such external projects have to conform to a number of guidelines .
Stay up-to-date with new topics by subscribing to the RSS-Feed .
PR = Praktikum, BA = Bachelorarbeit, DA = Diplomarbeit, PR/BA/DA = Praktikum, Bachelorarbeit oder Diplomarbeit, der Arbeitsumfang wird entsprechend angepasst.
TU Wien Institute of Visual Computing & Human-Centered Technology Favoritenstr. 9-11 / E193-02 A-1040 Vienna Austria - Europe
Tel. +43-1-58801-193201
How to find us
The following factors make a good scientific work:
back to table of contents
2.1 parts of a student thesis.
It is best to use the templates (Word and LaTeX) provided by the department, especially to automatically generate the title page, declaration of independence, and all directories. The thesis must be written according to the following structure:
The IMRAD ( I ntroduction, M ethods, R esults a nd D iscussion) schema is a common standard. Proposed structuring:
Chapter 1: Introduction Motivate the problem in the application context, restate the task in your own words, and give an overview of the work.
Chapter 2: Related Works Show who has already dealt with the topic or related topics, what solutions have been described, and what the connection is to your own work.
Chapter 3: Fundamentals Introduction of mathematical, technical, algorithmic, or other basic knowledge necessary to understand the work.
Chapter 4ff.: Methodology and Implementation Main part of the work - first describe the concept, then the realization.
Chapter 4ff.+1: Results Objectively present the results and describe how exactly they were obtained. Draw attention to peculiarities.
Chapter 4ff.+2: Discussion Discuss the implemented solution based on the results. Understand and explain peculiarities. Based on this, work out the pros and cons (of the developed method). Under certain circumstances, the chapters "Results" and "Discussion" can be summarized in a single chapter.
Chapter 4ff.+3: Summary Brief summary and evaluation, results/solutions are condensed into a conclusion.
Chapter 4ff.+4: Outlook The outlook shows meaningful possibilities for further processing the material. Chapters "Summary" and "Outlook" can be summarized in a single chapter under certain circumstances.
In Chapter 7↓ (Best Practices), you will learn more about the contents of each chapter.
It is best to use one of the chair templates. You can find these at: tu-dresden.de/ing/informatik/smt/cgv/studium/materialien
Body text in serif font creates good readability. Headings can look nice in sans-serif bold font. Recommended font sizes are:
Emphasis can be achieved through italics , bold , ALL IN CAPITAL LETTERS, small caps, and font family. However, do not use several AT ONCE ! Underlining is prohibited, bold and capital letters should be used sparingly! For source code, a monospace font is recommended (e.g., Courier New). Free variables and free function names should be italicized, whereas characters with fixed meanings should NOT be italicized - these are well-known functions (e.g., sin/cos, lim), constants (e.g., Euler's number e, the constant π , or user-selected constant symbols), and unit symbols (e.g., m/s, kHz). Mathematical variable names never consist of more than one letter! If more characters are needed for precision, they may appear in subscript (also not italicized). Examples of font formatting in formulas:
Italicized text can also be used to indicate (self-introduced) technical terms and foreign words and bold can be used to indicate keywords. Furthermore, italics are used when referring to titles of independent work (monographs, books).
Use quotation marks “” not to emphasize words, but exclusively to quote text passages or when referring to non-independent literature (articles from conference proceedings or journals, essays, book sections).
The work should be printed double-sided . Leave margins for notes. A good layout has an outer and inner margin of 2.5cm each, as well as a top margin of 3cm and a bottom margin of 2cm. The top margin leaves room for a 1cm high header, which bears the title of the current chapter and the current page number on the outside. The page numbers begin on the right (odd) page with the introduction. Chapter beginnings are always on a right (odd) page. If necessary, the preceding (left) page remains blank.
are to be labeled according to the schema Fig.␣<Chapter number>.<Sequential number>:␣<Title> . This refers to captions that are placed below the figure. Find a meaningful title. The figure must be self-explanatory along with its title. Pay attention to high quality, and prefer vector graphics. Also, ensure that each part of the image is large enough and that the captions are large enough for good readability.
are to be labeled according to the scheme Table␣<Chapter number>.<Sequential number>:␣<Title> . This refers to headings that are placed above the table. As with figures, a meaningful title is important.
are to be labeled according to the schema Listing␣<Chapter number>.<Sequential number>:␣<Title>,␣<Filename> . For short code passages, captions can be used; otherwise, use headings .
for annotations or translations. If the footnote refers to a word, the footnote mark immediately follows it. If it refers to a sentence, it is placed immediately after the period. Use footnotes sparingly. Consider how the content can be incorporated into the text in a meaningful way.
All sources, including texts, images, surveys, links, etc., must be cited. The author and the source of the content (books, papers, slides, web pages, etc.) should be identified in the bibliography. The reader must have a complete overview of the sources used and their origin, especially for non-printed media. Permission from the author is not required.
A citation is marked in the text to refer to the respective source. Depending on the field of study or type of work, it varies and appears as a numerical reference (IEEE style) or alphanumeric reference (AMS style, authorship trigraph). The following rules should be used in the final thesis (or just use the CGV template):
In the numerical variant, sources in the bibliography are sorted according to their first appearance in the text. In the alphanumeric variant, they are sorted according to the contents of the bracket. The structure of an entry in the bibliography differs slightly depending on whether it is a conference paper or a book (chapter) (due to the different information to be provided). For example, a conference paper is structured as follows (according to the CGV scheme):
[XYZ99] LastnameInCapitalLetters1, ␣ Firstname1 ␣ ; ␣ Lastname2, ␣ Firstname2 ␣ ; ␣ Lastname3, ␣ Firstname3: Title of the Paper. ␣ In: ␣ Proceedings of the italicized conference on something Vol. X(Y), ␣ Location, ␣ Year, ␣ pp. <PageX-PageY>
When citing sources from the web, always include the URL/link and the date of retrieval. If possible, archive a copy of the internet source. Surveys/interviews are also sources. In this case the following information should be recorded:
[Mei15] ␣ Lastname1, ␣ Firstname1 (Interviewee) ␣ ; ␣ Lastname2, ␣ Firstname2 ␣ (Interviewer): ␣ Title of the Interview. ␣ Telephone/Personal/Written Interview/Conversation/Survey. ␣ Location, ␣ Date, ␣ Time
Exact (direct) quotation Useful for definitions and statements that could not be described more accurately. Placed in quotation marks if it is not longer than 4 lines. Otherwise, the entire quote block is indented (without quotation marks). The source is placed immediately after the quote in the text (Harvard method). Exact quotes must be honestly and accurately reproduced, without any rewording or distortions of the meaning. Text highlights or errors in the original text must also be reproduced (these can be marked with [sic] - Latin for "thus" or "really so"). Double quotation marks in the quote are replaced with single ones. Omissions are indicated by [...] (make sure that this does not distort the meaning of the original). Adaptations to the original, e.g. grammatical phrasing, should be written directly in square brackets at the relevant point - and also if words are added or highlights are made (write a clear comment in the square brackets, e.g. [emphasis added by the author]). Exact quotes should be used sparingly!
Paraphrased (indirect) quotation Here, the content of sentences or paragraphs from the original literature is reproduced in the same meaning as in the original text. The strict rules of exact quotation do not apply, but thoughts may not be altered, omitted, or added. In the sentence/paragraph that encompasses the content of the external source, there must be a "according to," "as per," etc. The citation bracket is placed before the period if the paraphrased quote only goes over one sentence. If the paraphrased quote is several sentences long, the citation bracket is placed after the period of the last sentence of the quote.
Figure citation Figures from external sources must be reproduced unchanged or the changes must be clearly indicated. The source reference belongs at the end of the figure caption (in square brackets). If a foreign illustration was used as a template for your own illustration, it also requires an indication, e.g. "according to [XY01, Fig. X.Y2]."
"Second-hand" quotes are those in which a source is cited, whose content represents a quote from the actual subject matter. Such quotes should be avoided! An exception is the unavailability of the original source, which is a rare case. A "second-hand" quote must be marked with the note "cited in" e.g. "[MXY+01] cited in [XY01]" (in this case, [MXY+01] would be the original source and [XY01] the cited source). Both works must be listed in the bibliography.
Good style is to mention the authors of an external source by name - if there are more than two authors, use the form "SurnameOfFirstAuthor et al. " - however, it is also possible to use the citation bracket directly for this purpose. Examples:
Direct quote:
okay : In the study by [MYZ+01], it is described that these are " [...] crucial factors."
better : Meier et al. describe in their study that these are " [...] crucial factors." [MXY+01]
Indirect quote:
okay : According to [MS01], there are various crucial factors.
better : According to Meier and Schmidt, there are various crucial factors [MS01].
not so good : There are various crucial factors for this (see [MS01]).
Valuable sources should be used, such as papers from well-known conferences with review systems or those that have been frequently cited. Printed sources are generally more credible and should be preferred over web sources such as forums, tutorials, or Wikipedia. Wikipedia can be a first point of reference, but it is scientifically controversial - it's better to search for "proper" literature from there. General problems include:
The strategy is to:
These resources (STARs, old works, buzzwords, names of major conferences) are the basis for further research. Where should one look?
The SLUB has a subscription to many online portals, so you can download listed papers or books for free. However, this can only be done from the TUD IP address range (Uninetz). If you want to access it from home, you can use OpenVPN .
Finding new works through older ones search for the older publication. Then show the works that cite the older work - this option is usually called "Referenced by" / "Cited by". Then research the displayed (new) works.
Finding new works through buzzwords enter buzzwords in the search engine. Sort by publication date and number of citations. Scan the first hits (possibly new buzzwords will emerge). Possibly search for research groups that are known in the specific field and search their publication directories.
Finding new works through conferences after finding relevant research areas and keywords, you can search for major conferences in these fields. Look at the lists of publications and then research them in more detail.
Finding new works through well known authors search for publication lists of authors who are frequently mentioned in the relevant field or whose names frequently appear in the bibliography. Note the order of authorship in the header of a paper. The first-named author is the author (of the largest part) of the work. The far right typically indicates the head of the department/institute/chair as the supervisor of the work.
Begin with the Abstract and Results/Discussion section to quickly access the essential information. Ask the following questions about the source being examined:
Don't panic if you don't understand everything immediately: Scientific papers usually contain highly condensed information. Typically, they need to be read multiple times to be fully understood.
SQ3R method: survey, question, read, repeat, review
How do you know if the found source is useful? Even without specialized knowledge, you should pay attention to the following characteristics:
Always use scientific language - never use everyday language!
Use technical terms, but not to obscure content. The reader must be able to understand them. If unsure, create a glossary. If there is a technical term for something, use it instead of a synonym.
Avoid standard phrases such as e.g. "as can be easily seen...". Don't use relativisations ("many", "often", "mostly"), exaggerations ("enormous", "incredible"), filler words ("indeed", "well"), reassurance words ("somewhat", "somehow", "probably"), argument replacement words ("of course", "naturally"), or personal opinions. Your own statements are not prohibited, but must be critically reflected upon and justified. Stay humble in your explanations and avoid arrogant formulations (bad example: "The foundation is trivially provided by the well-known theories of tensor arithmetic" ). Avoid formulations with "one" or "I".
Don't write artificially complicated, but as if you were orally explaining a scientific fact to a professor. Write concise, clear sentences that exclude ambiguities and are content-wise informative. Terms must be defined clearly and used in a consistent manner. Also strive for a consistent level of language. Stay logical and never lose the thread. Stay focused on the problem. Write for the reader! Guidelines for comprehensibility:
Bad : It is a well-known problem in computer graphics that this interface limits the possibilities, which is why some data, such as textures, are not held in conventional main memory but are transferred to the graphics card and stored there in graphics memory.
Better : It is a well-known problem in computer graphics that this interface limits the possibilities. Therefore, it is common to store data such as textures in graphics memory instead of conventional main memory. This way, they only have to be transferred to the graphics card once.
Use subordinate clauses sparingly - avoid nested or unbroken sentences! Pay attention to clear role distribution: main information in the main clause, subordinate information in the subordinate clause. Eliminate subordinate clauses without (relevant) content. Avoid chains of genitives. Use verbs instead of nouns or auxiliary verb constructions (use "depends on" instead of "there is a dependency" or "is dependent on"). Whenever there is a choice between a verb and something else, choose the verb! Do not use too many prepositional phrases, meaning not more than one preposition ("in, under, over, between, in front of, after, against...") per sentence. Write in a positive sense instead of a negative sense - do not use double negations and write what is and not what is not. Also, avoid using too many passive formulations, but write in an active style.
Use abbreviations sparingly and always use them unambiguously. Explain them at their first occurrence and create a list of abbreviations. Commonly known abbreviations (according to Oxford English Dictionary, Chicago Manual of Style, etc.) do not need to be included in the list. Do not rely on the reader to remember all abbreviations immediately: if you use formulas, constants, or abbreviations again many pages after their first introduction, explain them again with a brief repetition. For example, write "Here, the value α , which is the rotation angle , is used again to..." even though you introduced the variable α three chapters ago.
Avoid bullet point lists and write continuous text instead. Avoid frequent use of forward or backward references (e.g., "As will be seen in chapter X..." or "As shown in chapter Y...").
Use figures, tables, and diagrams to make complex textual statements more understandable, but avoid figures of trivial things. All figures or tables must be self-explanatory (axis labels, legends, color meanings, units, etc.). The use of a figure in no way makes a textual description obsolete: a) the body text must also be understandable without the figure and b) the figure must not replace the running text. Do not place essential new information solely in the figure (Negative example: The text describes that the effects shown in figure XY occur for these or those reasons. However, the effects themselves are only mentioned in the caption). All figures, tables, and diagrams must be referenced in the text.
The lower numbers ("zero" to "twelve") are normally spelled out in text unless there is a particular emphasis on the numerical size. Units are generally abbreviated without a period (kg, km, h, min...). A narrow non-breaking space is placed between the value and the unit symbol (do not break the line here). Avoid writing unrelated numbers together (Negative example: "256 64-bit registers...").
A consistent style should be used, and a uniform naming convention for variables, function names, etc. should be established. Do not use overloaded symbolism, but still strive for accuracy. Avoid using formulas directly in running text as much as possible, as they disrupt the reading flow and can sometimes sabotage the text layout; instead, use displayed formula environments. For example:
The Pythagorean theorem is a fundamental theorem of (Euclidean) geometry and states that:
a 2 + b 2 = c 2
The equation holds for any right triangle, where a and b are its catheti, and c is its hypotenuse.
Do not unnecessarily include complicated and lengthy derivations in the main text. Reduce them to the essential points (and provide additional details in the appendix if needed).
Should never be included in its entirety in the main text! If necessary, only selected portions should be included due to special circumstances. Instead, explain the developed procedures using structure and flow diagrams or with pseudocode.
In the following, you will find tips for the chapters presented according to the IMRAD ( I ntroduction, M ethods, R esults a nd D iscussion) scheme.
At the very beginning of the written work, the introduction should provide a concise motivation for the task and elegantly introduce the topic. Here, the problem is presented in the context of an application, and the content of the work is briefly previewed. What problem was solved, why is it relevant? What is the approach? What was thematically limited or excluded? It is important to highlight your own contribution in a few concise sentences. (The conclusion should refer back to these contributions at the end to give the work a narrative bracket.) The introduction ends with an overview of the work — here, the contents of the individual chapters are briefly described (avoid trivial statements such as "In the results chapter 7, the results will be presented"). Hint : Avoid standard intros like "XY is an important field of application in computer graphics" or "XY is indispensable in computer graphics."
It should be shown who has already dealt with the topic or similar related topics, what solution approaches have been described and what the connection of the respective work to one's own is. Keep the " 4 Questions " in mind as a mnemonic: What problem was tackled? How was the problem solved? What did it bring? How does it relate to your own work? In this chapter, it is particularly difficult to create a red thread and prevent the text from becoming a list of papers. Strategies that can be combined are available: chronological or aspect-oriented. In the chronological listing, related works are described in chronological order, giving a historical overview of the solution approaches to the problem. Typically, the first source in time is described in more detail, as well as the sources that follow more closely in time. Finally, the current state should be examined in more detail. The second strategy, aspect-oriented citation, involves dividing the papers into aspects of one's own problem. For example, if the topic is volume rendering with global illumination, papers on volume rendering in general should be presented first, then sources on advanced methods, and finally papers on the integration of global illumination, possibly even in separate sections.
Mathematical, technical, algorithmic, and other knowledge should be explained here, but only as much as is needed to understand the work. The author's own level of knowledge before starting the work can be considered as prior knowledge. More advanced basic knowledge or detailed mathematical derivations can be moved to the appendix. The work is not a textbook. Explanations of the technical terms used may be given here (or at the beginning of the methodology chapter).
Here, the author's own work is described conceptually, including problem analysis and solution search/finding. At this point, a theoretical examination of the material should take place — do not explain using concrete APIs or source code (pseudocode, however, is allowed). Only after that comes the description of the implementation — in most cases, the implementation as software. Pay attention to a clear and problem-oriented selection of code examples or (partial) class diagrams. Detailed and comprehensive presentations should be moved to the appendix if necessary.
Here, an objective presentation of the results is made. A division into quantitative evaluation (generation of measurement data) and qualitative evaluation (surveys/expert feedback/description of peculiarities) is useful. For each evaluated issue, the result (e.g., as a figure or table) should be shown first, then described, and only then interpreted. Evaluation should not yet take place.
Only in the discussion section are the results to be critically questioned and assessed. Based on this, the pros and cons (of the developed method) are worked out.
The work is briefly summarized and evaluated, the results/solutions are condensed in a conclusion (making a connection to the problem statements raised in the introduction). An assessment of the general usefulness of the developed methods can be given. Hint : End on a positive note! In the conclusion, show the "good" things first, then the "bad" ones. For the latter, note that they are solvable and that the developed methods are nevertheless promising.
The outlook presents sensible extensions of the developed methods or possibilities for further research. Here, current weaknesses should be explained as opportunities for new concepts.
At the beginning of a main chapter, an overview of the following subchapters can be given. At the end of a main chapter, its content can be summarized and linked to the next main chapter. Anything that could hinder the reading flow (such as extensive tables, figures, mathematical derivations, or source code) should be moved to the appendix. Only really important snippets of source code should be included in the main part. It is better to avoid it and explain the underlying concepts/algorithms.
Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | ||
Rough chapter structure, outline | X | ||||||||||||
Research (read, structure, take note of relevant information) | X | X | X | X | |||||||||
Prototype implementation | X | X | X | X | X | X | X | X | |||||
Rough draft | X | X | X | X | |||||||||
Revision, correction, final draft | X | X | X | ||||||||||
Evaluation, creating graphics/tables, etc. | X | X | |||||||||||
Proof-reading | X | ||||||||||||
Printing, binding, submitting | X |
Figure 1 Schedule for a Bachelor's Thesis..
Create a schedule and stick to it (for example, as shown in Figure 1). Also plan buffer time for unforeseeable events and don't let holidays, such as Christmas and New Year's, or exam periods catch you off guard. The work should be evenly distributed throughout the week. A day off from work is important! Make daily to-do lists and plan enough breaks (more than 5 hours of concentrated work per day is hardly possible). Especially plan the written work in small manageable steps and in the evening try to complete one item from the list for the following day.
Start work at a set time every day, whether you feel like it or not! Don't forget the breaks (recommended are 15 minutes of break after 45 minutes of work).
Consider your biorhythm and don't schedule important tasks during times when you are in a "tired" phase (instead, do simple tasks: organize literature, take care of the household or relax...). Remember to engage in daily physical activity — it also promotes mental performance.
Especially in Bachelor's theses, you have a very limited amount of time for implementation. Therefore, focus on the essential core of your implementation. You don't need to reinvent the wheel, instead use existing software components and frameworks (e.g. for event handling, I/O operations, etc.). Your advisor can surely give you good hints, so that you don't have to develop your software from scratch. Discuss explicitly with your advisor the scope of functionality that your developed components should provide, and tackle these tasks first. If you realize during the course of your work that you still have time for further functionality, this will be welcome and credited to you as a bonus.
When implementing, always keep the KISS principle ( "Keep it simple and stupid" or "Keep it small and simple") in mind. Try to find the simplest implementation for the given problem. In general, a mature software product is not expected, a functional prototype is completely sufficient. However, don't skimp on comments in the source code and adequate documentation. Good program structure and software design are also essential. This helps everyone who wants to reuse your software later — for example, for follow-up theses, in teaching, etc. Perhaps you yourself may want to reuse your own software later and will be pleased to find that all functionalities are well-structured and explained.
Many students invest too much time in the implementation. Reasons for this are sometimes "perfectionist thoughts" or the desire to include even more program features in the software. Unfortunately, there is also the problem that some prefer to engage in intensive implementation work to avoid the written work — possibly because they are not sure how to "get started". Most likely, they simply lack experience in planning and implementing such a large project.
The phenomenon of procrastination is not unknown and is also referred to as "student syndrome" among other things. If you yourself are plagued by such thoughts or feel unable or only idle to plan your activities, contact your supervisor in good time and develop a concept for work distribution together. Be aware: you are certainly not the first person to experience writer's block, and help is available!
11.1 the two types.
Intermediate presentation In this presentation, students should particularly show their current progress and receive feedback from the audience. Suggestions may arise that can improve the implementation of the task. The presentation should include an introduction to the topic and the presentation of related work to give the audience an overview of the topic. Then, the chosen approach should be justified, implementations shown, and current results presented. A slide showing a list of completed and uncompleted parts of the task should not be missing. For the unfinished tasks, a realistic estimation should be made with the help of a timetable of whether and how they can be completed on time.
Defense It is not just a summary of the contents produced. Due to the limited speaking time, students should demonstrate that they are able to select important content and leave out unimportant content (or only mention it on the sidelines). Above all, their own contributions should be emphasized. Try to present your knowledge in a way that is as understandable as possible. Unlike you, the listeners do not know every detail of the work and do not want to be informed about every little problem that occurred during the processing time. Start with a good motivation and introduce the task. Be creative and catch the interest of your listeners! This also includes explicitly listing the challenges (i.e., why is your problem a problem) once again. This can be done through a single slide entitled "Challenges." This is followed by a brief outline to provide a roadmap for the presentation. Then, related work and technical foundations should be presented first. These should be kept as brief as possible. A defense is not a lecture! In addition, many things have already been discussed in the intermediate presentation. The core of the work, their own achievements, should occupy most of the presentation time. For particularly extensive work, it may sometimes be necessary to discuss only one part in detail and present the remaining parts in an overview. Always keep the thread and consider carefully what knowledge the listener needs when to follow the presentation, thus avoiding duplicate explanations. Depending on the nature of the work, it can be helpful to start with an overall view (big picture) before explaining finer structures. This gives the listener a guide. Usually, results from measurements or surveys are presented and discussed at the end. The presentation ends with a brief conclusion in which they can emphasize their own achievement again and refer to the task statement/introduction. Here, you can tie things together and show the "Challenges" slide once again. This time, in addition to each sub-problem, briefly summarize your presented solution(s). This is followed by a demonstration of the developed application and the obligatory question and answer session.
Imagine the question and answer session as an opportunity to present more in-depth knowledge. Some questions may be directed towards you as an "expert" and may be quite detailed, while others may be simpler in nature and serve as an indication that parts of your presentation were not understood. React calmly and professionally in the latter case. Under no circumstances should you respond rudely or arrogantly — difficulties in understanding often come from the structure of the presentation (especially if many details are discussed but an overview is lacking). Do not view expert questions as a personal attack and try to answer as objectively as possible. This is not always easy, as you have spent a long time working on the task and may have become very attached to it. Try to approach the situation from a distance and do not justify your actions, especially if your approach is being questioned. Instead, allow for alternative solutions and provide a comparative assessment of your own approach.
Time Limit The given time limit is strict and must be strictly adhered to. During your presentation, the last 5 minutes of presentation time will be discreetly displayed to you. If you are about to exceed the time limit, you will be informed verbally. At this point, you should definitely wrap up the presentation, otherwise deductions in the evaluation may occur.
Clothes Dress appropriately for the presentations. However, you don't need to wear a suit. For defending a thesis or dissertation, a dark pair of long pants and a shirt or a plain sweater is sufficient. T-shirts with prints or casual pants can make you appear less credible as a presenter.
Performance Be as relaxed and confident as possible. Try not to appear too stiff (but also not too hyper). Use speech pace and accentuation to guide the presentation and direct the listener's attention.
Practice Practice your presentation beforehand — for example, in front of a mirror or with good friends. This way, you can already get some initial feedback on its comprehensibility. You will also learn to assess whether the presentation fits within the time limit. Practicing the presentation is also a great way to train a relaxed attitude and speaking style.
Slides Don't write everything you say on the slides. There is a great risk that it will appear as if you are simply reading off the slides. Instead, create good illustrations and diagrams. Slides support the presentation in this way much more effectively, as concepts are often more understandable and tangible when presented graphically. Avoid unnecessary text in your presentation.
Backup Slides If you had to remove detailed information from the presentation slides due to time constraints, don't hesitate to collect them as an appendix. In the Q&A session, the extra slides can help with your explanations and also show that you have a deep understanding of the subject matter.
References in Slides Adopted illustrations and descriptions of related work must be correctly marked as citations, e.g. with square brackets. Use the same abbreviations as in your written work. Create a slide with the references used in the presentation for the appendix, but do not show this slide during the presentation.
Intermediate Questions Generally, be open to spontaneous questions, but don't waste valuable speaking time. Try to return to the presentation as quickly as possible and refer to the Q&A session for questions that would take too long to answer.
12 Thesis Evaluation Criteria
The Chair of Computer Graphics and Visualization pays attention to the following points in their assessments for final theses:
Note: The examples for formatting formulas may be difficult to read on your browser due to the TU Dresden corporate design. We apologise for this and recommend the PDF version (German only).
COMMENTS
1000 Computer Science Thesis Topics and Ideas. Embarking on a thesis in computer science opens up a world of possibilities and challenges. This section offers a well-organized and extensive list of 1000 computer science thesis topics, designed to illuminate diverse pathways for academic inquiry and innovation.
Choosing a computer science research topic for a thesis or dissertation is an important step for students to complete their degree. Research topics provided in this article will help students better understand theoretical ideas and provide them with hands-on experience applying those ideas to create original solutions.
The problem now is that I don't really know what would be a realistic undergraduate computer graphics topic. My thesis advisor, who specializes in geometry (the closest thing to computer graphics- any other professor would be less helpful), suggested that I work on trajectory planning for spray painting robots and did not go into details.
At the same time, standalone headsets pose different technical constrains on computer graphics. The thesis is about exploring the image processing options available for tweaking the passthrough image and experimenting with different visual effects.
This research paper provides a comprehensive analysis of computer graphics, focusing primarily on its advancements and extensive range of applications. Computer graphics have profoundly ...
Department of Computer Graphics Technology Degree Theses " The Department of Computer Graphics Technology (CGT) offers the Master of Science degree with a thesis option. Students may choose courses that deal with virtual and augmented reality, product lifecycle management, and interactive media research." Below are some degree theses on the aforementioned subjects and topics.
Improving deep learning methods. Can we use ideas from the computer graphics toolbox (structure models and data representations) in order to improve the learning efficiency of deep neural networks? This would be an advanced master thesis topic for students who are a bit theoretically inclined (not afraid of a bit of math).
Material and geometric nonlinear analysis of local planar behavior in steel frames using interactive computer graphics. Master's thesis, Cornell University, 1985.
We permanently offer proposals for bachelor and master thesis projects in all areas across our research activities (see our publication page) and related subjects which cover most topics in Computer Graphics.
The master/diploma thesis requires independent research effort to elaborate some state-of-the-art topic. The following is just a small excerpt from a variety of topics related to realtime rendering, scientific visualization, visual effects, visual computing, and 3D printing.
Computer Science Theses and Dissertations This collection contains theses and dissertations from the Department of Computer Science, collected from the Scholarship@Western Electronic Thesis and Dissertation Repository
A meaty list of research topics in computer science, including algorithms, AI, networking, database systems, UX, and information security.
Dissertation Abstracts in Computer Graphics This directory contains the ASCII text files for all of the Computer Graphics Thesis and Dissertation Abstracts Compendiums published in *Computer Graphics*. Each of the compendium files are labeled ThesesXX where XX is the year in which that compendium was published (which bears little relationship to when the individual thesis or dissertations were ...
The problem now is that I don't really know what would be a realistic undergraduate computer graphics topic. My thesis advisor, who specializes in geometry (the closest thing to computer graphics- any other professor would be less helpful), suggested that I work on trajectory planning for spray painting robots and did not go into details.
Thesis topics for talented computer graphics students. Contact: Tomáš Iser. Dear Master students, have you successfully passed or are you currently studying the following courses? NPGR010 - Advanced 3D Graphics for Movies and Games. NPFL138 - Deep Learning.
Bachelor degree thesis topics Hi! I would like ask for your help! I study Computer Science in a hungarian university. I would like to finish my degree in the summer to do this I have to write a thesis. I need some suggestions for the topic of my thesis. I know that I want to write something in the topic of Computer Graphics.
List of dissertations / theses on the topic 'Computer graphics ; computer vision ; animation'. Scholarly publications with full text pdf download. Related research topic ideas.
Available for single-semester IW and senior thesis advising, 2024-2025. Research Areas: computational complexity, algorithms, applied probability, computability over the real numbers, game theory and mechanism design, information theory. Independent Research Topics: Topics in computational and communication complexity.
Our research combines computer vision, computer graphics, and machine learning to understand images and video data. In our research, we focus on the combination of deep learning with strong models or physical constraints in order to combine the advantages of model-based and data-driven methods.
For more information about diploma theses, projects, and bachelor theses please see the respective pages - this page just lists topics for these projects. The best way to obtain a topic for a Computer Science Project, a Bachelor Thesis or a Diploma Thesis is to contact the supervisor of one of the topics listed below by email.
Hint: Avoid standard intros like "XY is an important field of application in computer graphics" or "XY is indispensable in computer graphics." Related work It should be shown who has already dealt with the topic or similar related topics, what solution approaches have been described and what the connection of the respective work to one's own is.