blog:spring2016:mbeard2:journal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| blog:spring2016:mbeard2:journal [2016/04/05 03:53] – [April 4, 2016] mbeard2 | blog:spring2016:mbeard2:journal [2016/04/28 03:21] (current) – [April 20, 2016] mbeard2 | ||
|---|---|---|---|
| Line 40: | Line 40: | ||
| ====April 4, 2016==== | ====April 4, 2016==== | ||
| Well another week of c programming and yet there is a lot more to learn. Using the work that we had done in class, I figured out a way to implement the encoding and decoding function into a working c program, but unfortunately I could never get the arguments to work correctly. Using arguments is something that I really need to work on for sure. In class I think I understand using arguments, but once I have to use arguments for a project I get all screwed up and leave myself with a code that does not quite work all the way. This last project was called Secret Agent Message and it intended to write a code that, given the right argument, would encode a message and also decode the message if prompted to do so. The only thing that I got to work was the encoding and that only worked half the time. It had to do with the arguments which probably were not right at all. I was getting it to encode just fine but when I added the arguments I was getting a lot of errors and it left me stumped to where I just submitted the project as it was without getting it completely right. In class we went over making our own classes and working on a little bit of c++. We really just talked about how it worked, but never really got to writing much code. It is obvious that the projects are going to get more difficult and I have to take the time into learning how to use arguments as they should be. Our new project I have looked at and worked on, but not much has been accomplished though. A lot of errors on just the first couple parts of the code. I can never sit and write the whole code. I take the time to piece it together which works some of the time for me. This new project is going to be a tough one, just like the others, but it is going to take a lot of time and persistence to get it up and running like I want it to be. More stories of LAIR next week... | Well another week of c programming and yet there is a lot more to learn. Using the work that we had done in class, I figured out a way to implement the encoding and decoding function into a working c program, but unfortunately I could never get the arguments to work correctly. Using arguments is something that I really need to work on for sure. In class I think I understand using arguments, but once I have to use arguments for a project I get all screwed up and leave myself with a code that does not quite work all the way. This last project was called Secret Agent Message and it intended to write a code that, given the right argument, would encode a message and also decode the message if prompted to do so. The only thing that I got to work was the encoding and that only worked half the time. It had to do with the arguments which probably were not right at all. I was getting it to encode just fine but when I added the arguments I was getting a lot of errors and it left me stumped to where I just submitted the project as it was without getting it completely right. In class we went over making our own classes and working on a little bit of c++. We really just talked about how it worked, but never really got to writing much code. It is obvious that the projects are going to get more difficult and I have to take the time into learning how to use arguments as they should be. Our new project I have looked at and worked on, but not much has been accomplished though. A lot of errors on just the first couple parts of the code. I can never sit and write the whole code. I take the time to piece it together which works some of the time for me. This new project is going to be a tough one, just like the others, but it is going to take a lot of time and persistence to get it up and running like I want it to be. More stories of LAIR next week... | ||
| + | ==== April 20, 2016 ==== | ||
| + | Well it seems that I missed my last opus entry, but that was the first one I missed so whatever. This past week we worked on a grade figure outer in both c programming and unix. I've been working on trying to figure out how to get everything started correct. I had some code written and it just was a mess so its time to start from scratch and hand it in late. We have the end of semester experience coming up so i am sure there will be a lot of confusion and work to do in the near future. Grade figure outer is supposed to take all the info from the " | ||
| + | ====April 27, 2016==== | ||
| + | Well its the time of the year that we have all heard about. It is now the end of the semester experience where we have multiple projects that span what we have learned entirely throughout the course. The projects are an assortment of different ideas, but ideas that we are able to tackle from our knowledge in class. Now we are not required to be in class because there is no more teaching to cover but now class time is dedicated to working on our projects. I have a rough start on a couple of the c programs, but none are working properly. This last project is a bit stressful because I have two big projects for two classes. Both c programming class and unix have this EoCE that have to be finished but hopefully with a lot of time, the projects will sort themselves out. Next week I plan on being in both classes to get a little help on projects and break through a few barriers I am having with certain projects. This could potentially be the last " | ||
| ======UNIX/ | ======UNIX/ | ||
| ====MONTH Day, YEAR==== | ====MONTH Day, YEAR==== | ||
| Line 77: | Line 81: | ||
| ====April 4, 2016==== | ====April 4, 2016==== | ||
| This last weeks project was another example of the udr projects. This one was a lot more difficult than the last one and really emphasized using the mtools to gather information. It was not very easy to figure out how to use the mtools correctly but the most important one was the mdir which is kind of like using the file command in unix. It told you what the file consisted of and all the parameters. Mdir was a life saver when first trying to use mtools effectively. Just like the last project, dd was a very useful and powerful command to take a specific part of a file out and create its own file. Using dd more shows how useful it is and it shows how it can be used in many different ways. Our next project is udr2 which looks very difficult and will definitely take a lot of time, because we are looking at sleep patterns. Although analyzing sleep does not seem that exciting, finding way to sort the information and understand it will make things go a lot smoother in the project. These udr projects are getting very difficult and very time consuming. I guess that is how most projects will be from here on out. We are learning more and more about this crazy unix system, but now a few things are easier and showing me how much more there is to it, making it very difficult. There are so many commands to memorize and most the time you have to refer back to the manual pages to remember how to use them correctly. Hopefully this week in class we can get a few hints on how to tackle this udr2 project and learn how to use this file system better. There is a lot of stuff to do and learn. As you think you know how to do something, you find many ways how to do it the wrong way. More information in the upcoming weeks... | This last weeks project was another example of the udr projects. This one was a lot more difficult than the last one and really emphasized using the mtools to gather information. It was not very easy to figure out how to use the mtools correctly but the most important one was the mdir which is kind of like using the file command in unix. It told you what the file consisted of and all the parameters. Mdir was a life saver when first trying to use mtools effectively. Just like the last project, dd was a very useful and powerful command to take a specific part of a file out and create its own file. Using dd more shows how useful it is and it shows how it can be used in many different ways. Our next project is udr2 which looks very difficult and will definitely take a lot of time, because we are looking at sleep patterns. Although analyzing sleep does not seem that exciting, finding way to sort the information and understand it will make things go a lot smoother in the project. These udr projects are getting very difficult and very time consuming. I guess that is how most projects will be from here on out. We are learning more and more about this crazy unix system, but now a few things are easier and showing me how much more there is to it, making it very difficult. There are so many commands to memorize and most the time you have to refer back to the manual pages to remember how to use them correctly. Hopefully this week in class we can get a few hints on how to tackle this udr2 project and learn how to use this file system better. There is a lot of stuff to do and learn. As you think you know how to do something, you find many ways how to do it the wrong way. More information in the upcoming weeks... | ||
| + | ====April 20, 2016==== | ||
| + | Well it is time to take our scripting notes and put them into work with this last weeks project. We have to use a script to produce our current number grade in this course. There are a lot of pipes being used and a lot of loops also. I am still trying to figure out the best way to make the calculations. I know that you just need to take the data and send it to " | ||
| + | ====April 27, 2016==== | ||
| + | It is time for the EoCE to single handedly stress me out and force me to pull my hair out I am sure. We are given projects that vary in different processes that need to be done in order to complete them. I am excited that we have another puzzle box in this EoCE because they were some fun projects to complete. I am sure when I am doing that project I will not think it is fun but when it is all said in done I will be happy when it is all over. There is a lot of scripting in these projects which I struggle with, but hopefully with some research and time spent I will figure it out. I have been focusing on the c programs for now but hopefully next week i can get a few of the UNIX projects done. Well this could potentially be the last opus entry of this semester, but I have data structures and discrete structures next semesters so there will be many more opus entries in my near future. Time for the EoCE to wreck my life.... | ||
blog/spring2016/mbeard2/journal.1459828385.txt.gz · Last modified: 2016/04/05 03:53 by mbeard2
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
