Project 2 Plan

1) Finish up the rest of my first project + Import NEW openspace data into YURT

During my project 1 presentation I mentioned that I got stuck on dependency errors with Openspace

Summary: I would like to address the errors and determine if there is an easier way to streamline the Openspace -> MinVR process. By streamlining this process uploading new data (like Anessa's data) into a YURT port will be a practical solution for visualizing new data pertaining  to the cosmos in the YURT

Deliverables: Document entire process of getting Openspace working with MinVR, Document MinVR port working with YURT, then document how to upload new data into Openspace along with this process (This will involve collaboration with Anessa)

Software: Openspace, OpenVR, MinVR

Data: TLE (Two line element set/ This is the data format Openspace uses)

Resources: Openspace wiki, Openspace slack channel, Openspace git repo, MinVR git repo

Class Activities: 

Openspace to MinVR tutorial - This will be a tutorial where everyone can work on their personal machines and build Openspace to MinVR in class.

Uploading new data into Openspace - Class activity where I provide the course with data examples that can be uploaded to openspace and they choose what data they want ported then I port them for the entire class to visualize

Documentation review - Course review over documentation of errors and have the class look for holes in documentation. This can benefit the entire class in knowing how to write exceptional documentation of software or data. 

Schedule: 

4/02 - Document/Report known bugs and how to resolve them when building to MinVR

4/07 - Document the most current method of porting Openspace to MinVR

4/09 - Try porting to YURT remotely 

4/14 - Document Porting to YURT

4/16 - Port new data into Openspace/MinVR port (Collaboration with Anessa) most likely

4/21 - Curate potential new data for class activity

4/23 - Class activity

project 2 eval by David 3/3120

Very exciting project!  One concern I have is that debugging may be challenging and require input from outside.  As much as possible, try to make that happen as early as possible so that there is time to for outsiders to be responsive.  Success with this port will be a big win!  As a contingency, I might prioritize some of the new-data support in order to get the port to work.  Adding data should be independent of yurt functionality.  It would be great to have, but not super useful if the yurt functionality doesn't work...

Project 2 Evaluation by Ross 03/31/20

Concrete and well written proposal! As David mentioned, debugging the YURT remotely will likely add an extra layer of challenge to the porting process, so that is something to be aware of. You might consider allocating more of your schedule to porting rather than documentation or adding new data, as the former will likely take much more time than the latter. Good work and I'm excited to see the results!