They're installing acoustic panels in the eScience studio and today was supposed to be the "loud day", so we got moved to the CSE building for the day. The morning started off well with coffee and pastries provided to us around 9:30, and then we went around and gave project updates from the four different teams. It's true that we don't have much time to hear from the other groups what they're working on and how it's been going for them, so I think it will be helpful just to have these weekly updates where we can get a little insight into what all is happening with the other projects. Afterwards, the paratransit team and the sidewalks group met as one big group to try to set up some milestones or objectives for the coming two weeks. Our group's main goal is to have our optimization problem well defined by next Thursday and to finish the cost per boarding analysis before then, too.
For me, the day went by really fast today because for once we actually just had time to all work together in the same space as a team, and while we were working on different aspects of the project, it was incredibly helpful to be able to ask each other questions and get help from one another as soon as something came up. I was working on the cost per boarding analysis and coming up with a script that would give us the "ugly rides". I also took some time to go through some of the QCing script with Nick and I made sure he could understand what it was doing and what the syntax meant in R. There was a lot of back and forth with updating our workspace through git as everybody kept pushing new code, but at least for me I know my code still needs a lot better annotations. Also, using the R Studio server that Rohan set up was helpful because I can use it to try to run my UglyRides script once I create the right data file I'll need, but I won't have to keep remaking the data file.
For me, the day went by really fast today because for once we actually just had time to all work together in the same space as a team, and while we were working on different aspects of the project, it was incredibly helpful to be able to ask each other questions and get help from one another as soon as something came up. I was working on the cost per boarding analysis and coming up with a script that would give us the "ugly rides". I also took some time to go through some of the QCing script with Nick and I made sure he could understand what it was doing and what the syntax meant in R. There was a lot of back and forth with updating our workspace through git as everybody kept pushing new code, but at least for me I know my code still needs a lot better annotations. Also, using the R Studio server that Rohan set up was helpful because I can use it to try to run my UglyRides script once I create the right data file I'll need, but I won't have to keep remaking the data file.