Monday, December 10, 2012

Solidworks Spitfire

A few weeks ago I was tasked with learning the basics of Solidworks (a 3-D design program) by designing a key chain.  After some hours of tutorials, help from other Mechanical Engineering students, and playing around, my partner, Christian O'Bryan, and I designed this model of the Spitfire, a British WWII fighter.  Sadly, it is not a terribly good model, but we were pleased that it looked like an airplane.  





As part of the project, we printed our designs using a 3-D printer. 




 Reflection:

  1. Too Big 
    • While the airplane was a great size for a toy airplane (roughly 3.5 in wingspan) it was too large to be a convenient key-chain. 
      • Note: we made it this big because we wanted our wings (our weakest part) to have as much material as possible to decrease weakness. 
    • For the future I need to make sure the dimensions of my product fit with its intended use.
  2. Some Parts Too Thin to Print
    • As you may be able to see from the pictures, the wings on the airplane are rough on the trailing edge.  This is because the wings are so thin at that point that the printer was unable to print them well.  
    • For the future I need to make sure (if I am printing) that none of my parts are too thin to print properly.  While I don't know what the threshold for too-thin-to-print is, this project has given me an better idea for what it is.
  3. For Better Airplane Next Time
    • Next time I would love to model a Piper Lance as it has two major improvements over this model
      1. Square tipped wings so the wings are strong all the way to the tips.
      2. More compact airplane so it would be more suitable as a key-chain.

After this project was done, I was able to put my new knowledge to work with our next project, i.e. designing a Thermal Mug.  Learning from my last experience, I was able to design this Solidworks model in a little over an hour.  







Friday, December 7, 2012

Designing a Waxless Ski

       The following pictures are of my Math Model and Experiment Design for measuring the coefficient of kinetic friction of a ski. 









Thursday, December 6, 2012




Learning according to the Learning Curriculum

Dr. Elger’s Learning Curriculum defines learning as, “the process of becoming better at something that is useful.” The curriculum explains that learning requires certain things: (1) that the thing being learned is useful, (2) that improvement is occurring, and (3) that the learner is engaged in learning.

Recommendation for Improving Definition
Although, the definition displayed in the Learning Curriculum is wonderfully short and to-the-point, I would highly recommend adding the word “active” before “process”, making the definition, “the active process of becoming better at something that is useful.” Although this may seem like an insignificant change, it makes a large difference because learning is an active process and not a passive one. I have tried numerous different ways of learning things, even going so far as to try the learn-by-osmosis-with-a-book-under-the-pillow trick (it didn't work), and one thing that has been apparent to me over and over again (especially right after trying to sleep with a book under my pillow) is that learning is active. There is no osmosis-learning. There is no passive learning. Even babies trying to learn to walk and talk do so because they really want to “come to mommy” and because they want to mommy to understand what they need. They are active in becoming better at something useful. This is supported by the Learning Curriculum itself when it points out that engagement, i.e. actions of reading, listening, practicing, making mistakes and fixing them, etc., is a major part of learning. Thus, putting the word “active” into the Learning Curriculum’s definition of learning, would improve the clarity and fullness of the definition.


Learning and Competent Professionals

The main reason why competent professionals are really good at learning to learn is because they have made a conscious decision to be a learner. Being an active process, learning requires a mindful commitment on the part of the learner before that person can really learn and become competent. Being good at learning is relevant to being a competent professional in a number of ways. According to the Learning Curriculum, being competent means one has “the knowledge, skills, and attitudes to do something successfully”. Most of us, when we have done something successfully (e.g. played a hard piece on the violin, used parry counter-six riposte in fencing, started a fire with flint and steel, etc), think that we have learned that ‘thing’ and are competent in it. This idea, then, of needing to be good at learning to learn in order to be a competent professional might seem foreign to us, since often we think that if we are “competent” we have already learned what we needed to learn. When we really think about it, however, we realize that we can all learned how to do things better. We can always learn how to play the hard violin piece better (even Itzhak Perlman isn't perfect), become more effective with parry counter-six riposte, and start fires with flint and steel in worse conditions. This is why being good at learning is so relevant to being a competent professional; if a person is constantly working to get better and better or they will truly be competent.


Getting and Education According to ABET

According to ABET (Accreditation Board for Engineering and Technology), an engineer who really has an education excels in a list of twelve “competencies”. These competencies are as follows (these are based on Dr. Elger’s notes, which are his “translation” of the original ABET language into a more user-friendly language):

1. I get my knowledge down (i.e. know my stuff)

2. I build math models and know how to use them to solve real-world problems

3. I practice experiment design and use it to get valid data.

4. I design successful products/systems in their ability to do a task and in their marketability (i.e. successful in the marketplace).

5. I am a real team-player.

6. I can take a vague, complex, mixed-up problem and clarify, organize, and crack it.

7. I behave in a professional and ethical manner.

8. I am an effective communicator

9. I am able to connect and apply my solutions to the real world.

10. I learn and grow on my own without needing others to push me, and I have fun doing it.

11. I am knowledgeable on current societal issues and incorporate them into my work.

12. I use modern technologies and engineering techniques.


Getting an Education According to Me 

Education is an extremely broad term that can be applied to anything from pig farming to neural surgery. In all of these areas education is required in order to be able to do things successfully in that field (i.e. be competent). A pig farmer must be educated in pigs in order to be able to run a healthy and efficient farm. Similarly, a neural surgeon must also be well educated in order to perform successful operations. So how does one define what “getting and education” means? It is apparent that it must require learning how to do the basics in that field (e.g. the farmer must learn what things are healthy for pigs, when to butcher, etc), but it must also have to do with providing something for others (e.g. meat from the pig farmer, health from the neural surgeon). Additionally, the person must be able to learn without being pushed and have basic life skills (i.e. problem solving, knowledge construction, etc). Thus, I would define “getting an education” to be the process of acquiring the information and skills necessary to be successful in one’s field, provide useful products/services, and to learn how to learn. This definition is far from perfect, but it is a start.

Simple Way to Measure Getting and Education 
From what I have seen, a simple way to tell if you are really getting an education or not, is to try to apply your “education” and solve real-world problems.

What I Want Out of My Education
A fear that I had coming into college was that, in the end, my degree would be just a piece of paper, that I would not really come out knowing how to engineer things. Sadly, my first few semesters did not help this fear. I learned calculus, some physics, and chemistry, and yet I didn't know how to apply it. My older brother, who has a liberal arts degree, is much more of an engineer than I am, always thinking up new designs for things and researching how to build them and make things better. He really knows how to learn. He would share his ideas with me, and I, even though I have a higher “education” in mathematics and science than he has, would feel like I was talking to an engineering professor. One thing that I want from my education is to be able to apply what I have learned (i.e. engineering knowledge, math models, experiment design, life skills, etc.) to real world problems like my brother does. I want to have an “education” like his.


Neuroplasticity

Neuroplasticity is the brains ability to change due to experiences, in other words, the biological process of the brain “learning”. Apparently, when learning is happening, dendrites (connection structures on the neurons on the brain) grow and make more connections with other dendrites. The more experiences a person undergoes the more the growth of the dendrites and the greater the learning. That is why being active in learning (applying things, repetition, putting the time in, etc) is so important. It is part of a biological process. In my own experience, I have found that I can tell how much I am learning something simply by how I look at the rest of the world. For example, this semester in school I am taking two classes that deal heavily with analyzing the forces on objects (one dealing with objects in motion and the other with stationary objects). It seemed strange to me at first, but I started seeing the force of friction everywhere; in cars, on bicycles, coffee cups, books, gravel, frying pans, etc… What I think is happening, is that, having spent hours learning these concepts (e.g. friction), the dendrites in my brain have grown and made more connections, causing me to see more connections in the world around me.


Carol Dweck’s Mindset Theory 

Carol Dweck, a Stanford researcher, has proposed a Mindset Theory in which she concludes that there are two basic types of mindsets that people can have: a fixed mindset or a growth mindset. Accordingly, there are some behaviors that characterize people, indicating which mindset they have. People with a fixed mindset (the larger group) put a high premium on “looking good”. Their main goals are to get good grades, have high status, own nice stuff, have lots of money, etc… Hence, they tend to only do things they know they can do it, or, if they give up on something, they tend to blame it on talent, i.e. “I am just not talented in that area”. Because their focus in on outward appearance, they easily get jealous of others who do better than them. Contrastingly, a much smaller percentage of people have the growth mindset. These people tend to have a much greater motivation to get good at things, don’t mind looking like beginners, consider “failure” part of the learning process, and actually seek out people who are better at something than they are in order to learn from them. In short, the fixed mindset put others in charge of your actions (worried about what others think) where the growth mindset puts you in charge of your actions (worried about what is the right thing to do).

Which Mindset Used by Greats?
The growth mindset is held by many of the most successful men and women in the world. The Wright brothers weren't worried about what others thought of them. Instead, they used their mistakes to grow, and, in the end, they became the men who invented human powered flight! Thomas Edison, another man with the growth mindset, once said, “Results! Why man, I have gotten lots of results. I know several thousand things that won’t work.”


My Explanation of the “Beliefs-to-Results Chain” (BRC) 

The Beliefs-to-Results Chain (B.R.C.) is an interesting (and thought-provoking) idea. The chain almost models a simple function (i.e. I put in certain beliefs and get certain results out) with one significant exception: my results are dependent not only on my beliefs but also on my actions. The chain is as follows: Beliefs ==> Thoughts ==> Emotions ==> Actions ==> Results. The idea is that my results are based off of my actions, which are based off of my emotions, which are based off of my thoughts, which come from my beliefs. This “hierarchy” effect means that in order to change my results I need to change my beliefs. An interesting thing to note in this chain is that, while thoughts, emotions, actions, and results are all dependent on my beliefs, my actions are also dependent on my skills. In other words, my end results are not only affected by my beliefs, but also my skills.

Competent Professionals and BRC
Competent professionals can use this beliefs-to-results chain to improve their results and have more fun, by constantly analyzing their beliefs in light of this chain. For example, if a professional is not getting the results he wants from a meeting, he should ask himself questions to find out what results he was looking for and use that to find out why he wanted those results (his beliefs). Knowing his beliefs, he can then analyze them to see if they are correct, because it is possible that his result were right and his beliefs wrong. Changing his beliefs may give him a breakthrough and allow him to see the real way to solve the problem, etc. When this happens, not only does it help solve the problem quicker for the professional, but it gives him more enjoyment too. It is a blast when you “stuff” works!


Anders Ericcson’s Theory of Deliberate Practice 

Through many years of violin practice, something that was always drilled into me was you don’t learn a piece well by seeing how fast you can play it. What allowed you to learn a piece well was how correctly you played it. Since the best way to play it correctly was to play it slowly over and over, it became apparent that in order to learn a piece well, I would have to dedicate hours of practice playing each part over and over until it became “second nature”. This illustrates the fact that the more we practice fundamentals (correctly), the more they become embedded into our brain and the better we are able to do them. How are we to know if we are practicing well, though? The best way is to have someone who is really good at what you are trying to learn (e.g. superb violinist), have them show you the correct way to do it, and then come back to them and show them how you are doing it to make sure you are doing it right and for corrections. In visual form, deliberate practice looks like this:


Figure out how pros do ‘it” (e.g. play the violin) ==>   Practice   ==>   Get feedback (from peers, pros, etc)

Competent Professionals and Deliberate Practice 
Competent professional might use this process any number of ways to help themselves or their teams. Since competent professionals are always working on getting better at things, it is only natural that they would find others who are better in a specific way than they are (or their team is) and see what it is that those other people do to be so successful. After find out what it is, they would practice it; following up their practice with getting feedback in order grow. This is a general overview of deliberate practice.















Friday, November 30, 2012

Learning Project Management

Why do I want to learn Project Management?
There is no way I can escape projects in my life (even making dinner is a project of sorts) so I might just as well learn how to do projects well. The upside of this is that I will get better results in all areas of my life (yes, even cooking). I will be able to address things quicker, smarter, with less procrastination, and I will be able to get things done on time with better results (can't beat that). My ability to practice project management well will give me less stress, more fun, and more confidence.

Knowledge Construction
Here are the main ideas of project management:
  1. Start with a need or desire for something (to have or to be done)
  2. Create diamond to decide on goal for project (10 minutes)
    • Note: Goals have to be 3 things
      1. Extremely motivating
      2. Challenging but attainable
      3. Well-defined; measurable
  3. Using a diamond, quickly "decompose" project into Tasks (just enough Tasks to get started). (10 minutes)
    • Note: Each Task must
      1. Have a goal
      2. Take 15-60 minutes to accomplish
  4. Each Task has an Owner, and the load is balanced among members.
  5. Complete Tasks
  6. Meet regularly to
    1. Keep accountable on Tasks
    2. Solve problems
    3. Revise Tasks list (Iterate)
    4. Do SII's (Strength, Improvement, Insight)
At the end, Project Goals are hit, lessons have been learned, and documentation has been recorded.

Application
With this Knowledge Construction on how to tackle projects, I have been trying to apply project management in my every-day-life. I will illustrate my application of project management with an example from the school/professional area of my life (if have time I hope to post an additional example from the more personal area of my life).

Mechanical Engineering Project:
Applying project management in my current Mechanical Engineering project has been fairly straightforward, though difficult and in need of improvement. Our team has worked to have frequent meetings to keep each member accountable, we have used diamonds to define our goals, tasks, and to help with problem solving, and we have been careful to make sure that each task has an owner(s) and that the load is fairly balanced between members. Understandably, we have had to do a lot of iteration, even to the extent of changing our initial product idea. 
Strengths
Throughout this project, our team is done some things well:
    • We meet frequently for short meetings.
      • We try to meet as often as once a day during the school week. This allowed us to keep close tabs on where we were and keep each member accountable.
    • We assign owners for every task.
      • Every team member was great in volunteering for different tasks (I think it is a good indicator that the tasks are broken down well when no one is too scared to take them on). Giving each task an owner is extremely beneficial in that it creates fantastic accountability and the tasks seem to get done faster.
    • We have made sure load is balanced among members.
      • Thankfully for this project, balancing tour team has done a great job of balancing the task among the members (this is aided, I think, by the fact that with all of the tasks to be done written down and assigned owners, it is a breeze to assess how the work load is balanced). This lessens slacking, improves learning, and helps everyone have more fun.
Improvements
We have lots of areas we can improve in:
    • Use more diamonds
      • We need to use diamonds as often as possible (we can only get better with practice). Diamonds are useful whenever ideas need generating, whether that's brainstorming the tasks to be done or figuring out what a good customer segment is, so we need to use them whenever we need ideas in a meeting. In the long run, this will give us more ingenuity, faster idea acquisition, and better ideas.
    • Do more SII's as a team
      • Doing SII's as a team will helps us grow immensely. We will be able to grow closer as a team, be more efficient, understand our strengths and weaknesses better, and have more fun. To do this we need to specifically set aside time during a project meeting to do an SII; at least one SII per project should be done (three or four would be better).
Here are a couple of pictures of my logbook.  They are notes of our meetings, and it might be worth noting the iteration that took place.  We started with a certain goal and product in mind, and after several meetings and discussions (and iterations), we had a different product and tasks.  Our project changed a lot.  





This picture is of my logbook right after deciding to switch from our first product (inventory counter) to our second product (power meter for bicycles).

(Part of my learning project management is taking extremely useful notes and documenting better.  As you can see, right now it is far from stellar.)

Lessons Learned
         The three most important things I have learned about project management deal with the importance of diamonds, tasks, and having regular meetings. 
         Diamonds are crucial in project management as an efficient way to get good ideas (i.e. for problem solving, task generating, etc).  Our tendency is to pick the first idea that pops into our heads; however, if we use diamonds to generate as many ideas an we possibly can, we get better ones in the end, making diamonds an important part of project management.
         I also learned about the necessity of breaking a project into well-defined tasks and giving each of those tasks an owner.  When we tried this out in our project meetings, the results were glorious.  Everyone knew exactly what they were doing and when they had to have their task done, so things got done quicker; and, for some reason, people helped each other out more, too.
         Lastly, having regular meetings helped our project management immensely.  It allowed us to have shorter meetings while still going over the necessary "stuff".  Additionally, it helped us get to know our team members better (an immeasurable bonus when you are trying to work together as a team).

       
        The three most important things I learned about the Learning Cycle is that: 1) not everyone learns the same way, 2) application is super important, 3) iteration is super important.
  • Not everyone learns the same way
    • As the Kolb learning cycle shows, everyone learns things a little bit differently, which is exciting to me because it helps me understand my team members better (as well as others in general). 
  • Application is super important
    • This is especially important to me because I know that unless I actually apply something, I am useless at remembering it for the future.
  • Iteration is super important
    • Although I very much dislike this part of the learning cycle, I understand its importance, since it is better to do something a number of times quickly, than to try to get it right the first time (much more stress).  This is definitely something that will take me a while to get.

Sunday, November 25, 2012

Arduino Challenge Problem

Problem Statement


Make a servo rotate 180 degrees in one direction, then pause for half of a second and rotate back, pausing another half of a second then repeating.  At close to the 0 degree position (I chose the 1 degree position), a red light should turn on, and at the 180 degree position, a green light should turn on.

Key Facts
  • if commands are important for making lights turn on at specific points
  • for the servo wire, the orange connects to your digital control pin, the red connects to the +5 volts pin, the brown connects to the ground
  • be wary of special servo functions
Solution

Hardware




Code

#include <Servo.h> 
 
Servo myservo;  // create servo object to control a servo 
                // a maximum of eight servo objects can be created 
 
int pos = 0;    // variable to store the servo position 
 
void setup() 
  pinMode(13, OUTPUT);
  pinMode(11, OUTPUT);
  myservo.attach(9);  // attaches the servo on pin 9 to the servo object 
 
 
void loop() 
  if (pos = 1)                  // when servo is at 1 degree an led on pin 11 turns on 
{
  digitalWrite(11, HIGH);
  delay(500);
  digitalWrite(11, LOW);
}
  for(pos = 0; pos < 180; pos += 1)  // goes from 0 degrees to 180 degrees 
  {                                  // in steps of 1 degree 
    myservo.write(pos);              // tell servo to go to position in variable 'pos' 
    delay(15);                       // waits 15ms for the servo to reach the position 
  } 
  if (pos = 180)                    // when servo at 180 degrees, led on pin 13 turns on
  { 
 
  digitalWrite(13, HIGH);
delay(500);
  digitalWrite(13, LOW);
  }
  
  for(pos = 180; pos>=1; pos-=1)     // goes from 180 degrees to 0 degrees 
  {                                
    myservo.write(pos);              // tell servo to go to position in variable 'pos' 
    delay(15);                       // waits 15ms for the servo to reach the position 
  } 
  

Problem Documentation

Author:  Austin Tanner 
(servo sketch primarily based off of "Sweep" by BARRAGAN <http://barraganstudio.com>)
Date Created:  11/25/2012




Wednesday, November 14, 2012

Growing My Performance in Collaboration




Defensive Reasoning

Defensive Reasoning is the “fight or flight” mode that the brain enters when a person is feeling judged or criticized, or even when they are simply not succeeding at their current task.  This often causes people to respond by becoming angry or defensive, and when their defensiveness or anger is pointed out, they often deny it.  Another reaction a person might have when in defensive reasoning “mode” is that, although they might not get angry or defensive, they may start blaming the situation or say something like, “I am just not cut out to be a swimmer”.  This is a problem because when a person enters this mode of thinking they stop learning effectively.  Their brain releases chemicals that shut down their “higher order of thinking”, effectively causing that person to stagnate and stop learning.  They have not yet leaned how to separate perceived criticism, judgment, failure, etc, from data that they can use to help them grow.  To overcome this problem, a person should start by recognizing when their brain enters the “defensive reasoning” mode.  Once the person recognizes defensive reasoning, they should accept the emotions that come from it and let them pass.  Ultimately, if a person is able to apply Critical Thinking to a situation and then use the SII method to improve his results, he will be able to avoid defensive reasoning.

The SII Process
The SII process is a three-step process:
1. Identify 2-3 of my strengths.
    a.    Name action
    b.    Explain how I did action
    c.    Explain why it benefited me
2. Identify 1-2 Improvements
    a.    Name action I will take in the future
    b.    Explain how I will do the action
    c.    Explain why it will benefit me
3. Identify 1-2 Insights
In this process, strength is considered a skill that I used that benefited me in what I just accomplished, an improvement is a skill that I will use in the future to benefit me, and an insight the light bulb that went on (i.e. new knowledge that I finally got).

My SII on Collaboration

Step 1.  Strengths > My top 2 strengths in Collaboration

#1 Tried to cut down on my criticism.
Name – cut back on criticism
How – Reminded myself that every idea is worth considering
Why – I have a natural instinct to always want to go with my idea, even though it is probably (most likely) not the best idea on the table.  My fellow team members are all geniuses and have REALLY great ideas, so it is to my benefit to listen to them.

#2 Made sure we are clear about duties between meetings.
Name – clear communication about duties between meetings
How – at the end of the meeting, wrapped up by re-clarifying duties and having each member state what they need to have accomplished before the next meeting.
Why – this improves team efficiency, shortens meeting times, and ensures that each member is doing their share of the work.

Step 2.  Improvements > Top improvement

#1 Cut back on how much I talk during meetings.
Name – Cut back on my talking during meetings.
How – Focus on tasks at hand, and follow an agenda so as not to get distracted.
Why – Improves team efficiency, doesn’t waste others’ time, keeps me from looking like a fool.

Step 3. Insight > Insight

#1 When I am in a team setting (or anywhere for that matter), I find that I often get into defensive reasoning and try to defend my ideas, even though I know that the other person is right and that my idea is wrong.  Thus, I am finally starting to understand the full effect that defensive reasoning has on me, and how to recognize when I am entering that “mode”.


Monday, November 12, 2012

Tech Transfer and Intellectual Property


       This past week I had the very special opportunity to attend a talk by Gaylene Anderson who is from the University of Idaho Tech Transfer.  She gave a very easy-to-listen-to, highly informative talk on how to protect intellectual property.  While she gave us information on patents, licenses, trade secrets, and tips and information on how the process of technology transfer works, there were a few things that stuck out as being especially useful to me right now.  These were things like: the things an idea (i.e. an invention) has to be in order for it to be patent-able, what to do when sharing your ideas with others, and knowing whom your customer is.
The first thing that stuck out to me as being pertinent to my current situation was when she talked about what an idea has to be in order for her to be able to file it for a patent.  Interestingly enough, the idea must be novel, useful, and non-obvious.  The first two made sense to me right away.  Obviously, if a new invention is not going to be novel or useful, it is probably not worth patenting.  However, the third stipulation, that of the idea being non-obvious, caught me slightly off-guard.  In my mind, I had always thought that it wouldn’t matter how obvious (i.e. if someone else in your profession looked at it would they be able to figure it out easily) of a thing it was as long as your invention was something novel and useful.  Knowing this gives me a much clearer idea of what I need to aim for when developing new products, and when deciding if an idea is worth patenting or not.
Sharing ideas with others is an extremely natural thing for people to do.  I know that if I have a new thing or idea, I just love telling others about it.  Knowing this, Gaylene Anderson gave us some tips on how to be able to share our ideas with others while keeping them safe from being stolen, etc.  By making the party I am sharing with sign a confidentiality agreement (even if it is only on a napkin), not only will they not be able to steal my idea, but also my disclosure of information will not be considered a “public disclosure” and I will not be required to file for a patent within 12 months.  This it invaluable to me because I love telling others about my work and designs, so having a way that I can do that without painting myself into a corner is going to be very useful.
Finally, Gaylene Anderson reminded us of the importance of knowing who my customer is.  She told numerous stories of products that were “cool”, but had no marketability because there was no customer base for them.  This is definitely an important point since Dr. Elger has been pointing it out a lot as well this semester.  Understandably, I can apply this idea in every product that I create.  Knowing who my customers are while I am building a product will not only allow me to create better products, but also more marketable ones.
Gaylene Anderson’s talk was incredibly helpful to me as an engineer who is excited about designing and inventing new things.