FAQs.md

@@ -95,4 +95,34 @@ Yes, as always, if you fail a course, you have to repeat the entire one.
 
 ### 9. Where can I get more details about course organisation?
 
-More details about the course content and organisation are provided in the first two lectures, as well as in the TeachCenter description ('General Information') and forum, tutorials and question hours.
+More details about the course content and organisation are provided in the first two lectures, as well as in the TeachCenter description ('General Information') and forum, tutorials and question hours.
\ No newline at end of file
+
+---
+
+### 10. What are the registration requirements for these courses?
+
+TUGOnline directly lists the registration requirements (according to your study programme). If you can register for the course on TUGOnline, you fulfill all the requirements.
+
+---
+
+### 11. My submission works perfectly fine on my local machine, but crashes/doesn't compile/doesn't output anything/doesn't work on the submission system. What can I do?
+
+Please make sure to account for sufficient time **before the deadline** to test your submission on the submission system. 
+
+If something doesn't work as you would expect, you can follow this procedure:
+
+1. Check that you submitted the correct files (and submitted all necessary files) to the correct branch. You have to submit your solution to the `submission` branch of your repository for it to tested on the submission system. Also make sure that you correctly pushed all the necessary files via git.
+2. Check that you didn't add temporary project files (CMake, Visual Studio, etc.).
+3. Check that you didn't modify files that are necessary for the submission system to function correctly. An example would be the included `.gitlab-ci.yml` file.
+4. Check your compile and execute log on <https://assignments.icg.tugraz.at/>. You can find these logs by navigating to your repository and clicking on the `CI/CD -> Pipelines` button in the side bar. There you can find all your submissions and their corresponding test pipelines. Each pipeline has multiple stages, typically starting with a `build` stage and ending with a `test` stage. By clicking the round buttons in the `stage` column of the pipeline overview, you navigate to a more detailed view of that stage. There you can find build and execution logs of your submission, which include errors during compilation or during runtime.
+5. If you're still not sure why your submission is not working, you can take advantage of the fact that you can submit as often as you want. You can use standard debugging techniques (commenting things out, adding debug print messages, etc.) to nail down the issue.
+6. Undefined behavior (such as buffer overflows, memory access errors, divisions by zero, ...) can result in very different outputs depending on the system and machine. Most of these errors will either lead to the submission system sometimes not displaying the correct result or crashing.
+7. Compare/talk to colleagues and attend the tutorials. If you're still unsure on why your solution is not working, the tutors can help to guide you in the correct direction.
+8. Alternatively, feel free to create a post on the TeachCenter forum. All tutors and teachers have access there and you will receive the fastest response to your problems there.
+9. If you suspect that this is an issue with the framework or the submission servers, please notify us by writing an email to <cgcv@icg.tugraz.at>. Please **do not** use this email for general questions about your code, as the TeachCenter forum should be used for that.
+---
+### 12. I don't know how to use git. Is there an alternative method to submit my solution?
+
+You can also submit via the web interface of <https://assignments.icg.tugraz.at/>. On your repository page, you can create/edit/delete branches, add/edit files, and do pretty much everything you need to. We still strongly recommend you to use and learn git, as it is an industry standard tool for collaborative software development and version control, and you only need a very small subset of git for this course.
+
+---