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!
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
Beatrice - March 1st - tutorial on UNH's VR point cloud editing software (est 30 minutes)
Jakobi - March 3rd - Real-time Collaborative Tweet Data Exploration on a Webpage (est 40 minutes)
Amanda - March 3rd - Women in the Olympics (est 45 min)
Lucia - March 8th - VR vs 3D model navigation task (est 45 min)
Mandy - March 10th - MEMS data (40 min)
Robert - 3rd or 8th - collaborative archaeological map (est 40 minutes)
Maia - 3rd or 8th - Openspace for Desktop (est 35 min)
Tongyu - 8th or 10th - dynamic audio vis (est 30 min)
Alastair - 3/3 or later - sentiment analysis in VR
Paul - 3/8 or later - mars in VR (est 45 min)
Nick - 3/10 or later - collaborative urban planning
Aakansha - 3/24 or later (after spring break) - chemical data visualization (est 40 min)
Class motivation, goals, structure, syllabus, wiki
Give a breakdown of the wiki
What was done last year
What is expected this year
Where to find everything
Project-oriented structure for class
How to evaluate a piece of software -- a brief explanation
Start planning projects
HW due MONDAY 1/31 @ 12:00 noon:
(You must complete the assignments below by Monday 1/31 @ 12:00 noon)
Join the course slack channel (https://join.slack.com/t/cs1951t-2022/shared_invite/zt-12j193238-pTOfCok_dlSGPYdq4uXpug ) and introduce yourself on it (briefly)
Review the course homepage
Read some of the last year's wiki and identify (but do not implement!) nine separate changes you would make to the wiki, each requiring varying amounts of time to complete:
Three changes should each require ~10 minutes to complete.
Three changes should each require ~1 hour to complete.
The final three changes should each require ~10 hours to complete.
Log these changes in your journal.
Execute one of the 10-minute changes.
Log a total of 4-5 hours of homework time in your journal; this could include doing some of the following activities:
Read some background papers
Research a piece of collaborative VR software -- this could be a game, a framework, or anything else related to collaborative VR
Research data types, data examples, software tools, other institutions doing big-VR visualization work
Do things from Course Activities page
Log time and any issues in your journal
Ponder project ideas (always!)
Discuss wiki tasks and changes from homework
Introduce project guidelines (i.e. explain milestones, in class activities, and deliverables)
Brainstorm project ideas
(hopefully) distribute headsets
HW for 2/03:
Continue with activities from previous homework
Pick 2-5 potential pieces of software to explore and evaluate for your research project
Using this software, create 3-5 potential project ideas in your journal. Be prepared to share concisely (one sentence each) in class. We will ponder their levels of: 1) collaboration, 2) immersive VR, 3) scientific visualization.
Project ideas discussion
HW for 2/08:
Review wiki / web to solidify your 3-5 project ideas
For each project idea:
list three things you will do during the project
list one class activity we might do for the project
list potential deliverables:
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.
If you are confused or have any questions, feel free to post on the slack or email the TAs
Brainstorm software evaluation metrics
Continue adding potential software / data to the wiki
First half of class:
40 minutes: intro by Johannes Novotny + DinoVR Tutorial
Second half of class:
15 minutes: Pair up and review project titles, and activities. Working together, add deliverables to each potential project. Ask questions if you are not sure what to do. Each student should pick their first-choice project.
identify what you need to learn and do before this first project begins so that you can design it to be successful. The projects will start next week, so you have only one more week for this pre-project work. Check out what we will do on 2/10 to help guide this.
25 minutes: go around room and explain the project that you most want to do, including what we might do in class for it, what wiki deliverables you will produce, and what you need to do before the project. This will be done for each student via a max 1-minute individual oral-only presentation (no slides) followed by slightly longer discussion. I recommend speaking from notes, and I also recommend putting them in the shared class gdoc file at https://bit.ly/3r5J13f.
Document your potential pre-project activities in the wiki before leaving class
HW for 2/10:
Select one project from your list of potential projects and create a plan for your project. This project plan should have milestones to be delivered on 2/15, 2/17, 2/22 (2/24 is a holiday), 3/01, 3/03, 3/08, and 3/10. The project plan should include activities that span from February to the middle of March
Continue reading, doing, and logging with any extra time
30 minutes: Pair up with someone you haven’t paired up with before and jointly evaluate your pre-project plans. Evaluations should consider:
Will the project deliverables be useful and significant?
Will the project activities improve the potential quality of the project?
Will the project activities help identify and reduce project risks? Risks often involve external dependencies that end up not being met or over-optimistic estimates of time required.
Will the project activities themselves add deliverables to the wiki?
Go over any questions from above, beginning with project concepts, deliverables, and activities described very briefly.
Look ahead to the Project Evaluation questions/criteria below.
40 minutes: Each person should present to the class a 2-minute evaluation of another project. Essentially, it should discuss the answers to the questions discussed, both positive and negative with the goal of getting additional confidence about the evaluation and any additional suggestions.
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:
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
HW for 2/17:
Prepare journal for in-class review. Journals will be evaluated according to the following rubric:
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
Using the above rubric, evaluate your journal and include your self-evaluation in your journal
Class 2/22 (University Recess - No Class)
HW for 2/24:
HW for 3/01:
HW for 3/03:
Prep for Amanda's in-class activity by following the download instructions on this page
No prep needed for Jakobi-'s in-class activity
Work on projects
First half of class: Women in the Olympics (Amanda's in-class activity; est 45 min)
HW for 3/08:
Prep for in-class activities
Work on projects
First half of class: Openspace for Desktop (Maia's in-class activity; 45 min)
Second half of class: Mars in VR (Paul's in-class activity; 35 min)
In class activity: Analysis of EMS calls (Shashidhar's in-class activity; ~20mins)
Project 1 Presentations
HW for 3/22
Project 1 overarching take-home discussion
7 scenarios paper and project 2 discussion
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/29 (No Class - Spring Recess)
Class 3/31 (No Class - Spring Recess)
HW for 4/05
Peer journal evaluation
HW for 4/07
Consider the levels in Bloom's Taxonomy below as you deepen understanding of the knowledge you have put into the wiki and planning to put in the wiki. This is often used to capture learning in education, but it makes sense in any context involving learning about new things.
Sayan's in-class activity
Alastair's in-class activity
Bloom Taxonomy ,seven scenarios, software evaluations, and wiki insights
HW for 4/12
Refresh Bloom Taxonomy in your brain
Make sure journal is ready to review in class -- no missing links, hours up to date, etc.
Bloom taxonomy discussion (maybe seven scenarios as well)
Journal peer-review. Please evaluate a peer's journal according to the following rubric. Post your review in your partner's journal along with your name:
End-of-semester logistics discussion
HW for 4/14
Choose one of your wiki pages to have reviewed in class (and perhaps spruce it up, if you know of issues). Choose something where you feel like you would benefit from feedback.
Make sure your journal is ready for a peer-review
Hacking on the Wiki: review + editing
Journal peer review (see last class for rubric)
HW for 4/19
Create progress report and send to David at least 24 hours before class. Media must be embedded in the presentation (no external links) and presentation must be in .pptx format!
HW for 4/28
HW for 5/03
HW for 5/05
HW for 5/10
Send slides to David for final project presentations