Giuse Nguyen journal
1/28/19 Installed Paraview(2 Hours)
1/28/19 Read The Computer Scientist as ToolSmith II (40 mins)
Fairly short article about the positions of Computer Scientists as engineers that demand high performance.
1/28/19 Read VR Software to find things add(1.5 hours)
1/28/19 - Added VR Juggler Notes(1 hour) - outdated by 3+ years.
(Sanity Total : 5 hours, 10 mins)
--
2/3/19- Read up on Vive and Oculus, manuals and saw game demos online(2 hours)
2/4/19 Project Ideas: (3 Hours)
Project 1: Investigating how to calibrate multiple actions into VR space, i.e more than just hand simulation, looking into action simulation like the Wii. I’d like to see if other controllers could work with the pieces of VR technology that currently have, either through actual work/modding or just research.
Class: Learn about infrared motion/compared to VR motion.
Project 2: Learning about the CAD in VR-AR space programs that Microsoft and Autodesk appear to try and promote, and developing some program to add/ameliorate that experience. AR goggles to expand the detail of a room/area.
Class: Use a AR program for design/look at another person’s design.
Project 3: Utilize VRJuggler or other API to create another VRData visualization program/ compare with Paraview/other software… seems ambitious. The steps would be to download VRJuggler, then begin using its current capabilities on VR datatypes.
Class: Learn about the empty documentation that is VRJuggler.
https://en.wikipedia.org/wiki/Virtual_Boy - very interesting note in nintendo console history(2 hours), I was inspired to learn about investments of business sphere/ gaming sphere into VR pre-Oculus
----
Planning out future work days: (30 mins)
Plans for 2/12, 2/14, 2/21
Likely starting with a lighter load project, comparison of two to three design softwares, from features(more clear) to quality(vague).
2/12- Learn about Autodesk Maya, and Google Sketchup, and Blender, experience with Blender. (Install the programs) - An quick installation guide on Wiki if its not there.
2/14 - Have parallel tutorials done. Modeling - create some sand castle. Have metrics of comparison, (features, usability,)
2/21- Aim to have a written/ready form of study if I need to use a survey/ find one.
(S Total: 12 hours 40 mins)
--
2/8/19 Installed Autodesk Maya using student verification(2 hours)
2/9/19 Browse https://vr-plugin.com/ to learn about the Maya plugin.(2 Hours) Compare thoughts with Domemaster3D. (3.5 hours Cumulative)
(S Total: 18 hours 10 mins)
Self-Eval of Journal
Journal activities are explicitly and clearly related to course deliverables (4)
deliverables are described and attributed in wiki (4)
report states total amount of time (3)
total time is appropriate (3)
Peer-Review
Journal activities are explicitly and clearly related to course deliverables (4)
deliverables are described and attributed in wiki (3)
report states total amount of time (2)
total time is appropriate (3)
--
Creating milestones and presentation(1 hour 20 mins)
2/14/19 Learning about CCV and the YURT, trying to SSH in when I hadn't installed any ssh programs in a while (2 hours)
2/14/19 Project Milestones For the Future
2/26 - 2/28 Create a tutorial for VR development in Maya, Append to the Google Sketchup tutorial
3/5- 3/7 Create or link a tutorial to export to viewers such as Paraview for viewing in VR lab, write the user study/have metrics.
3/12- 14 Show forms of scientific data created in Google Sketchup and Maya in VR lab, potentially use another software
3/21 -28 Unsure
4/ Present An overall discussion show how people can go through tutorials
--
(Sanity Total: 21.5 hours) --
2/24/18 - Completed online Maya tutorial, still don't understand how the VR port works specifically(4.5 hours)
2/26/18 - Read up on CAD and VR software connections, since 3D modeling is either completely compatible or one-step away from being compatible with 3D printing and design.
(Sanity Total: 26 hours)
3/1/18 Learned more about Unity ports(1.5 Hours)
3/3 Entry link to word doc of Maya Tutorial. (2.5 Hours)
3/4 Maya troubleshooting. My laptop ran out of SSD space, learned about how to add and edit meshes in Maya. Also learned about the example animal meshes already available. (1 hour)
(Sanity Total: 31 hours) --
3/5 Add to Maya Article by exploring VR in Maya, lots of googling(5Hours) Trying to learn about DomeMaster3D but there were too many compatibility issues. VisStudio 12 was not working with my windows laptop.
3/7 Trying out the machines with Maya in the VRLab (4 hours) same compatibility issues arise, DomeMaster3D is missing a plugin? Decided to make my project more about the quality of the VR port from the projects rather than their related VR viewers.
3/9 Start to explore Sketchup(4 Hours)
(Sanity Total: 44 hours)
3/11 Export to Unity(3 hours)
3/12 Sketchup to Unity article(1 hour)
3/13 Paraview viewing(1 hour)
3/14 Updated several hyperlinks on https://sites.google.com/view/brown-vr-sw-review-2018/vr-development-software#h.p_CYHBJiUbUJyA(.5 hour)
3/16 Viewing my Unity and Paraview ports on VR machines(2 hours)
(Sanity Total: 51.5 hours)
3/18 Draft Hello World tutorials that actually matter to the project, i.e. simple mesh/primitive creation into export.(6 hours)
(Sanity Total: 57.5 hours)
Pages Updated by Me:
Maya Port Explanation(Done+ Added 100%)
Maya Tutorial on Animation + Modeling for VR(100%)
I wanted to use fluid vector fields or biological models, not sure yet, else 100%.
Fluid vector fields proved to be too complex for a newbie.
Sketchup Port Explanation(100% Added )
Sketchup Tutorial (Installation + Post Free Trial)
Modeling Software to Visualization Software(Page added, added what I wanted to add to 100%)
Maya vs Sketchup comparison table(100% Added to Main page)
Unreal Engine VR, Added a brief contribution after digging around on internet to learn more(100%) - not relevant to project
Several logistics, hyperlinks on the menu pages
Just noted the menu for Modeling Software is empty, Fixed with some links (100%)
3/20 Test Fluid Vector Field examples, visible but export doesn't have the animation.(5 hours)
3/22 Made comparison table to add to the Modeling Menu page(1 hour)
3/25 End of Sketchup free trial for students, learned about the export features available on Sketchup Warehouse and documented it in the Sketchup page (2 hours)
3/31 Prepared Slides(2 Hours)
(Sanity Total: 61.5 hours)
Next is all of April, which was my second project work...
4/2 Finished Gary's ARCore Hello World tutorial after not being able to finish it due to an issue in my Android Studio, and I reinstalled it(3 hours).
4/4 I started with AR programming with Android Studio, but it didn't pan out. I was messing around with the aspects found in this video https://www.youtube.com/watch?v=BeoY5mRm1UY trying to create a portal camera trick app, which creates views to different scenes on windows. (10 hours)
4/5 Finished Visual MinVr setup on my own time, had to reset cmake and Visual Studio solutions (2 hours)
(Sanity Total: 76.5 hours)
4/9 I pivoted to IATK after checking the contents of the Kyoto VR conference projects.(2 hours)
4/16 Started with trying to install it and looking for strange compatibility issues which I found a decent number of, I don't know why IATK didn't document these. (8 hours)
(Sanity Total: 86.5 hours)
4/18 Deciding to make a full page for IATK, as a chart/variable VR Visualization software. Adding data is pretty easy. (1.5 hours)
5/3-- Adding to IATK page with Presentaiton information, and Elaine's(?) Metrics of Analysis. (5 hours)
4/20 I learned about VRTK, the dependent repo for IATK, which was updated farther than what IATK was allowed for, so I had to revert to an older version(6 hours)
(Sanity Total: 99 hours)
4/23 I also experienced all of the functionality from Brushing and Linking to drag and move. (10 hours of debugging/ version checking, and just being super confused until I found out it did after one my fixes over those hours did something. I suspect the controller of the HTC Vive Pro was an issue because there was a warning message in the console, but it just used the HTC Vive settings and they worked.
4/25 Small write-up of an VRTK tutorial that was only available on video, their documentation is sub-par but not completely ignored or enigmatic. (4 hours)
4/30 Created Final Results Slides, and continued to work on trying to set-up a video recording (4 hours).
5/1 Created Video for slides that shows basic pipeline of a researcher or user who uses IATK to learn trends. (1 hour)
5/5 Needed extra hours, so I created another page on the filetypes produced by Maya and Sketchup, namely .obj, .dae, and .fbx. (6 hours)
5/8 Needed extra hours, so I updated my Maya page with user metrics (2 hours)
(Sanity Total: 120 hours) --
Needed to document my suffering with Brushing and Linking. ^
5/9 - Designed poster for presentation - 4 Hours
(Sanity Total: 124 hours)
FINAL Checklist - Laundry to make sure I did it:
15% class attendance and participation(^) - Was there for class.
10% initial search contributions to wiki(^) - Added to VR Juggler talked about what it was designed for, cleaned up Modeling and Visualization pages, added some excerpt into VR for Unreal.
15% project design, creation, data collection, and analysis contributions(^) - Wiki contributions for IATK, Maya, Sketchup, and Created tutorials for porting, and basic use cases.
1) Maya Page Update
2) Porting to Visualization Software Tutorial, (discussion of .obj filetype)
3) Sketchup and Maya super simple tutorials
4) Menu Page added a table
4) IATK Page complete with User feedback from class and friends.
5) IATK Tutorial for class
20% tutorial quality(^) - Can't judge it unbiased.
10% tutorial results analysis(?) - Had both qualitative and quantitative results/ comparison tables.
15% journal of activities and findings(^) - Here.
15% overall final wiki contributions(^) - Hopefully did it well
Peer-Review (Done by Gary Chien)
Journal activities are explicitly and clearly related to course deliverables (4/4)
Entries are brief and to the point, while doing a good job of what task each day was spent on.
Deliverables are described and attributed in wiki (4/4)
Contributed to plenty of wiki pages and made a clear list of contributions in journal.
Report states total amount of time (3/4)
"Sanity Total" is a nice way to help keep track of hours! Would be nice to include hours at beginning of each entry, to make counting easier.
Total time is appropriate (3/4)
About 150 total hours expected for 15 weeks. However, results speak louder than specific number of hours reached!