Ethan Sattler Journal

Deliverables (so far):

• YURT-SDL

• Building Unreal Editor for the YURT

• Porting an Unreal Project for the YURT

Project Ideas -- Updated as of 2/4 with more updates coming soon:

• Finish YURT Unreal Support

  • Tasks:

    • Integrate Scalable's easyblend library into the render pass, add support for .pol files into the ndisplay configuration

    • Fix QuadBufferStereo

    • Generate an ndisplay configuration for the YURT (with eyetracking) and develop a simple game.

  • In Class:

    •  How to download/install a custom UE4 editor version. How to do the UE4 point cloud project but with nDisplay support.

  • Deliverables:

    • Write up on successes/failures of the Unreal Engine

    • Unreal Engine/Editor for the YURT

    • Tutorials on how to setup and build a basic game for the YURT (this should go on the tutorials section of the Wiki), update Unreal info on Wiki

    • YURT point cloud nDisplay project.

  • Schedule:

    • 2/11: Start packaging the SDL patches and fixes.

    • 2/13: Test remote rendering on windows over VGL/TigerVNC to determine if virtualization is a possibility, and continue working on Scalable port.

    • 2/20: Write a launcher for spawning Unreal processes for every screen in the YURT

    • 2/25: Fix the Quad Buffer Stereo issues or at least find the root cause of the problem

    • 2/27: Finish fixing QBS. Figure out how to connect the YURT’s VPRN server with the nDisplay primary node VRPN server, hopefully start testing scalable (with eyetracking). 

    • 3/03: Completed how to build/run documentation and the point cloud tutorial.

    • Post 3/03: TBD

  • Data:

    • Point cloud data -- from the Blender/UE4 tutorial

    • Architectural Visualization -- huge number of resources/alternatives, but here's one example: Architecture Real-time - Unreal Engine 4 Archviz

• Study Virtualization options for Unity (graphics card virtualization is difficult apparently)

Project Self-Evaluation by Ethan Sattler

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

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 -- 4.5

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

o The proposed project includes an in-class activity -- 4

o The proposed project has resources available with sufficient documentation Also add any additional thoughts guided by the questions in the homework wiki entry. -- 4.5

Project Evaluation by Anessa Petteruti

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

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 -- 4.5

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

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

o The proposed project has resources available with sufficient documentation Also add any additional thoughts guided by the questions in the homework wiki entry. -- 5

Ethan Project Evaluation by David 02/07/20

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

5

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

2  Some things that will be tried are listed, and some have durations.  But the schedule gets very murky after the initial part.  There are no milestones for the deliverables.

o The proposed project includes an in-class activity

5

o The proposed project has resources available with sufficient documentation

4  I see no way to avoid the risky possibly-missing dependencies.

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

I don't see why virtualization is involved?  That seems to add a high-risk element to the project that is not needed.  But maybe I'm missing something?

Ethan Project Evaluation by David 02/07/20

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

Deliverables are explicit and clear.

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

Visualizing pointcloud data with Unreal would be quite interesting and useful.

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

Milestones could be fleshed out a bit; in particular, it would be nice to have a milestone for each class day.

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

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

Ethan Project Evaluation Giuse 2/8/20

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

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 5

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

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

I agree with David that there is some risky areas where you must innovate.

• VRPN Tablet Library

  • 
    

1/23: 2 hours.

• Through 1/28:

  • Installed paraview

  • Created this page

  • Total time: 1 hour

• Through 1/30:

  • Created the list of project ideas

  • Read required readings: YURT Software, Data Types, Examples, Collaborators, and Software Evaluation.

  • Total time: 2 hours

• Though 2/4:

  • Installed Unreal and Blender on Windows (had previously installed blender on Linux): 1 hour

  • Setup a Windows Virtual Machine to test nDisplay under virtualization: 1 hour

  • Started trial/error testing of the quad buffer stereo render loop: 3 hours

• Though 2/11:

  • Started trial/error testing of the quad buffer stereo render loop: 6 hours

• Though 2/20:

  • Time allocation:

    • Got Quad Buffer Stereo working on Vrlab machine: 2 hours

    • Unreal engine work: 4 hours

    • YURT testing: 3 hours

    • Total: 9-ish hours

  • Milestones:

    • Got Quad Buffer Stereo working on Vrlab machine!

    • Got QBS working on Unreal!

Self-evaluation:

1. Journal activities are explicitly and clearly related to course deliverables - 5

2. deliverables are described and attributed in wiki - 4

3. report states total amount of time - 5

4. total time is appropriate - 5

2/24 - Worked on launcher 3 hours

2/26 - Worked on Scalable - 2 hours

2/27 - Worked on Scalable - 4 hours

3/3  - Worked on Scalable - 4 hours

3/9 - Worked on Project presentation 1.5 hours

Week of 3/20: 12 hours on Scalable over the course of the week.

Week of 3/27: Project 2 Proposal (Continuation)

• Finish YURT Unreal Support + Point Cloud Visualization

  • Tasks:

    • Integrate Scalable's easyblend library into the render pass, add support for .pol files into the ndisplay configuration

  • In Class:

    •  How to download/install a custom UE4 editor version. How to do the UE4 point cloud project but with nDisplay support.

  • Deliverables:

    • Tutorials on how to setup and build a basic game for the YURT (this should go on the tutorials section of the Wiki), update Unreal info on Wiki

    • YURT point cloud nDisplay project.

  • In class activity: 4/14 or 4/21? 

  • Schedule:

    • 4/9: Have point cloud project working locally

    • 4/12: Add documentation to wiki

    • 4/13: Finish Scalable integration. Almost done but Unreal is being unfriendly...

    • 4/20: Finish YURT Configuration file

    • 4/24: Have point cloud project working in YURT

    • TBD (I want to have some flexibility in the case of unforeseen issues)

  • Data:

    • Point cloud data -- from the Blender/UE4 tutorial

    • Architectural Visualization -- huge number of resources/alternatives, but here's one example: Architecture Real-time - Unreal Engine 4 Archviz

Week of 3/27:

• 4/1: 3 hours

Week of 4/6: 

• 4/11: 6 hours

• 4/12: 5 hours

Week of 4/13: 12 hours

Week of the 4/20: 14+ hours

Week of 4/27:

• 4/27: 5 hours

• 4/28: 5 hours

• 5/1: 5 hours

Week of 5/4: 10 hours

Week of 5/11: 16 hours

• 5/12: 2 hours

• 5/14: 7 hours

• 5/15: 7 hours

Evaluation by Anessa:

 (5) Overall, I think it is a great, logical continuation of Project 1, and the deliverables, activity, and timeline are really clear as laid out in the proposal. I also think it’s really smart how you left some buffer time at the end of April for any issues that may come up!

Evaluation of project 2 draft by David 3/31/20

Looks great, Ethan.   I'm psyched!  Let's do our best to leverage any and all help on issues that might slow progress down.  Keep us apprised and reach out to CCV folks or others if you hit a snag.  Things are very close, but time is short.  I have the sense that there might be more wiki contributions.  Perhaps ponder and flesh that out a bit more in a revision?

Evaluation of Project 2 by Ross 03/21/20

Awesome proposal! Well written and detailed. If you want any additional pointcloud data, I can send some over.