======Part 2====== =====Entries===== ====Month Day, Year==== This is a sample format for a dated entry. Please substitute the actual date for "Month Day, Year", and duplicate the level 4 heading to make additional entries. As an aid, feel free to use the following questions to help you generate content for your entries: * What action or concept of significance, as related to the course, did you experience on this date? * Why was this significant? * What concepts are you dealing with that may not make perfect sense? * What challenges are you facing with respect to the course? Remember that 4 is just the minimum number of entries. Feel free to have more. ====Month Day, Year==== This is a sample format for a dated entry. Please substitute the actual date for "Month Day, Year", and duplicate the level 4 heading to make additional entries. As an aid, feel free to use the following questions to help you generate content for your entries: * What action or concept of significance, as related to the course, did you experience on this date? * Why was this significant? * What concepts are you dealing with that may not make perfect sense? * What challenges are you facing with respect to the course? Remember that 4 is just the minimum number of entries. Feel free to have more. ====October 21, 2011==== I found out how important order can be and is. I made a program that should have read in a file then changed the values in it to HEX, it then saved this. Next it would take the HEX file that it just made and read it in and replace the HEX with the binary values of the HEX. The program did not work and yet it didn't work. The first part worked be the second part did not because part of the program was happening before the other part so it would make the file full of HEX but it was not reading that out. So all that could be seen is the text its self before it was put in HEX. Thus the order has to be in a different order then what it was to work the way I wanted it to work. ====October 24, 2011==== Bitset that there is a special way to store store bits in C++ and that you can store just the bits. Its just so cool what can be-found when looking for other stuff. There's set reset and flip. =======Data Topics======= =====Linked Lists===== A Linked Lists is a string on nodes that are connected. There only one way. Node1 -> Node2 -> Node3. 8-) -> =) -> :-P -> :-D =====Doubly Linked Lists===== A Doubly linked list is a linked list that is two way and not just one. 8-) <-> =) <-> ^_^ <-> ;-) =====Stacks (array-based, linked-list based)===== A Stack is a nice and neat pile of items. A stack can be a array-based or linked-list-based. Both kinds need to be filled by pushing a item in to that stack and to remove a item you pop it from that stack and this can only be done from the top of the stack. ==Pushing== This is like putting something on top of something else. As you push new items on the list it gets longer. This adds a item to the stack. ^ ^ ^ ^ ^ ^ ^NewTop^ ^ ^ ^ ^ ^NewTop^ |OldTop| ^ ^ ^ NewTop^ |OldTop| |OlderTop| ^Top^ |OldTop| |OldestTop| |OldestTop| ==Popping== Popping is when you take a item from the list. So that when the top item is popped its taken off the Stack. This is taking a item from the stack. ^Item1^ ^ POP ^ ^ ^ ^ ^ ^ ^ ^Item2^ |Item2| ^ POP ^ ^ ^ ^ ^ ^Item3^ |Item3| |Item3| ^ POP ^ ^ ^ ^Item4^ |Item4| |Item4| |Item4| ^POP^ ==Top== The Top is the Item that is in the top most place of the stack. This lets you get to the next item in the stack. ^Top ^ |Ntop| |Ntop| ==Overflow condition (where applicable?)== This is where a stack has used up its memory and is now overflowing. This happens when the memory is not big enough for the data that is filling it when it reaches the most it can handle it overflows. ==Underflow condition== This is where there is not enough data to fill the stack. ==LIFO or FIFO?== A stack is LIFO or FILO. For the last one in is the first one out. Or the first one in is the last one out. =====Queues (array-based, linked-list based)===== ==Enqueuing== ==Dequeuing== ==Overrun and Underrun conditions== ==LIFO or FIFO?== ======HPC1 Topics====== =====Troubleshooting===== Troubleshooting is what is done when there is a problem (i.e. when it's not working correctly ). If the computer is not coming on when you push the button. Is it plugged in, is the power strip on, did the power supply go, is it the motherboard, is it beeping, and so on. First you look for the most simple thing that can go wrong and start there. Then move to the next thing in line after that. One's you have tested and looked at every thing it could be and some stuff that it might be it might start working or it might not. While in the proses of working it out you are troubleshooting. ones you are done you have fixed it or have to find a workaround. =====security - external===== =====LIFO & FIFO===== LIFO - Last in First out ^ Stack ^ In ^ Out ^ |4 - 1 | last | first | |3 - 2 | third | second| |2 - 3 | second | third | |1 - 4 | first | last | FIFO - First in First out ^ Stack ^ In ^ Out ^ |4 - 4 | last | last | |3 - 3 | third | third | |2 - 2 | second | second | |1 - 1 | first | first | ====Keyword 4==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ====Keyword 5==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: /* * Sample code block */ #include int main() { return(0); } ====Keyword 6==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ====Keyword 7==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: /* * Sample code block */ #include int main() { return(0); } ====Keyword 8==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ====Keyword 9==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: /* * Sample code block */ #include int main() { return(0); } ====Keyword 10==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ====Keyword 11==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: /* * Sample code block */ #include int main() { return(0); } ====Keyword 12==== Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ =======Sysprog Topics======= =====Focus on File Systems===== ===Filesystem Structure; inodes and data blocks=== ===Directories=== ===Links=== =====Connection Control===== ==Device files== ==Race conditions== ==Atomic Operations== ==Streams== =====Terminal Control and Signals===== ==Blocking vs. Non-Blocking== ==Signals== =====Event-Driven Programming===== ==Alarms, Interval Timers== ==Reentrant code, critical sections== ==Asynchronous input== ======Data Objective====== ===Objective=== Describe how the data structures are allocated and used in memory; define what that objective entails. ==Method== State the method you will use for measuring successful academic/intellectual achievement of this objective. ==Measurement== Follow your method and obtain a measurement. Document the results here. ==Analysis== Reflect upon your results of the measurement to ascertain your achievement of the particular course objective. * How did you do? * Room for improvement? * Could the measurement process be enhanced to be more effective? * Do you think this enhancement would be efficient to employ? * Could the course objective be altered to be more applicable? How would you alter it? ======HPC1 Objective====== ===Objective=== State the course objective; define what that objective entails. ===Method=== State the method you will use for measuring successful academic/intellectual achievement of this objective. ===Measurement=== Follow your method and obtain a measurement. Document the results here. ===Analysis=== Reflect upon your results of the measurement to ascertain your achievement of the particular course objective. * How did you do? * Room for improvement? * Could the measurement process be enhanced to be more effective? * Do you think this enhancement would be efficient to employ? * Could the course objective be altered to be more applicable? How would you alter it? ======Sysprog Objective====== ===Objective=== State the course objective; define what that objective entails. ===Method=== State the method you will use for measuring successful academic/intellectual achievement of this objective. ===Measurement=== Follow your method and obtain a measurement. Document the results here. ===Analysis=== Reflect upon your results of the measurement to ascertain your achievement of the particular course objective. * How did you do? * Room for improvement? * Could the measurement process be enhanced to be more effective? * Do you think this enhancement would be efficient to employ? * Could the course objective be altered to be more applicable? How would you alter it? =====Experiments===== ====Experiment 1==== ===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. ====Experiment 2==== ===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. ====Retest==== If you're doing an experiment instead of a retest, delete this section. If you've opted to test the experiment of someone else, delete the experiment section and steps above; perform the following steps: ===State Experiment=== Whose existing experiment are you going to retest? Prove the URL, note the author, and restate their question. ===Resources=== Evaluate their resources and commentary. Answer the following questions: * Do you feel the given resources are adequate in providing sufficient background information? * Are there additional resources you've found that you can add to the resources list? * Does the original experimenter appear to have obtained a necessary fundamental understanding of the concepts leading up to their stated experiment? * If you find a deviation in opinion, state why you think this might exist. ===Hypothesis=== State their experiment's hypothesis. Answer the following questions: * Do you feel their hypothesis is adequate in capturing the essence of what they're trying to discover? * What improvements could you make to their hypothesis, if any? ===Experiment=== Follow the steps given to recreate the original experiment. Answer the following questions: * Are the instructions correct in successfully achieving the results? * Is there room for improvement in the experiment instructions/description? What suggestions would you make? * Would you make any alterations to the structure of the experiment to yield better results? What, and why? ===Data=== Publish the data you have gained from your performing of the experiment here. ===Analysis=== Answer the following: * Does the data seem in-line with the published data from the original author? * Can you explain any deviations? * How about any sources of error? * Is the stated hypothesis adequate? ===Conclusions=== Answer the following: * What conclusions can you make based on performing the experiment? * Do you feel the experiment was adequate in obtaining a further understanding of a concept? * Does the original author appear to have gotten some value out of performing the experiment? * Any suggestions or observations that could improve this particular process (in general, or specifically you, or specifically for the original author).