Thursday, August 14

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.

Wednesday, August 13

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.

Tuesday, August 12th

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.

Friday, August 8

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.

Week’s Almost Through

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.

It’s Coming Together

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?

One Intern Down

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.

It’s Dead, Jim.

The fourth Friday was the big “Bring a friend” day. However, only four friends actually came. My friend, Adam, came at around 11 and helped Bob and I set up the volleyball net for the cookout, then I went inside to show him what I had been working on. Which leads me to the event of earlier in the morning. After working for a short period of time, the LCD touchscreen that we had interfaced with the Raspi had started to malfunction. It was showing only a white screen eternally, just as it had when we had first used it. I theorized that perhaps something had shorted due to the close proximity of the screen’s metal frame and the GPIO pins of the Raspi. Later, it was confirmed by Matt that this was the case, as the contact between the two components had caused the Raspi’s GPIO pins to burn out. However, we did not find this out until after I had begun uninstalling modules from the Pi in an attempt to return it to its state before I got my hands on it. We have now transferred the LCD to a new Raspi board, but it will have to be hooked up to the internet, it seems. At the very least, I can code on my computer and transfer the scripts in later.