I don’t really know what to feel for my results this semester.
GE2215: S (originally B-)
CAP: 3.75 (3.7 if using B-)
Will you look at that, straight B’s.
In my post for the previous semester, I mentioned that small class sizes result in very competitive bell curves. Once more, for the third semester in a row, I believe this to be true. I also did mention that I did not want to take GIS anymore. But why is there a Geography module up there on the list, and it’s actually GIS related?
I. HAVE. NO. BLOODY. IDEA.
Why on Earth did I take it? Now I cannot even S/U it (changing the grade to satisfactory, thus contributing nothing to your CAP) because I locked in my minor to the system (and why did I do that too?). If I could S/U it, my CAP would increase by a whopping 0.05. ONE stupid module results in a decrease in 0.05 CAP. Just great.
Edit: Good news! I managed to get the staff members to manually drop the minor and S/U it for me.
I don’t think I even need a damn GIS minor to work in the GIS industry. Computer Science degrees can get into the GIS industry just fine. I’m definitely dropping GIS next semester, since GE2215 has:
1. Confirmed that GIS modules have a terrible bell curve
2. Shown me what GIS really is (boring and trivial). GE2227, which was the cartography module, was all about the design of maps. I found that fun, but that is not what GIS is about. Very misleading.
Now, on to an analysis of each module.
CS2010: This is a follow up from CS1020 and CS1010 from the previous two semesters. It goes on to teach more complex data structures and algorithms. These include trees, graphs, shortest path algorithms, and dynamic programming.
I have to say, this module was the only module whose grade did not surprise me at all. I did average in all the assessments given, so I got an average grade.
What went wrong: I did not manage to do the last task of every single programming assignment for this module, so I only got 10/15 for those. I also seemed to have messed up quite a few questions in the finals.
What went right: My second midterms. I got 43/50 for that, well above average, and above the 75th percentile.
CS2105: This is an introductory module to networks. They teach you basic network programming, and the five network layers.
This module did better than expected. Here’s why:
What went wrong: The programming assignments made up 20% of the grade, and for the first assignment, I did very poorly. I failed eight out of ten test cases. I seemed to have submitted the wrong file, or some other mistake somewhere. I do remember getting it to work properly, but my submission did not. My grade for this assignment was far below average.
My second assignment was better, but still not good enough. It was slightly below average.
What went right: My third assignment though, I aced it by getting 140/140. For some reason, they did not release the averages for that assignment, so I do not know if I did well in comparison or not.
My midterms were above average by 1 mark, and I have to say that my finals weren’t too poorly done either.
CS3241: This is an introductory module to computer graphics. They teach you basic OpenGL programming, and stuff like scanline conversion algorithm, anti-aliasing, ray tracing, shading, texture mapping, binary space partitioning, etc., but mostly only in concept. Only texture mapping, shading, and Bézier curves were actually implemented on our own.
I really enjoyed this module. I also expected an A- for it, at the very least, a B+. Getting a B was really a rude shock for me.
What went wrong: Not too sure. Probably the finals? There was a question on recursion, so I might have messed that one up completely. Then we had to implement the De Casteljau’s algorithm, which I had barely any idea how to, so that was also messed up. But I did everything else in the finals correctly.
What went right: Everything else. All my five lab assignments had a decent grade, and one of them was above the 75th percentile. My midterms were above the class average by 5 marks or so.
Why only a B? Sigh.
MA1521: One of the three compulsory Mathematics modules that I have to take. It is mainly calculus, series and sequences, and integration.
I was really lucky to be able to take this module this semester. Why? The usual lecturer for this module had something on, so a different lecturer taught this module this semester. The usual lecturer offers no webcasts (terrible for someone so weak at Math), and apparently his solutions and concepts come from “magic”.
What went wrong: My midterms were about 3 marks below average, and my finals were terrible. I was expecting to just pass the finals, or in the worst case, fail it. I was rather disappointed after the paper, since I did feel rather prepared. The finals were quite a rude shock. I was hoping for at least a B+ before the finals, but a B is not too bad considering the finals.
What went right: Everything else was rather average, I suppose. Also, MA1521 was preallocated to the year 1 SoC modules. Year 1’s might possibly still be chilling out, and this is their first examination in university as well.
GE2215: Intro to GIS module.
I’ve already ranted about this module above. By the way, when I said GIS is really trivial, I really mean it. Secondary school kids could do it with ease. How this is university level is beyond me.
What went wrong: Probably the finals again. However, I don’t think I lost more than 10% of the finals grade (finals make up 40% of the total grade), so a B- is rather drastic.
What went right: I got full marks for four out of five lab assignments. Then again, if I got a B-, then so did everyone else I guess.
So, CAP dropped by 0.1. If I could S/U that stupid GIS module, it would only have dropped by 0.05. The modules are now getting more difficult, so I’m not sure how I’m going to recover.
and information about the module for the benefit of all those students who do not have access to IVLE prior to registering this module.
Please note that for CS3103L, there is no need to register separately. If your bid for CS3103 is successful, you would be automatically registered for CS3103L.
Please note that the first lecture is on 16 August 2007 (Thursday) at 12 noon. Venue: C1/206
This module focuses mainly on TCP/IP protocol stack and discusses the design of various protocols in the stack, their semantics and interoperability issues including concepts behind in designing such protocols. The Internet technology protocols like ARP, ICMP, IP, DHCP, DNS, TCP, UDP, Routing protocols like RIP and OSPF, and new IP protocol version IPv6 are discussed in detail. The dynamics of the TCP protocol is discussed in detail including congestion control and its behaviour in the wireless and mobile network environment. The client server communication paradigm is introduced and students are given the opportunity to develop distributed application using sockets and/or RPC-XML.
Weekly Lectures of 2 hours, 1 hour tutorial, and programming assignments on client/server application development.
|EE3204/E, EE4210; EEE and CPE students are not allowed to read this module|