======Part 1======

=====Entries=====
====Entry 1: September 25, 2012====

Today we started off talking about sorting. We tried to figure out how a program would sort numbers from least to greatest. We spent the rest of the class trying to write the program. After matt helped me with the loop I tried to get it to sort but it's a little harder than I thought it would be. I tried just putting the less than symbol in but that didn't work. I haven't figured it out yet but hopefully I will soon. 

====Entry 2: September 26, 2012====

Today in linux/unix we talked about wildcards. We learned that ? = any single character, * = 0 or more of any character, [] = match any size of echoed and [^] = do not match any single. You can also combine then together with ls to find vowels or how many files have 4 letters. We played around with combining different kinds of wildcards with the ls and wc -w command. I  had to leave about a half hour early and thats the last thing that I did.
====Entry 3: September 27, 2012====

Today in discrete I worked on the sorting program. I realize that I am not very good at programming but hopefully I get better soon because im feeling lost. I worked on trying to get it to sort and also just printing the list before it gets sorted. I spent just about all class trying to do this. I looked at the set program at first but I didn't work on it much. Most of the time I was trying to get numbers sorted.
====Entry 4: September 28, 2012====

Today we talked more about scripts. We went over that you need the #!/bin/bash before any script that you make, unless its a different language. We then made a game from a script. It asked the user try and guess a number using the $RANDOM variable. It would then say with it was equal with -eq, less than with -lt, or greater with -gt than the random number. At first we were getting really high numbers but then we changed the range from 0-9 by using the bc calculator. We went over if statements and if else statements and learned that to close if statements its fi and else if is elif. At the end we had a working guessing game that gave you six chances to guess the right number.
=====Keywords=====

{{page>discretepart1&nofooter}}

{{page>unixpart1&nofooter}}

=====Experiment 1=====

====Question====
What does the > mean in vim.

====Resources====
http://www.pixelbeat.org/vim.tips.html

====Hypothesis====
I know >> indents but maybe > indents less or maybe half of an indent.
State your rationale.

====Experiment====
Im going to type a bunch of words that dont really make any sense. After I get done typing im going to do the >> command to see an indent first and then the just the > to see what happens.
====Data====
what I typed before doing anything.
<cli>
  1 this is the experiment i dont know what im
  2 typing i just need a
  3 bunch of words and im trying to think
  4 of ideas but im running out so im going to
  5 go because i think i have enough words now
</cli>
What happened when I used the >> command

<cli>
  1 this is the experiment i dont know what im
  2 typing i just need a
  3 bunch of words and im trying to think
  4     of ideas but im running out so im going to
  5 to go because i think i have enough words now 
</cli>
What happened after I did the > command on the last line. Nothing happened.
<cli>
  1 this is the experiment i dont know what im
  2 typing i just need a
  3 bunch of words and im trying to think
  4     of ideas but im running out so im going to
  5 to go because i think i have enough words now 
</cli>
====Analysis====
Based on the data collected:

  * Was your hypothesis correct? No my hypothesis wasn't correct at all. The command did nothing.
  * Was your hypothesis not applicable? I think my idea was good but it didn't really do anything.
  * Is there more going on than you originally thought? (shortcomings in hypothesis)It might be waiting for another command after the > or a number before maybe like the number of indents like 1> or 1>>


====Conclusions====
I found out that although the >> indents the > command does not do anything. I tried the 2>> command too and it doesn't indent twice either. So unless it is used differently than what I'm trying to do I think the >> command is the only command using the greater than symbol. Also you can only indent once at a time, but its very quick so maybe thats why they didn't add that