Project proposal 1

Unity Porting:

• Milestones:

  • Unity working on CCV (2/11)

  • 2019 version of Unicave attempt to evaluate all the issues. From talking with those who have worked on Unity porting in the past, it is getting stereo to work. (2/13)

  • If any other element doesn't work, consult with class. If only stereo doesn't work, first try cheap solutions such as Ethan's library fix or Quadifier. Report on results. (2/20)

  • If the above don't work, try a minimal version using vms (Docker was suggested) (2/25)

  • If vms provably don't work, then get a minimal version working on a dual-booted system (2/27)

  • If either of the above work, facilitate porting to the Yurt (3/03)

• Potential deliverables:

  • Vm Guide

  • A write-up why [software quad-buffer stereo, vms, dual-booting] does/doesn't work for the Yurt. Essentially, a compiled list of things tried w/explanation

  • A set of guidelines and extra software for working with Unity and then porting to the Yurt

  • A Unity display configuration scene. Potentially with added features such as software calibration

  • A repository with a default Unity configuration that works in the Yurt along with scripts for running it

• Potential class activity:

  • Guide on porting simple Unity app to the Yurt

  • Show off iatk

• Resources:

  • https://wiki.gentoo.org/wiki/GPU_passthrough_with_libvirt_qemu_kvm

  • https://unicave.discovery.wisc.edu/

  • https://www.reddit.com/r/vmware/comments/ab1n30/is_it_possible_to_dedicate_graphics_cards_to_a

• Data:

  • iatk

  • Polygonal model data

    • Treak cavern

Project Evaluation by Carlos

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

The proposed project involves previously unavailable Yurt data visualization functionality: 5

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

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

The proposed project includes an in-class activity: 5

The proposed project has resources available with sufficient documentation: 5

Loudon Project Evaluation by David 02/07/20

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

I (still) got lost in your journal.  I saw only the Vulkan MinVR part and thought that was the whole project...  Doh.  It sounds interesting, if the port magically happens super fast :-)  The deliverables sound great.

5  Anessa's project involves data within unity, and seeing that in the Yurt would be awesome.  Perhaps you and she can coordinate on milestones that she might then depend on.  The pig-chewing unreal example could have a unity-in-yurt version.

o The proposed project involves previously unavailable Yurt data visualization functionality

5

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

5

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

4  We shall see...  There are quite a few planets that all need to align...

o The proposed project includes an in-class activity

5

o The proposed project has resources available with sufficient documentation

4  Lots of risks, but all of them seem unavoidable and the rewards seem big enough to make the risks worthwhile...

o Also add any additional thoughts guided by the questions in the homework wiki entry.

Pretty sure Docker won't have the necessary functionality, but there are several VM possibilities to consider.  Don't restrict yourself to free ones.

This will be very awesome if it works.  Keep the communication lines open.  We should leverage all avenues for getting past the risks!

Loudon Evaluation by Ross 02/07/20

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

Lots of great deliverables! Good balance between tutorials, guides, and software porting deliverables. 

o The proposed project involves previously unavailable Yurt data visualization functionality: 5

Having Unity working in the YURT would be incredibly beneficial.

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

The Unity porting project does not mention any particular dataset; it might be helpful to choose a dataset from the Data Types wiki page to serve as a benchmark for your Unity experiments. 

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

Milestones are descriptive and include the necessary dates. Some of the milestones are quite ambitious. 

o The proposed project includes an in-class activity: 5

Each project contains a relevant in-class tutorial, with a nice focus on porting software to the YURT.  

o The proposed project has resources available with sufficient documentation: 4

Porting Unity to the YURT will not be easy! But it's worth a shot. 

Loudon Evaluation by Giuse 2/8/20:

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

5 Deliverables are clear, useful, and important

o The proposed project involves previously unavailable Yurt data visualization functionality

5 Parroting Ross and David's desire for Unity in the YURT

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

5 Unity is very powerful and clearly provide a large scope of visible data types

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

5 The schedule is clear, explicit and measurable, and I'm always optimistic about plans.

o The proposed project includes an in-class activity

5 Activity included

o The proposed project has resources available with sufficient documentation

4 I think there is a lot of resources, but documentation seems a bit more elusive, otherwise I don't think this attempt would be so long lasting.