CAGD ePortfolio

  The fourth sprint felt like it started a bit wonky because we needed to put out a build while there was not much to the game. The AI caused some weird problems, so we had to turn it off for this build. We did some playtests with a few MADT students and with Dan as well. Other than doing a playtest, our programmer was hard at work getting in certain features that the marketing team needed, as well as getting the aftershock forecasts to be more accurate. He added in a command in the dev console to be able to freely move the camera and also changed the notification system so that it’d work off the real life aftershock forecast update schedule. Notification System On the first Thursday of the sprint, two MADT students from the marketing team came over to interview us. To be honest, while I am technically the most equipped to answer questions out of our group, I didn’t really feel like I could really add too much. I expected a lot of hard questions, but for the most part, we were ...

  In the third sprint, we are mostly on track with the direction we’re going. Unfortunately, a lot of it is still just programming, so our programmer ends up doing the large bulk of the work. For the first half of the sprint, there was still a bit of uncertainty since we had a lot of trouble thinking up a name and we had been waiting several weeks for data from the USGS. Luckily we were able to get a large spreadsheet of the 2023 Turkiye earthquake sequence on Tuesday, so we should ideally be able to use it on the next sprint. The big things we were able to get done this sprint were the formula parser and getting the forecast to actually work properly. Also, while working on the earthquakes, our programmer noticed a visual issue with them, mainly that they all look the same regardless of magnitude. Most of the work we did isn’t necessarily anything visual, but they were very important nonetheless.   In the first half of the sprint, we continued the struggle with the title....