First of all, for my update on learning, check out my personal blogging site that has just been completely rebuilt (it may look empty).
De Bono time:
Here is a list of concepts that my mentor and I talked about last meeting:
logic of a computer
profit vs. everything else
Coincidently enough, during our conversation, which went really off-topic (shhh), we talked and discussed a lot
about the United Airline incident that happened recently. When I went back to listen to our conversation, I realized that it was the part during our talk in which we brought up the most alternatives! To start, my mentor suggested for us to look at this incident from another perspective.
The passenger that was violently dragged off was actually a terrorist under disguise. The FBI have been tracking him for days, but never found an opportunity to take him down without alerting the media or the public. So they told the flight attendant to basically pick this passenger when they are doing the draw. This way, they can get the job done, and the public or foreign agencies will never know of the secrets they can extract.
Another explanation for the event doesn’t necessarily praise United, but it claims its innocence:
These explanations for the event look at it from another perspective, and offer an alternative way of thinking about the event.
Anyways, back to my actual topic of alternatives, I had a lot of alternatives when considering my car design:
how will it work? (line following? obstacle avoiding? real time control? )
how should I write and organize the code?
using a lot of if statements?
finding a way of listing input that will direct me to a certain output?
use “def” makes the code more readable than not using it, but it is more work
comment makes the code more readable by humans and make me remember what everything does, but is a lot of work as well
if I don’t have time, I could just do one mode (line following + one ultrasonic)
if the motors don’t work well going at 70% power, I can just not do slower speeds
maybe create two different tracks for two different modes, if I am going to have that
Huff, spring break just passed and I haven’t even written this in advance… I need to stop procrastinating…
But anyways, I think it is week 11, but not too positive, and spring break sure is a time to do stuff. I posted two posts on my “diary” website, but yet again, my crappy server broke down and the website is not accessible. So I will just post some of the pictures I posted there here. These are for V1 of my car, built on Mar. 15, 17. If you are on a mobile device like the iPad, click on the images to view the caption (they’re pretty important). If you’re on PC, I don’t know if captions show, but there are captions on most of the photos.
So, after that, I did a few upgrades, fixed the motor that didn’t really work, and plugged all the Input Outputs! I realized that the Pi can never power the motor, on its own, to make it work as normal. So I basically added another power supply to the motors. This means I will have two battery packs on my car, one for Pi, one for the motors. This is V2.0.
In my meeting with my mentor, I started writing code the car. The first step is to set up the initial initialization, like assigning output to the motor’s pins (24-27). Then, I have to figure out a logic for the car. This includes a exclusive list of the things it will perform under one of the many conditions. So much work for me in the coming weeks…
De Bono Time:
The six hat conversation:
First, I would like to say that most of the time we are talking, we are just confirming our thoughts or proposing a solution that may well be the only one suitable, and we are only talking like 30% of the time in the 2 hours, so I will try to skip over some mumble jumble. OH, and also our conversation is in Chinese, so it is hard for me to translate it into English word for word. I will just say the overall message. Legend on bottom.
Me: Telling my mentor the different things I’ve added since he last saw photos of it. (1.0 to 2.0).
Also tell him of my logic diagram I am working on. Also tell him of my goal for the night, which is to find out if my diagram works, my car’s design works, my motors function, and some python coding if we have time.
Mentor(and me, butmostly him): Confirm what I said, suggest a new method of figuring out what the logic of the car is. Demonstrates the method and work out the car’s reactions to different input values when it is first starting. (put down on the ground and motors are 0) Everyone agrees that this method is a lot better to follow when writing a code. Ask me to list what the car should do in each situation (ex. right IR sensor detects black, nothing else). Discuss about the type of line & and thickness for IR sensor.
20 min. later.
Me: Discuss how to control the motors, and testing a test code to see if motors function.
test code didn’t work,
Mentor: tells me why code won’t work. Deletes, or comments out most of code that didn’t work.
looking up pwm (pulse width modulation or something, it makes the motors spin slower)
Mentor: (don’t know python, but know the usual syntax and logic of the language) Copies a LED code over to the motor, changing some values. It is meant to fade an LED back and forth. He thinks that it should work, because they are both outputs, and there really isn’t much difference between them.
didn’t work at first, but when the work percentage/duty cycle is higher (spin faster) it works. We tested that it can start moving at around 65% when it was stationary through a lot of trials.
50 min. later.
Mentor: Suggest a new code that don’t fade out, and allow us to call it up pretty quickly using the “def” function. We also discovered that it allows us to change the variables pretty quickly (time and duty cycle). Also suggests that I put comments on my code so I can remember what they do later.
Me: It also makes your code easier to read to other people so they can know what you are doing.
Me:commenting code is boring, basically you just label the code, but I feel like I will probably forget what this line means in like two days, so I should probably still label it.
me labeling code for 20 min.
Some other little things we discussed that I won’t document here, and our meeting is finished.
First of all, here are some updates on the overall progress of my project. I have basically finished all the learning portions of in-depth, and I will move on to constructing my final project. This doesn’t mean that I’m done learning, it means that I will progress from reading 80% of the time to reading 20% of the time. My final project has a lot of things where it could go wrong, and there are a lot of room for improvements and upgrades. So, I think from now on I will learn through doing.
My progress report is, or was, on my personal blog, but the server crashed while I was writing the report and my site, along with several of my dad’s sites went down. (I must have done something wrong, the WordPress sites could no longer be accessed) I have a copied-and-pasted version here, but all the images are gone. Sorry…
First of all, my mentor had a different idea about the state of the connection when a capacitor is charging and when it is fully charged. From my readings, I thought that while charging, a capacitor allow the flow of current, and when it is done charging, it will block all current, and it will “open” the circuit. (no current could pass through) Through listening, I saw a different perspective and saw that his reasoning are valid, while my perception of what happened could explain the results of an example circuit, his way of seeing things is more valid. In the end, we are both wrong, and we had a laugh about it. It was after my mentor tried to explain to me his views for 20 minutes, using diagrams and everything. He kept using words that I haven’t read about before, and he is sometimes saying things based on the assumption that I know some things, which I may or may not know. For example, the term “short-circuit” appeared in my readings once (I can’t memorize things that well, and it didn’t come to me), and he kept saying that, resulting in me not understanding the whole phrase he is saying. I tried to wait patiently, because I know everything will be written on my face, and asked a ton of clarifying questions. Finally, I got what he was saying, but we decided to search it up anyways. Turns out we’re both wrong! I also got some interesting facts by paying attention to the matters of interest that arose. For example, since some light bulbs use AC, which has voltage that goes up and down, like a wave, those light bulbs are actually flashing. We can’t see they are flashing because the AC frequency is very short. In the US I think it is 60 times per second. Finally, by paying attention to his use of words, like open circuits or using t0 to t1 to describe an event, I can communicate more professionally with others, and also make my words easier to understand for an experienced person.
How to ask questions:
Fishing questions and shooting questions, they are kind of like the surface/shallow and deep questions we learn in middle school. A shooting question has two results, you miss, or you hit the shot. It is very straight forward. A fishing question is like fishing, you throw in a bait, knowing that it will attract a range of fish (or questions), but you won’t know which fish you will catch, or whether you will even catch one. We ask these questions and differentiate between which question to ask all the time. As de Bono observed, we ask shooting questions when we suspect the answer is no, and when we have an idea what we are asking. If we have no clue of the answer, we ask a fishing question.
Just like de Bono observed, we ask for clarification and explanation more than anything else in our conversations. This is very true for my mentor and me, as I often need him to explain something in plainer English. I also asked a lot of questions when the ultrasonic sensor that we finished last time didn’t work this time, after being transported to a different place. I asked for the possibility of some things going wrong to try to cover all the possibilities (shooting questions), like the connection of resistors, the order of the resistors in the voltage divider, whether the GPIO pins we are connecting to are malfunctioning, etc. We changed the GPIO, the variable names in the code, downloaded a version of the code online that people made, and non of that worked. Finally, we realized that it was supposed to be connected to 5v, instead of 3.3v. This part is when I asked a multiple choices question, of which scenario have the greatest possibility of happening, and therefore which one we should check first. I think using the multiple choice question is great because it lets us examine all the options before making a decision.
I asked for an explanation of the meaning of “short circuit”, which I believed to be a circuit without resistors. But that
description didn’t fit in with the context that my mentor was talking about. He explained, using a diagram, that it means, basically, that there is little to no resistance between the two poles. It also means that, like in the diagram below, all points in the red line have a V of 0. That is because they are all connected to ground, and they cannot have a voltage, but suddenly drop to a 0 when it reaches ground, for no reason. Sorry if that makes no sense.
I hope you are still staying with me after 1000 words, but luckily, or not, this is the end.
Believe it or not, three weeks have passed since we did our last blog post! During these three weeks, what I found is that schedules are hard to follow. Everything going on, like homework and events that just pops up, seem to make me completely forget about my schedule. I had a meeting with my mentor last week, and it is when he asked me about what I did in the period between our meetings that I realized: I haven’t done a lot. Because of a miscommunication between my dad and I (I thought he said to keep a log), I started to record all my significant progress on a random website that I made with WordPress in the summer, so now you can go on there to see some of my progress, and I won’t document my progress in these posts anymore. (If that’s inconvenient Ms.Mulder just comment on it) The exact link is here, to my posts, but you can also type in tony.szmba.com or tonysun.win to go to the home page. (the .win one has some weird bugs)
For our journey to a beautiful mind, which we are currently trying to be interesting and know how to respond, here are my reports:
How to be interesting
Using the phrase “Now that’s interesting” is like the easiest thing to do so far. My mentor would often bring up points that I have never heard or thought of before. Like when we were talking about analog (-∞-∞) and digital (1 or 0) and resisters in circuits, my mentor pointed out (literally pointed) that those dimming light switches on my wall have a resister that can change in their resistance. So when I turn the light brighter, the dial makes the resistance smaller and when I turn the light dimmer, the dial will make the resistance bigger so there will be less voltage, etc. and there will be less light. I never thought of that before, so I said “The Phrase” and was then able to make other connections in using the resistor. I also tried to find interesting points in a lot of things, so basically everything that he said which I did not know, I commented and made connections to other things. Because I didn’t record my conversation, I can’t exactly tell you what I used “what ifs” for, but I remember that once when I asked about what would happen if a LED has received too high a voltage and whether stuff will catch on fire if there is more electricity than it is designed for.
How to respond:
Ah, asking for clarification is me every minute. For my conversation with my mentor, basically when I ask a question, my mentor would respond, and before he finishes, I would be bursting with another question. He would answer me again, but I would have another question by the time he finishes. This is also something I need to improve on, since I will have a question while my mentor is speaking, and as a result, I usually lose track of what he has to say, and sometimes I would even interrupt. I did supported some of the points that my mentor made and improved some of his points, but that is because I was searching on the internet the same time he is and I found a better way to assemble the ultrasonic sensor than the method he found. I guess that still counts as responding.
Anyways, that is all I have to say for now, it is getting late and I am really tired, probably because I got my shots today. So this is it for now…
PS: don’t forget to check my progress on tonysun.win
Two weeks have gone by since my first post, and it was just a blur. For the first two weeks, I was just planning to learn about the Raspberry Pi in general, like its hardware specifications, Linux (Raspbian on the Pi) and a bit of Linux command prompt. My main source of information was two books published by the Makezine, and I find them to be very insightful, current and accurate. The only bad thing is that it is going very fast and lacks explanation in some parts, and I have to read more than twice to understand a shell command in Linux, for example. I did encounter some obstacles, like finals that delayed my process. To admit it, I didn’t do as much as I planned to do, and I think it teaches me to consider in external factors when planning a schedule. Below is a visual I made that contains the basic facts I now know about the Raspberry Pi. Linux commands that I learned are not shown because I couldn’t find a way to display them.
My mentor (I only know his Chinese name, I forgot to ask for English name) and I have set a schedule to meet after church hours, as he goes to the same church as I am. He has given me his CRC last Sunday, but I had forgotten to hand it in. Our last formal discussion was the Sunday after my first in-depth post, so two weeks ago. It was focused on the outlook of my final project, and some difficulties that I might have achieving them. It was more of a fact based talk, rather than opinion based, so there wasn’t a lot of point we could agree, or disagree on. I had just read to chapter 2 in the book then, but I did read Ms. Mulder’s summery on her blog post.
How to Agree: Most of our discussion was in unison, like how we discussed the number of time I should spend on this topic, the ideas that he proposed to make my project work. There was one time when he mentioned a new point about how a car could sense and avoid incoming obstacles that really appealed to me, and its logic was better than my old algorithm. Something that I didn’t agree with entirely at first was that my mentor mentioned that the Python language is easy. The same thing was said by my dad after. But to a newbie like me, it was hard. It was like learning French from English is easier than knowing no language and starting to learn a new one, word by word. I recognized that when my mentor said that because he knows multiple languages and knowing the structure of languages, Python is easy to him. Another influencing factor is that it could be my own conception that is wrong. Everything is hard before you learn it. I appeared to me to be a sweeping generalization. So I agreed that Python is a relatively easy language compared to others (agree with part of statement), in the end, even though it still seemed hard for me.
How to Disagree: So for the example of Python is easy mentioned above, I disagreed with part of the statement and politely brought it up because of the experience different between my mentor and me, so I could only say, Python is a comparatively easy language to people who knows other languages. Besides that, I don’t think there was any other disagreements.
How to Differ: Now that I remember, one difference that we encountered was how the car should react when it senses an obstacle. I thought it should turn right, turn left, turn left and turn right again, so it would go back on track. But my mentor thought that it would be better for the car to stop and turn around to go back the way it came from. In the end, we reached an agreement that this is based on the road and the obstacles, and that it all depends on the outcomes and functions that we want the car to reach.