login
Search
Fiuh, looking for this paper used as the building block in "S. K. Baruah, A. K. Mok, L. E. Rosier - Preemptively Scheduling Hard-Real-Time Sporadic Tasks On One Processor" is not that easy.
When I started to study Computational Complexity based on Oded Goldreich's book, I encountered brief explanations of big O and small o notations in section 1.1.5. So, I used Wikipedia to dig deeper which was very helpful. But, I got the true enlightment about the intuitions of big O and small o notations in the class when someone sitting beside me asked the teaching assistant (TA) about the meaning of the small o notation.
Some days ago when I wanted to edit a file having a long file name that is located in a deep subdirectory also bearing long name with Elvis 2.2.0 on GNU/Linux Ubuntu 9.04, Elvis crashed because the system's C library detected buffer overflow. Since Emacs could open the same file properly, I concluded that this is Elvis' problem.
The other day when I was working with the GIMP, I was very surprised that whenever I erased something, GIMP started to erase to transparent background. Previously whenever I erased something, GIMP erased to the background color, which was I wanted. I googled for "gimp erase to background color". But, the results were mostly the exact opposite: how to erase to transparent background. Finally, I figured out the solution myself.
When I was following the Database course in my undergraduate study, I was introduced to Entity-Relationship model, in particular, the notion of weak entity. But, having learned the notions of strong and weak entity, I always wondered whether or not I should model an entity as a strong or weak entity when both were possible.
I was following a step-by-step instruction of making a ramfs to be run on QEMU's ARM machine. The instruction says that the ramfs is to be created from BusyBox's _install directory with the following command: "find . | cpio -H newc -o | gzip > ../ramfs.img". But, after reading "info cpio", I decided to change "find ." with "find . -depth", which is considered a good practice to avoid problem with strict directory permission during cpio extraction since the directory permission is only set after all files inside the directory are copied into the directory. However, running qemu-system-arm, the kernel panics saying that it cannot mount the root filesystem as follows:
I was using octave-mode in Emacs when I found a little inconvenience when editing an Octave function name that has underscores in it, for example, "C_square_exp". Specifically, when I wanted to change "square" to "triangle" when the cursor is after the last character, pressing Alt+B made the cursor jump to the first character instead to the character after the last underscore.
For this week, the course on Agent-oriented Software Engineering (AOSE) was taught by a post-doc student named Amit Chopra. Chopra presented his PhD dissertation topic on the interaction in a multi-agent system (MAS) based on the concept of commitment. It was very enlightening and gave me the key to understand the advantage of Agent-oriented Software Engineering over Object-oriented Software Engineering.
About 1.5 years ago when I were with my friend in his office in our alma mater university in the evening, I tried to tap his wireless communication. With iwconfig I put my WLAN card to monitor mode and fired Wireshark. But, data packets were not received although WLAN management frames were captured. I wondered what was wrong but didn't pursue the matter further.
Throughout my undergraduate study, I had always been wanting to have a course on Artificial Intelligence. But, it was never in the curriculum. So, this course that I took in the winter semester was enlightening. But, I was baffled when it came to Knowledge Representation and Reasoning. Studying R. J. Brachman and H. J. Levesque's Knowledge Representation and Reasoning should help at this point.
This lecture actually discusses two different things that share a common ground: wireless communications. After discussing wireless transmission, the lecture goes on discussing sensor networks before discussing WLAN (IEEE 802.11) technology in details. The discussion on sensor networks is a broad overview while the one on WLAN technology is a detailed one.
This course is very interesting for me because of two reasons:
1. I unwittingly studied a formal method.
2. I smoothly got introduced to automata theory.
I took this lab in my first semester. This lab was very interesting through which I had the chance to experience remote development via SSH and to fiddle with OpenWRT running on an ASUS router, Nokia N810 and Android phone.
All of my stuff related to the lab can be found at https://docs.google.com/leaf?id=0B66kEP2FWgm_N2I4ZmUxM2YtZDJhNC00N2ZkLWF...
This course provides an overview of microcontroller hardware using ATMega16 as a reference, FPGA and VHDL, programming languages of PLC, buses (I2C, CAN, FlexRay and Profibus) and bit encodings (NRZ, differential NRZ, Manchester code and the like), real-time scheduling, and finally, embedded system development process. The course is interesting as it really throws light for newcomers in the area of embedded systems. I wish my compulsory business course in the undergraduate study had been replaced by this one.
This lecture throws light on the safety and reliability aspects of engineering.
My lecture notes and the exam can be downloaded from http://docs.google.com/leaf?id=0B66kEP2FWgm_MDY5YzA0NmMtMjMyZS00YzNkLTkz...
The lecture materials can be downloaded from http://docs.google.com/leaf?id=0B66kEP2FWgm_ZjRlM2FkNDAtMzQ4ZC00MTFiLTlk...
