Communication and Expectation

Expectation

This is an interdisciplinary course, which means that two or more topics are integrated as part of the curriculum for the class. The first one is more aligned with the artistic expression part of the course through the design of a virtual theater experience. The second one is more technical and will require the use of various coding and design tools like unity and GitHub to complete the assignments. As I mentioned today in class this course was designed without the requirement of previous coding experience, so it is ok if you have never coded or done any 3D design before. That said, it is expected for everyone in the course to be proactive and achieve a minimum level of knowledge for both the unity/programming part of the course and the artistic expression part of it as well. This will require a minimum of 8.5 hours weekly outside of the class time. in order to cover the learning materials while applying artistic choices. See UCSB Hours per Unit [1].

We are here to help you find the solution to your coding problem, but without your continuous effort it will be difficult for you to progress in this course—the instruction team will not be able to assist every coding issue you will have in this course.   My goal as your instructor for the class is that by the end of this course everyone feels comfortable with the basics and can have the tools to continue exploring these topics on their own if they are interested. To achieve this, a minimum amount of material must be covered throughout the quarter which means that the class will be fast-paced. These goals are achievable with the right level of time commitment. If anyone is concerned about this or would like to discuss any other details before making any final decisions about the class, please let me know and we can discuss it. This way we can also be considered with your fellow students on the waiting list.  

Submission Format

Academic practice requires transparency and reproducibility. Classmates should be able to examine the creative and technical methods used to produce the work. Make sure to include your source code and step-by-step direction in the report. If you used the asset, make sure to include the asset files in your submissions. When uploading your project summation files to the class Google Drive please make sure to include, the main zipped Unity folder, and the scripts you worked on. When making a submission, make a .zip folder including both Asset and ProjectSettings folders, make sure to unzip, test out and run before uploading your work for submission. *If it does not run please follow the instruction [1, 2] But most importantly include a document that shows step by step guide to follow along the process used to develop the game. Again, please include screen-captured step-by-step instructions. Screen-carputer software [1, 2].  For this course, it is okay to borrow code from the internet as long as the source is cited in the report. The wording and report must be fully written by the student and must be original work. Lastly, make sure to include the title of the report on Page Header + your last name and page number on Page Footer on every page. The preferred citation style used in a business report is (IEEE BibTeX). 

Please do not push new contents to submitted repository (shared URL) after the deadline, doing so could considered as a late submissions. If you have to continue working for personal reason, make sure to continue working on cloned the repo. 

• Add assignment repository URL to Assignment Submission Sheets found in your class Drive folder 

• Unity folder .zip file

• Unity Asset .unitypackage file

• IEEE BibTeX for the Asset used .txt file

• Source code (original script file that you worked on) .cs file

• Add package.txt file in the class Drive assignment folder explaining what is being submitted. 

• Instructional Document (PDF)

• 100MB .zip file - Git Large File Storage (LFS), more will be explained in the week 2

Example of citing unity asset in IEEE BibTeX: 

Course Assignments

In addition to weekly course activities, students will be responsible for completing three in-course assignments and one final project for the Fall 2022 semester. Each assignment and final project must be documented in written form (complete with Unity scenes and source code) and submitted on the class Google Drive prior to the class on which they are due. Communicate with the instruction team ahead of time if you have trouble submitting or will need more time to complete the assignments. Please be advised that this is a fast-moving and short ten-week course; therefore, it is important that you divide the labor amongst your group, communicate, work closely with peers and instructor.

• It is your responsibility to check the weekly course schedule regularly, please check once a week.  

• Please check class discord channel announcement once a day.  

• A weekly survey submission is part of attendance, so make sure to fill out the survey right away. 

• Make sure to include your source code and step-by-step direction in the report. 

• Please review both assignment and schedule sections carefully found on the webpage for any changes (As the detail will be added as the course progresses). Note that the adjustment made in the course is to better survey the student profile and learning progress. Making the course more relevant to student's interest and project ideas. 

Communication

Email 

When you have any question or concern email the course TA Pau Roselló Diaz (paurosellodiaz@ucsb.edu). Please be patient and polite, we will do our best to respond to your email within 48 hrs. Pau and I (You-Jin) would love to keep non-hierarchical and supportive course  structure. 

Use of Idea Sketch 

When communicating with us, be prepared. Organize your thoughts, use AR VR terminology [1] when applicable. Please have mock up images/ doodles ready to show when explaining the project to the instruction team. Bring sketch/ drawing or even simple 3D rendering to further assist you—the more detail you bring better we can assist. 

Use of Class Discord Channel

First, please change your nickname for the server to your full name, First and Last (this will not affect your Discord profile in other channels you are already associated with). Do not post anything on the "announcements" as it is reserved for the instruction team. Please use emojis to respond to the announcements—so we know how many students have seen it. Please check the class Discord channel at least once an every other day. Please feel free to use "assignments-questions" to help each other and collaborate between students. "student-only" channel is reserved for students to communicate about anything. Use this link to join the class Discord channel [1, 2]. Please respect the communication protocol, and do not send a direct message to the instructor on Discord. 

Use of Weekly Logs

Your Weekly Logs/research journals should be reflective of your experiences during this course (thoughts, ideas, sketches, notes, reading responses, etc.) and your progress with your team. At the end of this course, this component will stand as extensive documentation of your research process and course assignments, making it the most crucial component of this course for your learning/research development. Describe your weekly progress including Unity Learn, group project, individual tasks and highlight your contribution. It will also serve as a space where you can formulate technical instructional manual. class Google Drive -> Your Name -> Google Docs (week 01). Your Weekly Logs are just as much for you than they are for us. Keeping an organized document throughout the course will primarily benefit you. The only requirements we have are as follows: 

• Keep your logs in a google doc inside the shared student folder on our drive.  

• No less than 250 words per week. 

• Make sure to attach as much as screenshots of what you are working on

• Look through examples found in class Google Drive -> Keanu REEVES (example) 

• Feel free to be as creative with these as you would like!

Weekly Logs Due every Thursday 11:59 PM

© You-Jin Kim

Santa Barbara