Hey everyone,
This week I have managed to finish Project 2. At first, I was struggling with the contrast code, because I couldn't seem to get the "z" button to properly produce what was expected. After several trial and error I finally solved the issue. I put the draw-imgpair code in the definition for keypress for "z" which should've been imgpair before ip. Now for fractals, everything seemed to be running smoothly, until I noticed the base of the triangles would not change when I pressed the "left" and "right" keys. I couldn't seem to find the problem myself. So I decided to go on Piazza for peer/instructor help. Thankfully, a student answered my question and asked if in my sierp definition, was the size of the triangle in the [else part, "5". And it was. However, it should've been (param-base rp) for it to properly work. So I corrected the code, and voila! It was successful.
This week is the final week of school!!! Although, I'm not even excited, because of exams. I feel very unprepared. Hope everything turns out well. Goodluck to everyone!
- JHL
Sunday, March 31, 2013
Monday, March 25, 2013
Eight
Hey all,
Looks like there's just one more thing left to do for class before exams! Project 2. I haven't started yet, so I am not sure what to expect. Hopefully it will be on the same level of difficulty as last time. Wikipedia Part III wasn't as bad as I thought it'd be. Thought it would be difficult and a long process, but I found it to be fair. My task was to add and fix Wikilinks. A pretty simple task actually. Engaging the Wikipedian community was convenient, because there were many active people online willing to help. In my previous blog, I mentioned that I found the codes for Palindrome confusing and hard to comprehend. However, after last Friday's tutorial material on recursion, I managed to get a better understanding of how codes with [cond] and [else] work together.
Anyways, this week is a four-day week with Friday off due to Good Friday, so there's no tutorial this Friday. I am so relieved.. A long weekend is just what I need. Although, I'll probably end up spending it catching up on other classes that I am behind in. Sigh. Have a nice long weekend everyone.
- JHL
Looks like there's just one more thing left to do for class before exams! Project 2. I haven't started yet, so I am not sure what to expect. Hopefully it will be on the same level of difficulty as last time. Wikipedia Part III wasn't as bad as I thought it'd be. Thought it would be difficult and a long process, but I found it to be fair. My task was to add and fix Wikilinks. A pretty simple task actually. Engaging the Wikipedian community was convenient, because there were many active people online willing to help. In my previous blog, I mentioned that I found the codes for Palindrome confusing and hard to comprehend. However, after last Friday's tutorial material on recursion, I managed to get a better understanding of how codes with [cond] and [else] work together.
Anyways, this week is a four-day week with Friday off due to Good Friday, so there's no tutorial this Friday. I am so relieved.. A long weekend is just what I need. Although, I'll probably end up spending it catching up on other classes that I am behind in. Sigh. Have a nice long weekend everyone.
- JHL
Monday, March 18, 2013
Seventh
Hey all,
I was extremely busy last weekend and I completely forgot about my weekly SLOG. So I'll make up for it right now. Last week was a busy week for us CSC104 students, because of the test we had on Thursday, March 14, 2013. Unfortunately, I came down with a sickness and due to other factors related to my illness, I was unable to take the test. It got me really worried about my mark for the class and I couldn't just do nothing about it. So I found out I could fill out a Special Consideration form for missed assignments/tests, which I ended up doing. Dr. Heap was generous enough to accept the reason why I missed the test. Currently, I'm still trying to fully understand the coding for rot13 and Palindrome.. When I look at the codes, I always think of how it seems at such a more difficult level compared to what we have been learning. Coding sure isn't easy, but I'm going to try my best and grasp all that I need to know for the exam.
There's only about two more weeks of school! I'm excited for summer, but worried for exams. Hope you all are studying hard and good luck to everyone.
- JHL
I was extremely busy last weekend and I completely forgot about my weekly SLOG. So I'll make up for it right now. Last week was a busy week for us CSC104 students, because of the test we had on Thursday, March 14, 2013. Unfortunately, I came down with a sickness and due to other factors related to my illness, I was unable to take the test. It got me really worried about my mark for the class and I couldn't just do nothing about it. So I found out I could fill out a Special Consideration form for missed assignments/tests, which I ended up doing. Dr. Heap was generous enough to accept the reason why I missed the test. Currently, I'm still trying to fully understand the coding for rot13 and Palindrome.. When I look at the codes, I always think of how it seems at such a more difficult level compared to what we have been learning. Coding sure isn't easy, but I'm going to try my best and grasp all that I need to know for the exam.
There's only about two more weeks of school! I'm excited for summer, but worried for exams. Hope you all are studying hard and good luck to everyone.
- JHL
Friday, March 1, 2013
Sixth
Hey everyone,
It's been a while since my last SLOG, because of reading week. Anyways, I finished working on the very first project of the semester for computer science today. At first, I thought it was extremely complicated, especially the ball one. But after reading over the whole outline a couple of times, I realized that it was pretty simple. Most of the coding required for the ecosystems part were codes used previously in the course, such as the check-expect. I thought I completed it, but once I ran it, all it produced was a picture of a fox beside a picture of a mouse. The pictures just stayed on the screen without any other actions occurring as time passed by. All tests passed, so I'm really confused about the outcome. Oddly, the end result of the ball part was the opposite. It produced a working simulation of the stop sign bouncing off all 4 sides whenever it came in contact. However, a message pops up saying 1 out of 12 tests failed. The error was located in line 77, which was already provided in the file. I don't remember exactly what it said, but it was regarding the direction "up" and how the expected value didn't match the actual value. My goal is to find a solution to both problems before the due date.
-JHL
It's been a while since my last SLOG, because of reading week. Anyways, I finished working on the very first project of the semester for computer science today. At first, I thought it was extremely complicated, especially the ball one. But after reading over the whole outline a couple of times, I realized that it was pretty simple. Most of the coding required for the ecosystems part were codes used previously in the course, such as the check-expect. I thought I completed it, but once I ran it, all it produced was a picture of a fox beside a picture of a mouse. The pictures just stayed on the screen without any other actions occurring as time passed by. All tests passed, so I'm really confused about the outcome. Oddly, the end result of the ball part was the opposite. It produced a working simulation of the stop sign bouncing off all 4 sides whenever it came in contact. However, a message pops up saying 1 out of 12 tests failed. The error was located in line 77, which was already provided in the file. I don't remember exactly what it said, but it was regarding the direction "up" and how the expected value didn't match the actual value. My goal is to find a solution to both problems before the due date.
-JHL
Subscribe to:
Posts (Atom)