Last night we started getting everything setup for this semester. Unfortunately, due to our fearless leaders poor planning, we ended up moving stuff around the Engineering Building for about an hour before we gave up and went back to 4225. But alas, we have a plan. I’m going to order a new router for the lab so we should be able to connect the entire network back up in our lab. Other than that, we started working together to get source code downloaded and start making some plans for the near future. Sounds like we’ll have to spend a little time getting caught up with Java, and maybe a brief lesson in SQL, and we should be off and running. By my count, we’re currently 7 members strong. Our meetings will be on Tuesday evenings at 6:30pm in 4225SC. So come one, come all, we’re gonna program like there is no tomorrow. See you all next week.
No commentsGeneral
When I saw this, I thought of the USARSim team. Google has open-sourced code named “Protocol Buffers” , a system for serializing structured data for use in communicaitons protocols, and data storage.
Protocol buffers are a flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. You can even update your data structure without breaking deployed programs that are compiled against the “old” format.
Google Open Source Blog: Protocol Buffers: Google’s Data Interchange Format
I don’t know if this would be helpful in storing and transmitting robot info over the network, but thought I’d post it here to see if anyone else thought it was interesting.
Tags: data, encoding, storage, google
No commentsCommunication, Database
Katie was working diligently on OpenGL code before she left and I saw that she uploaded some modified code. Rather than lose it, I decided to branch off until she gets back so she can merge later. If you are looking for the running code, it’s now contained in the branch/USARSim2008 folder in the repository and that will be what we use until we merge.
No commentsGeneral
Had our first meeting in a month and the first item on the agenda was to determine where we left off. After an hour of getting the lab setup again (plugging in cables, turning on computers, network setup, and reformat & software re-installed on 2 computers) we were finally able to play around with our code. And surprisingly, it’s looking good. After a few modifications, we were able to start the GUI and display up to date laserdata from a single robot while maintaining communication between them. Pretty cool stuff. Read the rest of this entry…
2 commentsGeneral