Posted on

Anthony’s Report 3/25

I have been able to get access to the phone devices so that I could start testing and using the actual Unity interface for testing. After taking some times trying to figure out how to get the phones to work, with unity, I was able to start trying to figure out how to code our game in unity. Most of this week was getting accustomed to the new interface, and also some small implementations as well.

In terms of progress, we are still a little bit more behind than we would have liked to be currently in the project, but not so much so that it is an issue for us at the moment. Extra time will need to be taken to try to catch up, and make sure we do not get more behind than we currently are.

This next week I hope to get a majority of the base of the game created, so that once it is time for our demo, we will have something to show.

Posted on

Joseph’s Status Report for 3/25

I am still in the process of coding the line rendering algorithm, so that is what I’ve been working on for the week. Besides that, I helped Anthony set-up the Android phones that were received and push the project build to the phone successfully. I also made a team Unity account so we can share paid Unity packages that are downloaded. I’ve tested that this works, having downloaded and imported the Uduino packages into the project and pushed them to Github.

This week was pretty busy for me due to all the preparation for Greek Sing happening today, so I didn’t manage to get as much done code-wise as I hoped. This means I am behind schedule, but I am still hopeful in getting a mostly functional algorithm by the Interim deadline.

Posted on

Team’s Status Report 03/25

We were finally able to purchase the Uduino software package with help from ECE purchasing. We also finally were able to obtain our additional Android phones, one borrowed and one purchased, for the purposes of testing.

Posted on

Sophia’s Status Report 03/25

This week was dedicated to our ethics discussions. It was a useful experience as it definitely helped open my eyes and see some ethical considerations we hadn’t thought of before. In terms of more technical work, I spent some time coding up our IMU script. I have settled on using the wrapper functions rather than tinkering with the raw data as the raw data is formatted in a way that parsing through it manually myself will introduce a bunch of unnecessary overhead and make it difficult to hit our proposed latency goals. I have been struggling a little bit to get the rotation vector working properly since all provided angles are positive. It has then been difficult to differentiate a tilt from the left versus a tilt from the right. Its unclear if this will cause future issues for us when it comes to calculating line position so I want to debug this as thoroughly as possible before reaching that point. I have also finally been able to purchase Uduino after help from the ECE purchasing. I have not yet tested how well Uduino works with our NodeMCU board.

I am still slightly behind schedule because by now I should have the double integration script working. However, the next few weeks have been allotted for debugging and fine-turning, which is technically what I am working on right now. I will be working on this a little bit over the weekend to hopefully figure out this little bump and be right on schedule.

Next week will be spent fine tuning our IMU script and trying to test its integration with Uduino to send data over to our Android devices.

Posted on

Sophia’s Status Report 03/18

This week, I spent some time working on the integration of the IMU data. It was a little bit more finicky than I thought especially because it took a while to understand the sensor_event_type and its different attributes. I also experimented with not using the Arduino wrapper and directly pulling out the raw data. However, the raw data was extremely confusing to use and work with so I have decided to use the wrapper function. I have also worked on ordering the Uduino package. However, due to issues with purchasing software packages, the ordering for it has been delayed and moved higher up into administration.

I was out of town traveling so I did not finish everything I wanted to do before I left. Due to this, I am also a little bit behind on schedule. This just means, however, that I will need to do some more work over the week end to compensate for this.

Next week I hope that double integration script will be finalized so I can do some tests, debug, and fine tune it then.

Posted on

Team Status Report 3/18

Currently, our group has the same risks as before in prior weeks. We still would potentially have issues if integration were to go poorly. At the moment we are simply trying to make steady progress, and hope to begin integration as soon as possible just in case there are any roadblocks. Due to recent updates to our design though, this should be mitigated since we have started using packages that will implement some integration of components a little more smoothly then in earlier versions.

From the last week no changes have been made to our current design

No updates or changes have occurred since our last update

Currently our progress is steady and there are no major updates from last weeks status report.

Posted on

Anthony’s Status Report 3/18

This week I mostly worked on continuing to understand how unity works, by messing with some of the packages in my own projects.  Our group was able to get the extra android phones that were needed at the end part of this week. This will allow me to soon start implementing the actual game for our product, since phones are required in order to test and run the VR packages that we need to use to create our game. I was able to verify that the phones are working , but not actually able to start using it to develop anything for our game this week. I also spent some time working on the ethics assignment for the week as well, which took more time than anticipated.

Currently in terms of progress, I am still slightly behind like I was prior, but did not get any more ahead or behind than our prior week. In general progress is steady, and should be able to catch up once I start implementing games.

Next week, I will be able to get started on creating on creating the game and hopefully helping my partners with whatever else they need as well.

Posted on

Joseph’s Status Report for 3/18

This week I started writing out the code for the line calculation algorithm. The lines are yet to actually be rendered and tested with dummy data, but the basic code structure and pipeline have been written out. In addition to this, I also read and worked on the ethics assignment and readings that we were assigned to do. Schedule-wise, I am still a bit behind, but once the line algorithm has been written out and tested I should be back on schedule. I hope to finish up the line calculation and rendering algorithm in the following week and test it out for bugs.

Posted on

Joseph’s Status Report 3/04

This week I spent time solidifying how exactly the line calculation algorithm will be designed, codewise. Also, I decided which unity gameobjects would be best used in order to render the lines, that being the line renderer object over the trail renderer object. This is due to the line renderer working better with the locational data points we will obtain from the hardware, as well as better integration with the cloud anchor objects necessary to make the drawings able to be seen on multiple devices. Other than that, the rest of the time was spent working on the Design Report, which took quite a bit of time.

Unfortunately, I was hindered this week and spring break by a medical issue that cropped up Monday the 27th, that being extremely bad stomach pain that came on whenever and always lasted for hours, rendering me incapable of anything. I went to the ER Saturday the 4th when it wouldn’t get better and instead got worse, in which they didn’t find anything obvious and life-threatening luckily, though also weren’t exactly sure what it was.

(medical note attached)

Luckily, after some follow-up visits, time and medicine I seem to finally be getting better as of today, so I’m hopeful to get more done this following week, which would involve me working towards a functional line rendering script with test inputs. I am somewhat behind schedule due to this issue, as I should’ve started actually coding the line algorithm by this point, but from previous research on the best ways to implement this, I am confident I can code a functional line renderer within our set timeline.

Posted on

Anthony’s Status Report 03/04

For this last week, most of my time ended up being spent working on our groups research Design Report. Although it was expected that this task would be simple it ended up taking a lot more time than anyone in our group had anticipated. Also since I still do not have access to an Android device, which would be required to actually perform testing and programming with our AR Foundation Software, I have not been able to start working on coding content specific with the AR packages. I instead continued to do light research on how the packages will work and will be integrated. As mentioned from last week, I was able to start trying to figure out how to create the game scenes themselves, and how they will potentially be integrated on the phone app with AR foundation. I was not able to get started on the game code itself, rather sample projects that will hopefully allow us to simply integrate easily once all resources have been ordered.

My schedule is still a little behind, since We expected to get started on creating the game itself at this time, but it does not currently set us back to much given some buffer we also have for the project as well. Catching up will simply require taking a bit more time on weekends to work on developing the code, and figuring out how to integrate.

Next week we will hopefully the all our resources in order to allow everyone in the group to have the ability to integrate code with AR Foundation. At this point I also expect to start actually starting and getting through a good portion of app creation itself, assuming no other tasks get in the way.