Things we'll do through the semester

• document our entire process to produce white paper or site on VR software

• characterize types of VR software users and their needs

• see some VR in action

• characterize types of VR software

• identify metrics for VR software

  • ease, power, depth, support, learnability, tutorials,

  • user base, types of users supported

• find and read papers and web about efforts like searis

• find and read papers and web pages about software

• download, install, and try software

• if tutorials exist for software, do them

• Create tutorials for how to use data visualization software

• Interview some experts

  • Application scientists at research labs

  • Vis/VR managers at research labs

• Create, post, and analyze survey results

  • software used

  • software evaluation

• Flesh out gaps in document

• Iterate on everything to fill in more gaps

TODO List 2/13/18

First, I'll define "course deliverable" as something that goes into the final paper or the state-of-the-field website we're building.

1) Add a progress report to your journal, modeled on what we did in class. Be concise and include the three aspects we discussed: the course deliverable, the activity or activities that support (or comprise) that deliverable, and the relationship of each activity to the deliverable. It's fine to have multiple deliverables. Please also include include the total time spent up through this report. Note that it's also fine (and expected) that some of your activities may not have been targeted at a deliverable. Please list them as such and describe their value.

2) For each deliverable you list, indicate where it lives in our resulting final paper, under the "manuscript" page, or website, the "home" page. Put something in the manuscript draft to represent the contribution. It can be something like "Results of comparison of Hello World implemented in Blender and Unity [table of numbers]." This may involve some fiction, which is total fine. If you don't know what to add or where to add it, may be it isn't a deliverable or maybe the manuscript or home page needs to be adjusted.

3) Add a multi-week plan to your journal. It should include predictions of what a report like 1) above would look like, when you do it again on March 6th. Also include how long you expect each activity to take, in hours. This is a prediction, but when you look back you can calibrate future predictions better. For this plan, include specific milestones for the interim class dates: 2/13, 2/15, 2/22, 2/27, 3/1, 3/6.

4) For each deliverable in 3), predict where it will go in the manuscript or home page, but don't actually edit it in.

5) There are a number of unlinked pages under the "Manuscript" page (which used to be the "Resources" page). Please incorporate those into the Home page, linking them into the outline on that page, labeling them on the Home page, and moving them into the page hierarchy under Home.

TODO List 2/6/18

For Tuesday 2/6 class

GROUP 1: Kyle Cui (DEMOING HMD AT CCV), Amedeo Alberio, Kevin Dackow

start at Yurt, go to CCV HMD at 11:10

GROUP 2: Zach Dixon, Brett Halperin, Edwin Hidalgo

start at Yurt, go to 546 at 11:10

GROUP 3: Elaine Jiang, Jen Kaplan, Jacob Leiken

start at Yurt, go to gfx lab at 11:10

GROUP 4: Ruiqi Mao (DEMOING HMD AT CCV), Brandon Li, Cyrus Maden

start at CCV HMD, go to Yurt at 11:10

GROUP 5: Duncan McManus, Daniel Nam, Linda Park

start at 546, go to Yurt at 11:10

GROUP 6: Ankita Sharma, Martin Uildriks, Charles Njoroge

start at gfx lab, go to Yurt at 11:10

Fumeng Yang DEMOING IN 546

Zach Dixon DEMOING AT gfx lab

TODO List (aka homework) 2/1/18

• make sure you've done everything for Tuesday, especially if it was your first day

• start to create and populate the "Resources" page. It is currently empty (except for an errant footer). Create sections and entries or copy sections from the "David's notes while talking with Dan Keefe" file. Create pages off of that for specific software or elements in other sections (hardware, types of users, etc.). Populate with info from your notes. I (David) will check that out Thursday morning to see if there are places where some in-class group work will be helpful. But also feel free to communicate with others about possible organizational or content decisions that you are making.

• start to think about and possible make summary evaluative info for software: time to install, time to create a bouncing ball example, OS's supported, graphics HW supported, dependencies, etc.

• start to think about and document possible activities that would help to evaluate software at various levels. We had a couple examples of tutorials that folks did and of VR environments that some tried to make.

• don't forget the minVR tomorrow, Wednesday, noon meeting with pizza and software edification. 180 George. Bring your laptop, if possible. The software works on mac, linux, and windows, from what I understand.

The homework goal is 10 hours logged per week on average over the semester. I won't repeat that every time, so refer back here if necessary

TODO List (aka homework) 1/30/18

• read some sources; annotate, augment, and organize

• create new pages for various lists and start to populate

• add your knowledge about users, software, places, etc., as you learn it

• create your journal page

  • name and contact info

  • skills

    • practice with software downloading and installation on linux and/or windows

    • experience with a game engine

    • 3D modeling and/or animation

    • software testing, evaluation, and documentation

    • software engineering like cs32 or cs33

    • computer graphics, like cs123 and/or cs224

    • human-computer interaction, like Jeff's HCI class

    • other?

  • VR interests

  • log 4 hours of activities you've done by the second class