Brian's THIS SEMESTER Opus
BLARGL FLARGL
In the beginning, there was nothing……Then Derrick Mcglynn decided he had enough of not existing……so from non-existence he imagined Brian Black…….from there Brian's imagination flew out of control and subsequentially imagined Derrick into existence……all at the same time creating the world out of Brian's imagination flying wild…..meanwhile in an alternate dimension John Kingsley's brain (as Skynet now) had created Matthew Taft, the latter of which went back in time to destroy John before he became as powerful as he was…….little did he know that as he inevitably fails……his body is used to make John into Skynet…..but in the most recent iteration he was sent across dimensions on accident and landed here…..where he co-exists with his dimensional twin, Brian……….and that my friends……is how the world started….but that has no bearing on what this opus is about
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
Identification and definition of the chosen 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 <stdio.h> int main() { return(0); }
Identification and definition of the chosen 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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
State the course objective; define what that objective entails.
State the method you will use for measuring successful academic/intellectual achievement of this objective.
Follow your method and obtain a measurement. Document the results here.
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.
State the course objective; define what that objective entails.
State the method you will use for measuring successful academic/intellectual achievement of this objective.
Follow your method and obtain a measurement. Document the results here.
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.
State the course objective; define what that objective entails.
State the method you will use for measuring successful academic/intellectual achievement of this objective.
Follow your method and obtain a measurement. Document the results here.
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
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:
Whose existing experiment are you going to retest? Prove the URL, note the author, and restate their question.
Evaluate their resources and commentary. Answer the following questions:
State their experiment's hypothesis. Answer the following questions:
Follow the steps given to recreate the original experiment. Answer the following questions:
Publish the data you have gained from your performing of the experiment here.
Answer the following:
Answer the following:
I've been working on my Linked list library implementation. I started by creating the main and trying to get the list to get created. I also decided that this would be what I would be using for Joe Oppenheim's class, so after deciding that I had chosen to use a char data type instead of the int that everyone else seemed to be using. So after half of the class of screwing around with Tyler and Andrew (not to point fingers [point point] >.>) I hacked together a main program named “doublylinkedlib”, original I know. All it does currently is it takes input and puts together a list of the string. I know at some point i need to be able to get it to accept a string from command line so that it works perfectly for Joe's class. But, that's all later down the road. I have plenty of time. The first function I am working on will probably be “append” simply because that will be one of the easiest ones to quickly hack together. Mostly because I only have to work on a simple thing of adding it in, and wholesale copying and pasting the section of the building my list from my main. God only a few more tens of words. I've run out of things to say but I need to get 300 words out for each entry that way the 4 entries will total to the 1200 I need for the month. Oh and for the record, I am TOTALLY not writing this at 10/30/2011 at 10:20 at night. Nope, totally not. How is it that I have no issue doing the work but I have a hard time getting my thoughts onto the opus so that it will be graded?
Here we are, week two into the month and earlier I thought I had finished append. Yet, it turns out that it kept breaking somewhere. That's when Matt had shown me about GDB and how to properly find out the line (and when he went through it, it had seg faulted). After like 20-30 min later I had fixed the line that was getting the error. Somehow tmp was being passed as NULL so when I went to make tmp = tmp → next it would seg fault. I still do not remember what the other functions I need to have made done, and what is this prototype that I need to have in the header file that I have yet to create? Something tells me I should know it and that it is a common sense thing, that's why I am apprehensive about asking anyone in the class what it is, because the last thing I need is for them to think that I can't code. I barely show up let alone let's make me seem like I have no idea what I'm doing. Still, I think I'm going to ask Tyler Monday if he knows what the functions are. If not then there's always the other classmates. Although I think Brad may be my only hope (queue cheesy star wars reference) hopefully not though. So far my project is going good, and it seems a good experiment to try is to try my best to break my code as much as I can. Because from what Andy and I have seen, char takes so many different keystrokes. There's got to be a way to break it, maybe from pressing too many keys at once. You know, inputting more than 1 character at a time. Like entering the full string of “hello world” all at once. Yea, that might work.
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
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:
Remember that 4 is just the minimum number of entries. Feel free to have more.
Identification and definition of the chosen 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 <stdio.h> int main() { return(0); }
Identification and definition of the chosen 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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
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 <stdio.h> int main() { return(0); }
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$
State the course objective; define what that objective entails.
State the method you will use for measuring successful academic/intellectual achievement of this objective.
Follow your method and obtain a measurement. Document the results here.
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
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:
Whose existing experiment are you going to retest? Prove the URL, note the author, and restate their question.
Evaluate their resources and commentary. Answer the following questions:
State their experiment's hypothesis. Answer the following questions:
Follow the steps given to recreate the original experiment. Answer the following questions:
Publish the data you have gained from your performing of the experiment here.
Answer the following:
Answer the following:
Here we are in November……guess i'm a little behind with my projects……need to figure out how to implement stacks and queues into my program so that I will have one program that uses all the different functions needed for the 7 minimum (it's going to end up using ALOT more than that) that way I only have to write one “main.c” instead of having to write a minimum of 7 “main.c”…..hopefully i'll end up getting hit by a stroke of genius and i'll be able to blaze through my work and be able to write my opus without too much of an issue. Balancing work and class is still proving to be a bit challenging but hopefully i'll be able to pull through and scrape by with a C in this class…..but with only one class with Matt it makes it hard to figure out how to write 300 words each week……..that's probably my weakest part in this class……that and just remembering to do the thing…..i wish i still had my laptop up and running that way i could just use that during my free time at school when i DO remember about this…..but as the holiday season continues and as work hires more people (giving me less hours because of it) i may be able to use the extra free time effectively and productively for this class…..keep missing the official class time because of my inability to keep track of time…..but in my mind atleast i'm making it up by staying through SysProg all the way through to Joe's class (which is kind of my way of insuring that i'll go to his class since there's next to no urge to skip his class while i'm already down here)
Well it looks like I'm REALLY behind because i STILL haven't figured out how to properly implement the 4 stacks and 4 queues i need for my projects and they learned about Binary Trees this week……so that's ANOTHER thing to add to my ever-growing to-do-list……/sigh i wonder if i'll ever catch back up…….hopefully next weekend i'll be able to get everything caught back up……i really should be able to catch up with like 90% of the week off from work…..at the same time Skyrim just released Friday and that's been the only thing on my mind this entire weekend…….hopefully that doesn't take up all my free time this week…….still facing the issue of not having a laptop and pretty much borderline NEEDING one by being a computer science major……I know i need to find out how to work in 2 binary trees, a graph, and a hash table…….those are the oddest things to try to work into my program……plus i need 1 more thing for file I/O because i can just use the one thing from last sem for my freecell program……actually now that i think about it i can instead of making it freecell i can make it shuffle the deck and then “draw” the top, we'll say 20 cards for argument's sake, then display using a graph the amount of each value upto 4 obviously…….that's actually a great way to use it……because i would end up getting stack, graph, file I/O and maybe a queue if i do the display portion properly…….that's 4 requirements in one go…….not too terrible and that's using an old program…….i may be able to just pull this off if i do it right.
Another Week and no progress made……..work keeps dragging my motivation down……looks like i'm gonna have to pound out not only this entire Opus but 90% of these projects in the up coming weeks……no break for CoD or Skyrim or even Reddit……..Hopefully i can not end up procrastinating like usual and get atleast the opus done……..atleast i know what my keywords are going to be on…….I really need to check the syllabus to see if the keywords have a minimum word count on them or not…….Also i need to study the keyword section for the proper format for them……only one hundred out of three hundred words…….dang…….i really hate this minimum word count at times……..it can be really hard to think of 300 words for an entry when i've done no work……granted the final few ones shall be easier since i plan on making 3 more entries so i have 7 total entries versus the minimum 4 making each entry only 100 words needed…..If only i could stop procrastinating for a week or two so i don't end up having to do 80% of this semesters work in 1-2 weeks……knowing my luck that's just how it's gonna happen…….he should be announcing the end of course experience soon……i really need to find out when he's going to post it and what is required on it…….because that's the last thing i need to not meet the deadline for……hopefully some of the stuff he has us do for that will also count towards our requirements on the course because i am still stuck as to how to use a hash table for this class…..Oy i hope i can figure something out soon
like…..zomg i didn't have a weird name for the month this time…….i kinda ran out of ideas for the months for December…….and i'm actually doing a Opus entry the date i posted it as?!?!? what blasphemous work is this……yes that's right i'm finally kicking myself into high gear……i only have this week and finals week to have all of my work for Data done so i can hopefully pass the class…..tonight i shall work on atleast 6 of the keywords……hopefully i can get all 12 done before the night is up……i have 3 hours to kill……i should have plenty of time……worst case scenario…..i finish them up in class
Got no work done yesterday…….hopefully i should get the keywords done tonight……also done with the experiments since i can avoid going tomorrow……..so due to that it allows me to spend all day (especially since i have the day off from work too) on my EoCE…….i should get Palindrome done…..as well as the string correcter-thingy…..and maybe my hash table and graph that i need done……those being noble goals i REALLY hope i can get them accomplished…….since i have the entire day i should be able to get more than just that……but knowing my luck and skill in procrastination i most-likely will only get that done…..but here's to hoping
well ain't this a kick in the teeth…….i can't connect to lab46 through putty……guess i have to reboot my computer and go into linux so i can write the programs and be ready to just ssh into lab46 once i get everything sorted out
after some messing around to update my linux……and then problem after problem of trying to do stuff like login to this very site…….SUCCESS!!!…..partly……still can't SSH to lab46……but atleast i can still code my stuff for my EoCE
got distracted and decided to work on PrimeNumber but i am get the error
“/tmp/ccIA1epd.o: In function `main': PrimeNumbers.c:(.text+0x82): undefined reference to `sqrt' collect2: ld returned 1 exit status ” when trying to sqrt the input……why does taking the easy way have to be so hard?
Computational Complexity is a part of the theory of computation. It pretty much classifies computational problems according to difficulty and relates classes to one another.
Big-O notation is used to show time complexity
Theta is used to show a asymptotically tight bound
Bounds are used as both Upper and Lower bounds which are just subsets that are greater-than or equal to/lesser-than equal to respectively to the main set
a sorting algorithm is an algorithm that places the input into a certain order for the output
Selection sort algorithm has a time complexity of O(n^2) making it inefficient for large lists…..how it works is it runs through the entire list finding the lowest value, then it switches that place with the first position……..then runs through to find the next lowest value……rinse and repeat for the entire list.
Bubble Sort Algorithm steps through the input comparing adjacent pairs each time and swapping them if they are in incorrect order (the lower one is the latter one). Each full interation causes one less swap needing to happen because of the higher value of the iteration being placed at the next highest position
Insertion Sorting Algorithm is used by taking a value and placing it into its approximate place.
State the course objective; define what that objective entails.
State the method you will use for measuring successful academic/intellectual achievement of this objective.
Follow your method and obtain a measurement. Document the results here.
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
What is the question you'd like to pose for experimentation? State it here.
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.
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.
How are you going to test your hypothesis? What is the structure of your experiment?
Perform your experiment, and collect/document the results here.
Based on the data collected:
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.
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:
Whose existing experiment are you going to retest? Prove the URL, note the author, and restate their question.
Evaluate their resources and commentary. Answer the following questions:
State their experiment's hypothesis. Answer the following questions:
Follow the steps given to recreate the original experiment. Answer the following questions:
Publish the data you have gained from your performing of the experiment here.
Answer the following:
Answer the following: