Since the last post, most of my time has been spent attempting to solve various coding problems such as creating a user interface and its related challenges, as well as processing anaglyph videos. The videos have taken a back seat to the interface, now, as it is being more challenging than originally thought. Yijung has been a big help with the coding as has Kevin Kha, who is working on networking the two Raspi’s together. Kevin struck success just yesterday when he was able to successfully send signals and information between the two Raspberry Pi’s directly hooked into one another through an ethernet crossover cable.
As I type this post, however, one of the Raspberry Pi’s seems to have have generated its own problems regarding connecting to the Raspberry Pi network. Kevin and Matt are working on it while I attempt to do what I can, when I can, but… Anyway, expect another update soon. I need to get back to work.
Welcome back, true believers! I’m back at RIT as Joe Pow has hired Maddie, Rachel, and I for the summer. We are working with two new interns, Kevin and Yijung, and an incoming freshman who will be with us in Imaging Science , also named Kevin. Our task this summer is to build on our camera system from last year (pictures will be posted of that, I promise) and allow it to take anaglyph (3D) pictures and, hopefully, video.
This blog is beginning a little late, as we are currently on the intern’s second week and we already have some electronics soldered together, thanks to intern Kevin, and Yijung and I have created the basic code to take two pictures and merge the required color bands into an anaglyph picture. However, we DO have a lot of work ahead of us and plan to keep this blog updated as we go along.
This is our image processing code, written in Python using the Python Imaging Library, alongside an image that was processed using our code.
I forgot to mention that the past few days, we have also been rehearsing our presentation. The girls have been doing touch-ups as well based on feedback, and it’s starting to go well. This morning, all the intern groups were giving dry runs of their presentation, and we ended up leaving after ours because Bethany knew that Joe was coming in just a couple hours to see our presentation once more. Later on, after I had to take a bag and a half of lab equipment home, I was able to nail down the portion of the code that focused on the camera’s constants, and got the rotation set properly. Perfect.
In other news, Rachel, Maddie, and I ended up going to lunch late due to our presentation for Joe, and we had our own little reminiscences about our internship. We hope and plan to stay in touch, and I honestly hope that’ll go well. This internship has been one of the most enjoyable opportunities that was ever represented to me, and I sure hope that CIS will have something for me to perhaps help out with next summer and that I will have the opportunity to attend RIT after my final year of high school.
Today we decided to use the open source software. Quite a disappointing moment for me, but at least I still had a hand in the electronics. AKA, headed our electronics portion. Next step: modify the open source software so that the picture is right side up. This is quite a bit of code, so this may take a little while.
I apologize for these blog posts having gotten less entertaining. As the internship comes to a close, I find myself busier than ever.
So, today, I worked on code. All day. Pulled my hair out, grew it again, then pulled it out once more. Really not too much to say. Except that, if I can’t get it all functioning by tomorrow, we’re going to stick with the open source software I downloaded.
In actually good news, while I plugged away at the code, Matt, Rachel, and Maddie worked on assembling the camera. It works, now, with the open source software! Sure, we had to cut open a new hole for the charger and open up a lot of room with files and saws, plus our picture is currently upside down, but it works!
Monday, August 11
I came in earlier than needed today, reaching the lab at a normal time. However, due to the fact that I was up until 5 AM before going to sleep, I quickly fell asleep as I reached the lab. After my nap, I got to work. Coding. Researching. Code. Research. None of it seemed to want to work. So, by this point, I downloaded some open-source software for a project not unlike ours and attempted to learn from it. This learning will happen tomorrow.
After work, the CIS interns and the REU students took a field trip to the Mees Observatory in the Bristol Hills. Sadly, we did not get to see that many stars (the clouds were much too overbearing). Maybe better luck next time.
Today, a lot of research was done, attempting to get the code working. Pygame still refuses to read the mouse clicks when the preview from Picamera is up. When I can get it to listen to the mouse clicks, however, the preview still only briefly flashes, then the whole process quits. Much of my day was, as previously stated, trolling the internet attempting to find some solution. I ran into many roadblocks, but I feel as if I’m getting closer. The weekend is here, at least, and the Mees Observatory visit is on Monday, so that will be a fun trip.
Thursday, August 7.
Coding. Just coding. I am working on the camera code. It’s being frustrating. Same old story, really, when it comes to a large programming project. I’m currently attempting to get the code to register touchscreen inputs.
Just had an idea while writing this. The touchscreen, if I remember correctly from my initial tests with it, the touchscreen simply works as a mouse. When presses (at least on the desktop) it moves the mouse around. Possibilities arise.
Maddie is out again for the first half of today due to a surprise college visit she had to partake in. Our power switches came in today, as well as the pin headers. We were also able to power the Raspi through the pins on the touchscreen using a small DC generator. It was a very proud moment, because that was one of our biggest points we worried about. Now, all I really have to do is assemble the power supply portion (Woo! Soldering!) and finish the code. Now, if Pygame would actually work with me, that would be fantastic. … Eh, what’re you gonna do?
Maddie’s gone for the day. She’s off visiting Syracuse University today, so it’s just Rachel, Matt, and I. Today, I worked with Pygame and made one last ditch effort to get Kivy to work. Pygame is an interesting addition to Python and I feel like this is going to be a good time. In other news, Rachel and I took a small field trip over to the transportation offices so I could grab a parking pass for next week. Possibly the most painless process I have undergone over the course of this internship.