Differences

This shows you the differences between two versions of the page.

--- blog:fall2015:pgrant3:journal [2015/10/27 03:38] – [October 19, 2015 C Prog] pgrant3
+++ blog:fall2015:pgrant3:journal [2015/12/08 03:56] (current) – [November 16, 2015 C Prog] pgrant3
@@ Line 50: / Line 50: @@
 We looked at shell scripting more in class, and I have been playing with it out of class.  However, I could not successfully create a script that can give the user a count of how many terminals each user logged into lab46 has open.  I think we are going to go over it tomorrow in class though, so I am eager to see how it was done.  My biggest issue with shell scripting is definitely going to be remembering all of the unix commands that are available for us to implement, when applying a solution to a problem.
+====November 2, 2015 UNIX====
+After completing the wpa0 project, I have learned a lot about changing web pages based on directories that the source code is located in.  That was my biggest issue when working on this project.  It took me a lot longer than it probably should have figuring out which way to write out the address of the files that I was trying to display.  Part of the reason that it took me so long was because I was over looking basic syntax of HTML.  I would be missing simple things such as a " before an "a" tag.  After completing this project I was extremely satisfied with my end result.  Way more so than I thought that I would be.
+The next project that we are doing seems difficult in the way that the puzzle box projects were.  We are given a file and we have to use the tools at our disposal to resolve the problem.  After looking at it for a few hours and tinkering with it, I didn't get anywhere.  I need to sit down and really focus on this one.  Some commands that I am using don't seem to be working, when it seems like they should be.  Also, we have to log every command that we use in solving this project, and that is different as well.  I am excited to actually start logging the correct procedures in order to complete this project.  At this point I am not very far at all.
+====November 9, 2015 UNIX====
+I successfully completed udr0.  As I said in my previous entry, I had spent quite a bit of time poking at it, just looking for a place to start.  After being shown a hex editor in lab46, the address and the length of the pieces made more sense.  We were introduced to a table of contents that gave us the information that we needed in order to grab each of the three files that we needed to arrange to view the image, which was the end state of the project.  Admittedly, I ended up doing way more math and conversions from octal and hex to decimal than I really needed to.  But it got me on the right track.  After realizing the simple way of doing it, by skipping to the address and grabbing the length of the contents with the dd command, the first half of the project became trivial.  It just took me a lot longer than I would have liked to get there.  After putting them all into one file and seeing that it was an RLE image, converting it to the correct format and resizing it to fit the requirements was a breeze.  I think that this project was definitely harder than the puzzle box projects were, for the sole fact that it was extremely difficult to find out where to even begin.
+The next project we have due this Wednesday has us writing a script, which I desperately need more practice with.  I haven't started this to the point have should have at this point, but I am excited to begin and become more familiar with scripting.
+I ended up downloading a Unix based OS on my home computer called Fedora.  Attempting to set up my own flavor of Unix Operating System is turning out to be enjoyable.  Not quite as relaxing as I would have hoped, but relating what we learn in class with something I can do in my personal time to enhance my experience on my desktop is satisfying.  I was looking into attempting to use Arch Linux to really have control over the specifications that I will utilize when I'm on my personal computer, but I think I have quite a bit to learn before I break an operating system that I attempt to use.
+====November 16, 2015 UNIX====
+I have started working the logic on for the project that was extended a week, due this Wednesday, rather than last Wednesday, out on paper.  Logically, I can figure out the direction that I am going with this project.  I have found that actually working out a solution on paper, for logical reasons, outside of syntax, is better for me than just diving headlong into a project which is what I usually do.  My biggest issue going into this project is definitely syntax of scripting.  Bash scripting is definitely a language to learn on its own.  When we are in class it seems to make so much sense and seems easier to me, but when I try to do things on my own I seem more lost.
+As far as working on my own, I couldn't stand trying to do thing that I wanted on certain operating systems, due to their stance on not allowing proprietary software.  I wish I could do more on the desktop I currently have, but my hardware seems to restrict me.
+====December 7, 2015 UNIX====
+After finishing sfp0, I can comfortably say that I am almost a little bit comfortable with scripting.  I may be giving myself less credit with respect to my current knowledge of bash scripting, but that project was a doozy.  As I have stated in previous opus entries, my knowledge in bash was no where near a level that I feel like it should be at.  After this project I am a little closer to that marker for myself.  I pretty much waited until the last minute to cram my head full of bash knowledge.  Luckily, I finished on time and had a working script.  There are definitely better ways I can approach problems, but giving myself enough time to successfully attempt a more efficient, but complex solution is important.  I cranked out over 200 lines of bash script in order to meet the requirements, and I feel like that is almost counter productive.
+After looking at the end of course experience, I am glad that I took the last assignment as serious as I did.  It looks like that is a significant portion of our final project set.  I will probably go through all the previous projects as well in order to refresh myself.  At this point I am one hundred percent confident that I can successfully complete all of the personal portions.  The part that makes me a little more nervous is the in person assessment.  Mostly due to the fact that it is unknown in terms of what we need to do before we start it.  Also, the fact that we can not use any resources to aid us, and to act as a buffer is a little nerve wracking.  All in all, I am confident, though.
 ====September 7, 2015 C Prog====
@@ Line 76: / Line 102: @@
 At the end of the day, I am getting a lot more comfortable with the mindset of looking at a problem, and breaking it down into smaller pieces, and working through one thing at a time. Before, I would just rush and half way understand something, before trying to implement it further, into something I barely understood.  That, as well as finding patterns in order to implement a solution to a problem, make me confident that I am heading in the right direction, mentally, for this course.
-====October 5 C Prog====
+====October 5, 2015 C Prog====
 This past week we have looked at functions again, and in greater detail.  I've been toying with the idea of continuing a previous project that I had worked on.  That being a casino sort of program.  Since we have learned functions now, I feel that it is a lot more feasible.  However, when I plan it out before taking it to my keyboard, I feel like it would be more beneficial, especially for my sanity, to wait until we go over creating our own libraries in order to accomplish this program.  There are a lot of moving pieces that need to go into it, and I'm excited to soon reach a point where I can make a dynamic program.
@@ Line 99: / Line 125: @@
 The next project however, seems like it really stepped up difficulty wise, to me at least, compared to our other projects thus far.  We have to create our own functions to solve a problem.  Going into it, I cruised for a good hour knocking things out.  I was set, and I was excited that everything was going so well.  I created my first function within it, then a second extra one, outside of the recommended ones.  I was on a roll.  That is until I was creating a pointer function.  I'm not really sure how you say with they are.  I was using one to create an array, not realizing while I was doing it that you can only return one thing from a function.  So if you want a function to create an array, in order for it to run smooth during compile time, you have to point it to the first memory address that you allocated and filled with a value, in order to return the correct values from the function.  Prior to this project, and this major learning experience that came with it, I was still apprehensive about pointers.  I understood that at a conceptual level.  But at this point, I am comfortable with implementing them in my programs.  That is most likely until the next project.
+====November 2, 2015 C Prog====
+We delved into C++ in further detail this week, and looked at classes with respect to parent and child classes.  The syntax is beginning to make a little more sense to me, as far as utilizing classes.  I feel like I need to do a project that uses them more in depth to really understand how to do it on my own.  We went into public, protected and private with respect to those things.  I learned that children classes, and nothing else can access the private parts of the parent class.  When I was attempting to learn C++ over the break we recently had, I was following a tutorial on recreating a game called CaveStory.  Through this I was introduced to classes and header files and how to utilize them after creating them myself.  Also, calling classes through the syntax "Graphics::graphics", and utilizing pointers like "this ->" didn't make sense to me at first.  I didn't really understand what I was doing.  So I stopped doing that and decided to wait until we started c++ in class to get a better understanding of what I was doing, so that I could actually learn from it and attempt to recreate another instance of it.  After being introduced to those concepts in class I am a lot more comfortable utilizing that syntax in practice.  I am excited to learn more about it and expand my knowledge.
+As far as projects go, I am not worried about the current one due on wednesday, with the encoding and decoding, and I have written a similar program before during the problem solving final exam.  And a Caesar Cypher, which is what we are utilizing, in my opinion is not that difficult to implement.  This is speaking from the perspective of having just finished the other project that is due on wednesday, where we utilize functions and pointers to implement an algorithm to solve a specific subtraction problem from left to right.  After I got the core concepts of pointers and their utilization in function definitions, work resumed smoothly.  At the end of the project I was getting stuck with the input not being registered when the value was over 10 digits long.  It would stop counting after that and just say that 10 digits were entered.  I figured out that I was using the percent d modifier, rather than what I was supposed to, with the percent ul modifier for unsigned long int.  After I corrected that, the program ran correctly for every input value I gave it for up to 18 digits.  So I am confident that I will get full credit for that assignment.
+====November 9, 2015 C Prog====
+I definitely should not have underestimated this project that is due in two days.  Firstly, I completely overlooked the fact that we are required to use fgetc() to grab characters from stdin or from a file, instead of fscanf() which is what we have used all semester up until this point.  So far, fgetc() has no problem grabbing characters from a file and terminating, but when I use it on the command line, it grabs the characters and prints them out like I want it to, but it just prompts me to write more, rather than reading a null terminator character, which would be ideal for it to do.  That is currently where I am stuck, which is lame because that is relatively early in the project.  However, I have figured out what algorithms I am going to implement in order to accomplish a the required task of a Caesar Cipher.  At least, I certainly hope so.  I will probably have to fix quite a few logical flaws when I get to that point.
+On my own time, I am taking another look at the Cave Story game that I was attempting to recreate in C and C++.  After going over syntax changes, that aren't really that different from what we have been doing in C, I feel a lot more comfortable tackling this task.  I understand now more than ever how important baby steps are when you're trying to create something that is large.  Certainly more large than what I have been exposed to thus far.
+====November 16, 2015 C Prog====
+I ended up finishing the sam0 project on time.  When it came down to it, I was not sure that I would be able to do it.  At first I was looking to attempt to implement functions and solve it that route, but I ended up breaking it in to too many functions to do.  That project taught me that sometimes, especially for some things that can be solved in only a couple logical steps, don't need four functions to operate.  I got it nailed down eventually into the main function.  The only thing that I found wrong with it was that instead of using ctrl D to exit out, it segmentation faulted on ctrl D.  This worked for me.  That was the only way I could get it to work for me, and at the end of the day, the main problem the program was sought to solve, was successful.  I was happy with myself also, because of an algorithm that I figured out, that worked with the issue at hand.  I modified my basic caesar cipher algorithm to allow it to go in a negative direction as well.  This was the first time I had figured something out on that scale myself on paper.
+For the project that is due this week, as usual I feel like it should be working, but it seems not to be.  I think that I need to learn the functions that I am attempting to use.  Once I get clarification on them, I am certain that the logic and code, for the most part, will be correct as is.  It has been interesting learning how to look at programs with regards to handling bytes that make it up, rather than the ASCII content that makes it up. This introduced me to several new ways of thinking in regards to solving problems when dealing with files.
+====December 7, 2015 C Prog====
+I have done a lot with respect to programming in C and C++ over the past two weeks, especially over the break week.  I find the projects that we have for this class almost easily do-able, and I am really happy with where I stand, at least as far as C goes.  Over the break I resumed recreating the game CaveStory in C++.  This time though, I actually understood, for the most part what was going on.  At this point I am just going through a guided tutorial of sorts, as I do not know the least in structuring a major project, especially a game that renders images the screen.  As of now, I can get a character from the sprite sheet I have to run around fluidly on the screen, with a refresh rate established in the window I have created.  I am working through getting the background and levels rendered behind the character.  The biggest thing I have learned aside from the programming knowledge, is that even the most simple ideas, can take a long time to flesh out, and be multitudes more complex than they originally seem.
+As far as the end of course experience goes, I am more than confident that I can complete the projects without too much hassle.  That includes the in class portion where we can not use outside resources.  I guess all of the time I put into this course throughout the semester has paid off.  I feel that I actually understand and can apply what I have learned in this course much more so than others due to my passion for learning and being completely interested in the material.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools