The Kuhlest
Site Ever
pokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemonpokemon
by: Richard King
ProjeKts
Monday 15 June 2009
TenThingsILearned
1.) Kernal is the most
important part of an operating system.
2.) the Kernal is in between the assembler and the Operating system.
3.) The Kernal manages the CPU.
4.) The Kernal manages the memory.
5.) the Kernal manages the I/O.
6.) Linux is a free os.
7.) operating system is abreviated as OS or O/S.
8.) The OS manages the resources.
9.) linux was published under general public access.
10.) The scource code for linux is accessable to everyone.
My Journal
Today in klass we learned about the kernal and linux. We
also learned eachothers names. I have already forgotten almost
everyones names. We made a Kuhl game. We did the hello world thing. We
learned how to do some programing and made this web page.
WacKadot
order
of steps I would do:
1) make the curser dot
2) make a location randomizer thingy
3) make the color thingy
4) make the other dots
5) make the right or wrong thing +score
there were differences in the order of steps mainly because I did Not
think of the display, making awhole thing for the dots. also i had
thought to do the colors with the randomizer.
step 1:
this step makes a black screen, thing to quit, and a random
number
generator.
step 2:
generates
red dots.
step 3:
make
the dot follow
the cursor
3.1:
before
I think that the code would be:
def curserdisapere (pygame.mouse,color)
pygame.mouse.color = pColor
after
pygame.mouse.set_visible(1==0)
step 4
makes a red and blue dot
step 5:
obtains new position to handel colisions (of points).
step 6:
changes the position and the color of the dots
step 7:
keeps score
q2
the reason that some steps are done more than once in the loop.
q3
I did not under stand sprite. I think that the dots specify things
(sort of like a slash). One group is is for the circles; theother is
for the rectangles.
Tuesday
16 June 2009
Today I learned: software kontrols hardware; leap
years okkur on years divisible by 4, but on years that are divisble by
100 but not 400 , leap years do not okkur; how to make a program that
calculates the price of pizza per square inch; cumputers are stupid; I
have to tell a computer explicitvely what to do; how to swap variables;
how to assign multiple variables at once; how to do inputs; how to do
math; how to be kuhl; it requires a 3rd level derivative for a
pokedog to
catch a frisbey; how to do definnite for loops; how to get a square
root; we learned about intergers, long, and floating digits. We created
several programs the most challenging was the date problem.
Wednesday
17 June 2009
we
learned about strings and list today. we also learned about
other stuff.
Thursday
18 June 2009
In my opinion the most important parts of a game are no movies,
challenging, grafics, audio, ballence, content, and pacing.
The website was informative. It was fun. i learned that there has to be
a goal.
We learned about defining functions. it is not neccessarilly about code
length.
Friday
19 June 2009
Today we learned about the disadvantages of for loops, whisch is that
they require a definite sequence. we learned about while loops. while
loops are done with a condition (while true, while
i<10). We learned about booleans: True is 1 and Fale is 0; and is like multiplication; or is like addition, and not is the
oppisite (i.e. 1 not 0; 0 not 1). the order of opperations in
boolean algebra is not then and, then or.
We learned about sprites and pygame today. Py game does not require a
GUI; pygame adds silliness every 3.1415 seconds; pygame does not
require OpenGL; it acan be used on multi-cored CPU's; and it is easy to
use. sprites are a very important part of pygame. they have a
location and a image attatched.
not, then
and,Monday
22 June 2009
then, or.
today we learned the things. we
learned to be specific about stuff. we learned about life.
Tuesday 23
June 2009
We learned NOTHING!!!! We PROGRAMED!!!!!
Wednesday
we learned about vectors. we programed.
Thursday
Today we learned about AI. AI is
never really done. There is the searching method of AI. AI used
to be mainly math logic. It then bekame biology. they made the sensors
that were like nuerons. originally , they only used one that was able
to solve only linear problems. they then did the genetic algorithem.
Then they made these system of nuerons that kould do most things after
being trained. The mathmaticians kame bakk to say that they kould do
the same stuff with math but they instead aktually knew what was
happening. so then the knew thing was statistiks. they were able to
make robots that kould do many things with statistiks (such as locating
itself). The problem is when are they done. Also, how do they make
robot of human-like intellegence.
Friday
Today we learned about cyber
monkeys. there are brain machine interfaces. they will one day be used
for pristetics. this will go on and on. this resaerch is funded by the
military. the brain controls things with its mind. the devices can
either be implanted or they can be done on your head. the video game
controlers that do this dont work very well. There are two types of
interfaces that go one the head, EEG and ECoG. they did not look good.
they had spike to begin with but they then became more esthetic. the
brain thing detekt spikes in the brain. the equation for movement were :
x = a1
* n1 + a2
* n2 + a3
* n3 + ...
y = b1
* n1 + b2
* n2 + b3
* n3 +
...
where
n=firing rate. I kould use this in a program to simulate some sort of
ai thing.
Saturday
There was this man how made a game in one week. He
learned a lot. His game was called Hackenslash.
It was a RPG. He did a lot in his last bit of time. Specifikly, he did
the most during the last fifteen hours. He gave himself forty hours
because that is the standard work week. The reason for all of this is
because he figured that it would not be so hard to program a game is
one week.
At first he thought that he would not have the time
to take off forty hours. Eventually he decided to go through with he
challenge. he broke his time up into incament of ten hours in his
planing. The first ten hours were to be used for engine set up. The
second ten hours were to be used for making the character work. The
third ten hours were to be used for creating the maps, the AI, and et
cetera. The forth ten hours were to be used for adding features.
The post production time was to be used for debugging.
I also made a game in a group of four. It was
a space shooter. We did the levels and enemy and charcter and
power ups and lasers and tmplate seperatly. We failed. It did not even
work. The compiling did not work. some of the code was retarded. The
debuging was impossible. We worked a lot harder in our last thirty
minutes then in the reat of the time. We did our plot in the last ten
minutes.
The guy who programed a game in a week also failed,
but not as fully as we did. He learned that it is best to get the
important stuff first. He also learned that it is important to always
be in crisis mode. He learned that he should have had someone else do
the art. He also learned that it is often better just to start over
with code. He learned that scope should not exceed budget. We learned
very similer things.
Monday
Today we started our final projekts. I am doing an RPG. I am using
everything I learned.
Tuesday
Today, I did the graphics and side bar.
Wednesday
Today, I sprited skeletons. We made enemies. I made a maze with
an invisible wall. It says, "BWAHAHAHA!!!" when the player steps next
to it. I made chests open. Gotta'
catch 'em all!
Thursday
I learned much in this class. It was Fun. I started this class as a
novince programer but I am much better now.
Last Day: Friday 4
July 2009
I think we did well on our final project. the only thing I regret is
that it was not fully debugged. I like the class and the language. I
thought that the projects were fun. i did not ever get to play my
project. I hope to continue work on it when I get home.
We should have spent more time integrating the file and actually
playing the