Course Timeline and Homework

Editable Link

Course schedule, in and out of class.  Subject to change, particularly further in the future. If you have any ideas for a future class, please add them here!

Timeline Summary

Week 1-2: Course and wiki introduction, Headset handouts and logistics

Weeks 3-4: Plan and start project 1

Weeks 4-9: Project 1; project 1 in-class activities, journal reviews; project status presentations; project tutorials; project 2 planning

Weeks 9-15 Project 2; project 2 in-class activities, project status presentations; journal review, project tutorials and activities

Week 16:  Final project presentation preparation

Week 17: Final project presentations

Project 1 Class Activity Dates

2/28: Melvin (30 mins)

3/02: Lexi (20 mins), Mohammed (20 mins)

3/07: Dave (20-30 mins), Yifei (20-30 mins), Yuanbo (10 mins),

3/09: Brian (30 mins), Ashley (30 mins), Austin (30 mins)

3/14: Camilo (variable), Liza (30 mins), Vincent (30 mins),

Week 1 

Class Thursday 1/26:

HW due Monday 1/30 @ 12:00 noon:

To take this class you must complete the assignments below by Monday 1/30 @ 12:00 noon

Week 2

Class Tuesday 1/31:

HW for Thursday 2/02:

Here is a start to fill in.  It uses with fixed-width font "Courier New" to help with vertical alignment.   We will refer back to this at the end of the semester, so consider what you will be thinking then.

before after
----  ----
  1   | 5 | Goal 0: example goal showing "novice" score before and "expert mentor" after
      |   | Goal 1:  [fill in]
      |   | Goal 2:
    .  .  .

      |   | Goal 8:
      |   | Goal 9: ______________________________

Class Thursday 2/02:

HW for Tuesday 2/07:

Deliverables are what future readers of the wiki will look at and learn from. Examples might be comparative prose about different software packages, a Consumer-Reports style table of evaluations of features and quality of different software, tutorials showing how to use software for data visualization purposes, measurements of how long it takes and how difficult it is for a group to do a tutorial, etc.  A good way to make sure you have a deliverable is to say explicitly where it will go in the wiki.

Week 3

Class Tuesday 2/07:

First half of class:

Second half of class:

HW for Thursday 2/09 (due 9AM!): 

Class Thursday 2/09:

Below are a set of questions that should help in evaluating project ideas. Answer each with one of:

The questions are “The proposed project …”

HW for Tuesday 2/14:

Note that these first project should have milestones for 2/14, 2/16, 2/23, 2/28, 3/02, 3/07, and 3/09. Second projects will begin on 3/14 and go through the end of the semester. Here is an evaluation rubric for projects:

Below are a set of questions that should help in evaluating project ideas. Answer each with one of:

The questions are:

o The proposed project clearly identifies deliverable additions to our VR Software Wiki

o The proposed project involves collaboration in VR

o The proposed project involves large scientific data visualization along the lines of the "Scientific Data" wiki page and identifies the specific data type and software that it will use

o The proposed project has a realistic schedule with explicit and measurable milestones at least each week and mostly every class

o The proposed project explicitly evaluates VR software, preferably in comparison to related software

o The proposed project includes an in-class activity, which can be formative (early in the project) or evaluative (later in the project)

o The proposed project has resources available with sufficient documentation

Week 4

Class Tuesday 2/14:

HW for Thursday 2/16:

Activities logging rubric -- fill in in your journal

Activities logging rubric

key for each criterion:

5 == exceeds expectations

4 == meets expectations

3 == mostly solid with some gaps

2 == shows some progress

1 == some attempt

0 == not found


Journal activities are explicitly and clearly related to course deliverables

deliverables are described and attributed in wiki

report states total amount of time

total time is appropriate

Class Thursday 2/16:

Week 5

No Class Tuesday 2/21: Long weekend

HW for Thursday 2/23:

Class Thursday 2/23:

HW for Tuesday 2/28:

Week 6

Class Tuesday 2/28:

HW for Thursday 3/02:

Class Thursday 3/02:

HW for Tuesday 3/07:

[David asks that you sideload the apk before class, please, and make sure it runs]

Week 7

Class Tuesday 3/07:

HW for Thursday 3/09:

Class Thursday 3/09:

HW for Tuesday 3/14:

Week 8

Class Tuesday 3/14

HW for Thursday 3/16

Class Thursday 3/16

HW for Tuesday 3/21

Week 9

Class Tuesday 3/21

HW for Thursday 3/23

Note that your project should have milestones for 4/04, 4/06, 4/11, 4/13, 4/18, 4/20, 4/25, 4/27, 5/02, 5/04. 

Class Thursday 3/23

Week 10

Class Tuesday 3/28 (No Class - Spring Recess)

Class Thursday 3/30 (No Class - Spring Recess)

Week 11

HW for Tuesday 4/04

Class Tuesday 4/04

HW for Thursday 4/06

Class Thursday 4/06

Week 12

HW for Tuesday 4/11

Class Tuesday 4/11

HW for Thursday 4/13

Class Thursday 4/13

HW for Tuesday 4/18

Week 13

Class Tuesday 4/18 

HW for Thursday 4/20

Class Thursday 4/20 

HW for Tuesday 4/25

Week 14

Class Tuesday 4/25

HW for Thursday 4/27

Class Thursday 4/27

Mohammed's in class activity

HW for Tuesday 5/02

Week 15

Class Tuesday 5/02 

HW for Thursday 5/04

Class Thursday 5/04 

HW for Wednesday 5/10 @11:59PM:

HW for Tuesday 5/09

Week 16

Class Tuesday 5/09 

For our last class before finals we will review poster drafts, and rehearse full-semester flash talks -- both will help prepare you for the final public presentations (see Class 5/18 for more info). Since those will still be over a week away, it's ok to have some placeholders. 

Final Poster Draft Format Options

Final Poster Guidelines


The poster should be in landscape orientation -- wider than high.  42'' wide by 30'' is a pretty good size if you are printing from Room 475.


You can use the software of your choice to create the poster, but we recommend Powerpoint, Photoshop or Figma. You'll want to resize your slide / photoshop canvas to the actual size of the poster (e.g. 42'' wide by 30'' height, more details about printing size are in the section below). For Powerpoint, this can be done using the resize slide feature. For Figma, you'll want to make sure that the aspect ratio of your frame matches the aspect ratio of your print. Please be careful not to make a blurry poster.  Images should be high-enough resolution that they are ~200-300 DPI when printed.  Text should not be turned into an image. Ensure that images are high enough resolution when scaled to the correct size. For Figma, I've found that (6918 px, 3032 px) is a good pixel size. This can be rescaled to 42'' by 24.5'' poster size when printing. 


Since the format of the public presentations is similar to a science fair/research symposium, one way to think of a poster is as a set of sections that you can use to complement what you want to say.  The gist of your presentation should be understandable by your poster alone. 

There are 5 examples of posters from the past here: Final Posters.  Think about their visual layout and how you could present from them.  Jakobi and David are happy to give feedback on the posters before next week, and we will also do so after class to help you refine them for the public demos.

Flash Talk

Please prepare a flash talk of 40 seconds for Tuesday's (5/09) class.  Send Jakobi a powerpoint slide or a small number of slides with timings.  Jakobi will ensure that the total time for your slides is 40 seconds, and they will advance automatically.  There will be an additional 5 seconds between speakers to transition.

This flash talk for Tuesday's class will also be presented at the public demo, and as such, should be directed at a broader audience. Your flash talk should include an overview of your work during the semester, your public demo, and your poster. Think of the flash talk as a bite-sized pitch to attract people to stop at your poster and learn more about your project. 

Poster Printing instructions:

Week 17

HW for Wednesday, 5/17

before after
----   ----
  1   | 5 | articulate VR visualization software tool goals, requirements, and capabilities
  1   | 5 | construct meaningful evaluation strategies for software libraries, frameworks, and applications; strategies include surveys, interviews,      comparative use, case studies, and web research
  1   | 5 | execute tool evaluation strategies
  1   | 4 | build visualization software packages
  1   | 4 | comparatively analyze software tools based on evaluation
  1   | 4 | be familiar with a number of VR software tools and hardware

  1   | 4 | think critically about software
  3   | 5 | communicate ideas more clearly
  1   | 3 | explore how VR could be used collaboratively

Class Wednesday 5/17 Time: 2-3:30p Final Presentations!

Please come to CIT 101 at 1:45p by the latest to set up posters and demos. 

The final public presentations will have each person presenting a 40 second flash talk in front of a projector about their project to the audience.  That will happen at 2:15. The rest will be done in a science-fair like format: each person will stand in front of their posters on easels and invite passersby to hear their project presentation and try out their interactive VR demo. Make sure to bring your headsets and print your full sized posters early!

Class Final Projects

Virtual Reality for Collaborative Data Visualization

Wednesday, 5/17/22, 2-3:30

CIT 101


2:15-2:30pm: flash talks presented with slides in CIT 101. 

2:00-2:15 and 2:30-3:20pm: posters and live demos.