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: Course introduction and project 1 planning 

Weeks 2-4: Plan and start project 1

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

Weeks 9-14 Project 2; project status presentations; journal review, project tutorials and activities

Week 15: Final presentations 

In-Class Activity Schedule Prefs

Week 1 

Class 1/27:

HW due MONDAY 1/31 @ 12:00 noon:

(You must complete the assignments below by Monday 1/31 @ 12:00 noon)

Week 2

Class 2/01:

HW for 2/03:

Class 2/03:

HW for 2/08:

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 2/08:

First half of class:

Second half of class:

HW for 2/10: 

Class 2/10:

HW for 2/15:

Note that these first project should have milestones for 2/15, 2/17, 2/22, 3/01, 3/03, 3/08, and 3/10. Second-half projects will begin on 3/16 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 includes an in-class activity

o The proposed project has resources available with sufficient documentation


Week 4

Class 2/15:

HW for 2/17:

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

Criteria:

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 2/17:

Week 5

Class 2/22 (University Recess - No Class)

HW for 2/24:

Class 2/24:

HW for 3/01:

Week 6

Class 3/01:

HW for 3/03:

Class 3/03:

HW for 3/08:

Week 7

Class 3/08:

HW for 3/10:

Class 3/10:

HW for 3/15:

Week 8

Class 3/15

HW 3/17

Class 3/17

HW for 3/22

Week 9

Class 3/22

HW for 3/24

Note that your project should have milestones for 4/05, 4/07, 4/12, 4/14, 4/19, 4/21, 4/26, 4/28, 5/03, 5/05. 

Class 3/24

Week 10

Class 3/29 (No Class - Spring Recess)

Class 3/31 (No Class - Spring Recess)

Week 11

HW for 4/05

Class 4/05

HW for 4/07

Class 4/07


Week 12

HW for 4/12

Class 4/12


Completeness Review

Please answer yes or no to each of the following questions:


Quality Review

Please evaluate your partner’s overall journal using the following criteria:

In addition, please explain why you chose the number you selected.


HW for 4/14

Class 4/14

HW for 4/19

Week 13

Class 4/19 

HW for 4/21

Class 4/21 

HW for 4/26

Week 14

Class 4/26

HW for 4/28

Class 4/28

HW for 5/03

Week 15

Class 5/03 

HW for 5/05

Class 5/05 

HW for 5/10

Send slides to David for final project presentations 

Week 16

Class 5/10 


For our final class we will have concise final presentations of second projects as well as full-semester flash talks.  Both will help prepare you for the final public demos.  Since those will still be over a week away, it's ok to have some placeholders. The content of the presentation should be more directed at the class, while the poster that accompanies the talk can be directed at the public. 


Project 2 Presentation


The project 2 presentations should be 3 minutes long.  If you go over, I will warn you at 3:15 and stop you at 3:30.  Please practice to get the timing close!


Project 2 presentations should focus on your VR+data+collaboration learning during the second project.  I would hope that what you learned is captured in wiki pages, so you might want to include the names of those pages and some of the main messages captured there, particularly evaluative info.


The idea with the presentations on Tuesday is to:

(1) prep you for your final presentations

(2) provide an opportunity for you to highlight your results for project 2, as we did with project 2.


Although the project 2 presentation is prep for talking to guests who come to your public demos, the content of what you say will have to adjusted to their body of knowledge--this is to say that guests will know less about VR than the class, so your discussions at the public demos should adjust accordingly. 


The project 2 presentations will be limited to only your project 2 results. You'll want to extend your poster to include learnings from project 1 as well for your final poster.


You have a choice for how to do these presentations.  I recommend the first option, which is to present from a physical poster.  That will give you practice creating one and presenting from it.  You can then use an updated version for the final public demos.  It would be fine to have material not necessary for this project 2 presentation that you will use during the public demos, eg, info from your first project.  It's also ok to have some space left to do that.  The second option is to create a single-slide powerpoint "poster" and present from that.  That will mean using a 16:9 aspect ratio and having the much lower resolution of a projector.  The third option is to use slides as we've done for other presentations.  I am offering this option since I hadn't specified the poster earlier, but I fairly strongly encourage you to use the first.


Please reply in the slack by Saturday with the option you are going to use.  If you are going to use slides, please get them to me enough before class that we can assemble them.


Poster - Class Presentation vs. Final Presentation


Since the poster can be used to present with both the project 2 presentation and the public demo, for our final class it can include information solely about project 2, and it can be updated to give a full semester overview for the public demo. It could also include a full semester overview, and when presenting on Tuesday's class you can focus on what you learned from project 2 only. The content of the presentation on Tuesday should be directed at the class. 


Final Poster Guidelines

One way to think of a poster is as a set of regions similar to slides that you can use to complement what you want to say.  It's also helpful to have the poster able to stand on its own, so the gist of the flash talk should be there in a way that a viewer can understand it without you being present.


There are 5 examples of posters from the past here: https://www.vrwiki.cs.brown.edu/course-archives/spring-2020/2020-final-posters.  Think about how you might present from them and copy the parts of their structure that you think are useful.  Ross and I 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.


You can use either Powerpoint or Photoshop to create a poster. You'll want to resize your slide / photoshop canvas to the actual size of the poster (e.g. 4' wide by 3' height). For Powerpoint, this can be done using the resize slide feature. 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. 


In order to better handle slides and posters together, let's go with landscape orientation -- wider than high.  4' wide by 3' high is a pretty good size.  4' wide by 2.25' high is standard HDTV (projector) ratio -- I find that to be uncomfortably and awkwardly short when printed.



Flash Talk


Please also prepare a flash talk of 40 seconds for Tuesday's class.  Send me a powerpoint slide or a small number of slides with timings.  I 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. It should focus on what you learned about Data Viz + Collaboration over the course of the semester.



Poster Printing instructions:

Week 17

Class 5/19 2pm final exam period!

Class Final Projects

Virtual Reality for Collaborative Data Visualiztion

Thursday, 5/19/22, 2pm

CIT 101


[pictures]


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

2:15-3:20pm: posters and live demos. Where will this be?

Cookies!