======Part 1====== =====Entries===== ====Entry 1: January 27th, 2012==== This week for computer organization we really just talked about what was going to happen. We explained how logic gates work and how we were to use them. We counted 0 to 64 in binary to show how we would count through with these gates. With the gates we are going to create a computer simulator, slowly creating flip-flops, registers and programs to run through it for us to see if it works. So with the logic gates, we first made up truth tables to show how they would operate. Then we began creating the codes for the in linux. In HPC, i started looking at a script that is for the mac labs up in corning. The script is flawed and does not work. It is made to add, change and delete usernames for the students that use them. So for one of my projects in this class, im going to understand how this works and hope that i can fix it so they are able to use it. ====Entry 2: February 3, 2012==== This week of class we went more into the computer simulation. We talked a little on logic gates and the logic of using them. We have header files and programs that will run these gates. But soon we learned to combine them to create more gates and to start the creation of flip flops. Its a combination of logic gates that will create certain outputs that we could use for bigger parts of the computer. It would either give out a value or an undefined, and these two outputs could be used for our advantage when creating this computer simulation. In HPC, I am still looking over the script. Its a little more confusing then originally thought of so it might take longer then usual. I am beginning to have more of an idea of how this script works but not enough to actually start manipulating it in any way. ====Entry 3: February 10, 2012==== In this week of computer organization, we talked more on flip flops and latches. We talked a little on how they worked and how they will be implemented into registers, the place where most of our memory runs through and gets stored. I actually taught the class this week of how a register should work. I didnt have a complete concept of it but i knew enough to actually talk to the class about it. The register can output and input data many different ways, like serial to parallel or parallel to parallel. With these different ways, we can manipulate on how we want our data to be outputted. So we can store information how we want and output the information the way we want. So we talked about this and how it can be used in our simulation. In HPC i believe i know how this scripts work. Once you see it, its pretty segregated in its steps and you can see where it can be broken up into functions, i just need to know how to use functions in bash scrpting, i havent delved into that yet. I will perform a experiment on it i believe to get a better understanding of it. But all together, i got good headway on this script. ====Entry 4: February 17, 2012==== This week we talked a little more on the use of registers and flip flop logic. It was kind of confusing but i think it is understood now. But the main topic of the week was learning the turing theory. he was the father of computers, in a way. he had made a theory of a basic computer. Infinite tape ran while a head would move left, right, or place a value on the tape. It was a simple programing computer (in a way) that read input and wrote output onto tape. So we did an excercise with this to get thinking on different concepts of simple logic and programming since we will be dealing with a low level language when finishing this computer simulation. In HPC, i am having a hard time with this script. I wish i wasnt taking so long but when i feel like i am making head way, it somehow gets ruined and i have to start from sqaure one. I feel i should look this over some more and see what can be done for me to get a better grasp. =====Keywords===== {{page>asmpart1&nofooter}} {{page>hpc2part1&nofooter}} =====Experiments===== ====Experiment 1==== ===Question=== How Does Whiptail work in the linux enviroment? ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. ===Hypothesis=== Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * Was your hypothesis correct? * Was your hypothesis not applicable? * Is there more going on than you originally thought? (shortcomings in hypothesis) * What shortcomings might there be in your experiment? * What shortcomings might there be in your data? ===Conclusions=== What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made. ====Experiment 2==== ===Question=== Is there a way to read and connect data from different files of scripts into one script? ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. ===Hypothesis=== Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * Was your hypothesis correct? * Was your hypothesis not applicable? * Is there more going on than you originally thought? (shortcomings in hypothesis) * What shortcomings might there be in your experiment? * What shortcomings might there be in your data? ===Conclusions=== What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made. ====Experiment 3==== ===Question=== What is the question you'd like to pose for experimentation? State it here. ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. ===Hypothesis=== Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * Was your hypothesis correct? * Was your hypothesis not applicable? * Is there more going on than you originally thought? (shortcomings in hypothesis) * What shortcomings might there be in your experiment? * What shortcomings might there be in your data? ===Conclusions=== What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made.