Mike Colonna

  • What you did

  • How long it took

  • What went wrong

  • The data used

  • Images/videos of different visualizations

  • Images/videos of data in Yurt and in the lab

Visualization #1

Data: cco-ascii.vtk (Neutron Star) and newjets-ascii.vtk (Fiducial Jets) from Data Types and Examples

Step 1 – Loading Data and Changing Appearance

Loading the .vtk datasets in Paraview was trivial – I simply loaded the files and they appeared in the viewer. I then tweaked some parameters to change the background color and the color of the models, so that each element stood in contrast to the others. This was also trivial.

Step 2 – Loading model into VR – VR Lab

Using one of the laptops in the VR lab, I followed the instructions for loading my dataset into VR. I clicked on Tools > Manage Plugins, and loaded the OpenVR plugin. When I clicked on 'Send to OpenVR', I received an error message telling me that the Vive had not been properly set up. The headset was connected to the laptop, but tracking was not enabled. Brandon and I spent the next few minutes debugging the situation.

After setting up tracking and sending to OpenVR again, Paraview became unresponsive and was unable to load the models into the Vive headset.

So, I moved to one of the larger computers. Transferring my files and opening Paraview there was trivial. I managed to run OpenVR and view my data in VR successfully there. I think the problems here were due to hardware limitations on the laptops, which may not be able to run Paraview and Vive at the same time.