-
Notifications
You must be signed in to change notification settings - Fork 1
Blog 2016 10 14 Fall
# Entry One
This week we were able to complete the problem statement and have it signed by the CS capstone group and Dr. Squires. Luckily we were able to keep our organization up but still managed to meet Kevin McGrath's requirements about keeping everything in a repository.
Our Monday weekly meetings have been going well. We have managed to recruit four students that have good coding experience if we need any extra help with research or testing. This is also where the Rocket Team as a whole agreed that having a server at the ground station communicate with the rocket would be best. All the data would be stored there. A web server would then collect the data and have a local Wi-Fi connection. We hope to have a good visualization included on the webpage of the rocket's whereabouts as well as some numerical data that would be crucial to finding it.
This next week we hope to have the new recruits continue the research we started so that we can get it done faster. We also need to communicate more with the ECE sub team to make sure that they can get the equipment we will need in order for this to happen.
The plans for the coming week are to:
- discuss a proposed architecture and scope for our project
- collect user stories from the rest of the rocketry team
Progress is going well. Our client, Dr. Squires, was very pleased with our problem statement. Currently, we are working with the avionics team to hammer out the details of the project.
Git is an amazing tool, but it does not excel in fast, remote, simultaneous collaboration. Compounding this with the large size of the rocketry team has made it difficult to produce the documentation in a timely manner.
Progress# This week we were able to finish our problem statement. Do to my previous plans I had the job of redoing our abstract from when we had another group read our abstract and read it. I also did some proofreading and had the ability to allow someone who knows nothing about computer science or rocketry read it. They were able to understand what we were trying to get a crossed with our problem statement. We got a general idea of what each team from the project wants from us software wise. What the teams needs and their wants. That way we have primary and secondary objectives.
Problems# I personally had some issues with some prior engagements. So I wasn't able to contribute as much until late Wednesday. That shouldn't happen again. My teammates were great to help with that. I had some issues with GitHub. I haven't had to use the command line ever. I am used to using source tree but I noticed I have more control with the command line. Keeping up with all the information of all the teams for the project is tough. They have information that can help us understand what is good for designing the software even if we aren't working directly with them. That's why it is good to know the verbiage of aerospace, rocketry, mechanical engineers and electrical engineers. I don't need to know everything but I should know at least what they are speaking so that I am not asking them to explain everything every time we have a conversation.
Plans# Next week we should meet a couple of more underclass men that couldn't make it to the meetings last week. Also we hope to get a little bit more precise information from each team. They should know more about the competition, materials, and so on that pertains to us. I personally will be joining the AIAA by the end of this week because they are one of our main sponsors plus they are helping me get my class one certification. Also meeting our TA for the first time next week.
OSU High-Altitude Rocket Team