Course Timeline and homework

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 : intro

Weeks 2-3 project 1 planning and some tutorials to support that.

Weeks 4-8 project 1, including proposal presentations; journal reviews; project status presentations; project tutorials; unreal; software porting; project 2 planning; paraview yurt surface rendering

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

Week 1 

Class 1/23

HW for 1/28:

Week 2

Class 1/28

HW for 1/30:

Class 1/30

HW for 2/04:

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.

How to integrate applications to the YURT I.pdf
How to integrate applications to the YURT II.pdf

Week 3

Class 2/04

First half of class:

Second half of class:

HW for 2/06: 

Class 2/06

HW for 2/11:

o  Note that these first project should have milestones for 2/13, 2/20, 2/25, 3/03, 3/05, 3/10. Second-half projects will begin on 3/17 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 previously unavailable Yurt data visualization functionality

o The proposed project involves large data visualization along the lines of the "Data Types" wiki page and identifies the specific data 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/11

HW for 2/13:

Class 2/13

HW for 2/20:

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

Week 5

Class 2/18 (University Recess - No Class)

Class 2/20

HW for 2/25:

Week 6

Class 2/25 at the Yurt

HW for 2/27:

Class 2/27

HW for 3/03:

Week 7

Class 3/03

HW for 3/05

Class 3/05

Week 8

Class 3/10

Class 3/12

HW for 3/17 (now officially due 3/30, but sooner will help everyone get and give feedback)

Week 9

Class 3/17 (cancelled, but David will be in zoom at

HW for 3/19 (now officially due 3/31

Class 3/19 (cancelled, but David will be in zoom at

HW for 3/31 (AFTER BREAK!)

Week 10

Class 3/24 (Spring Recess - No Class)

Class 3/26 (Spring Recess - No Class)

Week 11

Homework for  3/30

Homework for 3/31 

Class 3/31 

Class 4/02

Week 12

Class 4/07

Zach's Python activity in Google Colaboratory. Links can be found in his project 1 documentation. It should take 30-40 minutes to complete. 

Class 4/09

More Colaboratory work, quick project checkins, connect to yurt.

Week 13

Class 4/14

 Howdy, folks.  We will be mostly brainstorming on upcoming in-class activities.  In working with Spencer, we realized that crafting an engaging, relevant, and topical in-class activity involving paraview was going to be challenging.  This seems likely to be the case for Loudon with Unity, Ethan with Unreal, and Brandon with OpenSpace as well.

To help with that crafting process, I'd like the four of you to give think about some options for your activity that will help the rest of us provide feedback and input.  Everyone else should think about what activities involving those software packages might be useful for the data you are working with (or maybe just of interest to you personally).

Class 4/16

Week 14

Class 4/21

Loudon's Unity Activity (creating a simple Unity app and guide to port to the Yurt) Time to complete: 1.5 hours

Make sure to have Unity installed with the Linux Build module

Porting Guide

Class 4/23

Brandon's Openspace data exploration activity (Explained in project 2 plan here ) Time to complete: 1.5 hours

Week 15

Class 4/28 (reading period)

Class 4/30 (reading period)

Week 16

Class 5/05 (reading period)

Exam Period

 5/15 10:30am ET -- Remote Demos/Posters -- may run past noon