Grading

A+: The student is awarded an A+ when the projects not only fulfill the requirements, but also delivered a great theater experience utilizing the full physical space, artful placement of digital contents, crafty execution, and detailed documentation.

A: The student is awarded an A when the projects fulfill all the requirements. The project delivered a good theater experience mirroring the concept accurately.

B+: The student is awarded a B+ when the projects fulfill all the requirements but are short in delivering the initial art concept. The project fulfills the requirements, but a student must allocate additional measures to demonstrate art concept.

B and below: The student is awarded a B when the projects fulfill contain all the components but are short in execution/ code does not execute properly. Depending on the degree of completion and effort, student can receive a grade ranging from B to D-.

D- and below: The student who misses 3 classes or fails to submit more than 2 assignments may receive these grades.

Students are joining this course with varying amounts of experience; grades will not be evaluated on purely technical success or art style adaptation. The grade estimates start from 0 and students must earn for each letter grade through assignments and grading criteria and not deducted from 100.  If you are prepared for sessions and actively participating, you will succeed in the course. UCSB Grading System can be found Here.

Teamwork Expectation

• Communication Etiquette: Please be considerate during the team discussions. Let others speak and let them finish. Our discussions may touch on sensitive topics such as human cloning, cyborg morals, mind uploading, violence, race, gender, and politics in Mixed Reality domain. To encourage productive and safe discussions around these issues, it is essential that everyone feels welcome to participate and to give opposing views. Learn to share ideas without targeting individuals. Avoid resorting to stereotypes. Any hateful comments will not be tolerated in my class.

• Team Development: Students will co-develop executable AR applications (APPX) for HoloLens 2. While considerable effort will go to designing virtual stage, and digital special choreographing, students must produce working prototypes, test functionality. This extensive process will require close teamwork.

• Team Attendance: Missing a class where team activity is scheduled will greatly hold back team schedule and workflow for other members. As mentioned in the expectation page, attendance at all lectures and sections is required unless you provide documentation of an illness or emergency and notify your TA of your absence/lateness ahead of time. Proper notification will prevent a negative impact on your team project development timeline. If you miss a class, it is your responsibility to catch up on the work and plan catchup with team members.

Teamwork Grading

The team projects are weighed differently than the personal grade and each student will receive an individually estimated grade. Each student will submit a Pear-Review survey conducted weekly rating team performance by sector and this will be used to estimate individual's contribution in the team. The instructional team will intervene to better assist team dynamics using this information.

Extra Credit 

 The instruction team cannot help each student, scanning through their code line by line and trouble shoot. We will be able to direct each student to the right resource and literature to overcome the technical difficulty. That being said, in this course students are expected to proactively seek answers on their own utilizing resources such as Unity Learn, online forums [1, 2] and Discord channels: #student-help or #assignment-question.

We implemented a support system that benefits both learners and tutors! A student who helps out other students will receive extra credit for their teamwork participation which is one of the biggest portions of the grades in this class. Here is how it works:

• Tier 1: Peer helping; helping classmates with a technical problem. 

• Tier 2: Share technical instruction PDF that many students are struggling with (must upload to the class resources folder found in Class Drive). 

• Tier 3: Share technical instruction PDF and give short workshop in the class. 

The student who received the help must keep the record by posting it on the Discord #tutor-record channel right after getting help, so that the student who helped can receive the credit. Please submit the student tutor activity through the Discord #tutor-record channel by posting using the following format: 

[9/30/2022] You-Jin Kim helped out Alejandro Aponte on scene manager script that does XYZ (20 minutes) 

The instruction team will be monitoring both discord #tutor-record channel, updating student progress and grade weekly. 

Peer Helping Etiquette

The collaboration will be crucial to your success in this course. As such, each component listed below will account for teamwork evaluation.  You are encouraged to work with other students on your assignments, and to help other students, provided that you comply with the following conditions: 

• Honest representation: The material you turn in for course credit must be a fair representation of your work. You are responsible for understanding and being able to explain and duplicate the work you submit.

• Active involvement: You must ensure that you are an active participant in all collaborations, and are not merely dividing up the work or following along while another student does the work. For example, copying another student's work without actively being involved in deriving the solution is strictly prohibited. 

• Give help appropriately: When helping someone, it is important not to simply give them a solution, because then they may not understand it fully and will not be able to solve a similar problem next time. It's always important to take the time to help someone think through the problem and develop the solution.

Workflows in Team

• Peers are an incredible resource. In the university setting, we learn just as much, if not more, from our peers than from instructors.

• Reach out via Discord channels: #student-help or #assignment-question about your technical problem. When posting a question make sure to include thorough details and screenshots of the problem you are facing so that a peer may be able to answer your questions.

• Have a backup plan. When presenting a project proposal, make sure to describe the art style and how the team is planning to adopt the vision (here explaining game logic and functionality) and backup solution (generally simpler and easier technical solutions). 

• Review with the team and formulate a precise idea of how complete the demo simulation would be in each stage. -> For example, the team should determine how detailed their underwater-themed virtual stage will be before placing the dancers and tryout in HMD. Make a checkpoint before the team invest all their renounces to making one aspect of the play. Be realistic about it with your time. It is better to have something working even though the quality is not up to your vision. 

© You-Jin Kim

Santa Barbara