DNIS in SRC: Second Place but What a feedback!

I couldn’t blog about what happened in the presentation right after it because I had places to go and things to do on my last day in China but in short it was amazing.
I asked my new friend Ari to record it in video for me and he did. As you’ll see I was terrible. I was tattering and I paused for a very long time searching for the word ORDER in my head. The bottom line I have not been worse in a presentation. The explanation is simple; my knees were shacking of fear. I was so nervous and I couldn’t help it. As I went last I got to see how all the judges asked questions and how hard these questions were. Also I got to know who the judges were and that made me even more nervous. So at the beginning I was pretty bad but I did good I think in the questions.
Even before the results were announced I knew that we’ll come second as the other guys, no matter how terrible he was on his presentation had some really solid Game Theoretic proofs behind his work and our idea was fairly simple. I was a little sad because I knew I could do better in my presentation and so I went to ask prof. Suman (posters Co-Chair and one of my judges) about my presentation and he told me that the judges liked it a lot but the idea of our project was fairly simple. Also I got to meet prof. Romit afterward and he encouraged me and told me he liked the presentation. That really meant a lot for me coming from those professors.
We came in Second in Mobicom’09 SRC Undergraduate Category. I am really proud of what we’ve did and I hope that we (as in Egyptian students) will have more of this kind of representation in major conferences in the following years

Comments

  1. AnonymousOctober 7, 2009 at 11:40 PM

    Congrats! don't worry about the idea being simple, simple ideas can be extremely powerful. Keep up the good work
    M. Sayed

    ReplyDelete

Post a Comment

Popular posts from this blog

Integrating Click Router and GNURadio

Recently, I have been working on integrating Click Modular Router to work with both WiFi cards and USRPs to facilitate the development of cognitive radio testbeds. I am using GNURadio to control N210 USRPs . I found that developing routing hops to be interesting and worth sharing as it requires the USRP to simultaneously send and receive. This requires the transmission and reception to be on separated frequencies.  For transmission, first a client socket must be created in the click configuration code. Socket(TCP, localhost, 4002, Client true) Then, I used a thread to constantly listens on that socket and transmits the data once a new packet is received. This allows for the separation of tasks and good visibility of the transmission code. I noticed that there is a trend to include the transmission code within the main function which degrades the code readability. The thread takes as a parameter the top_block describing the data path on the USRP. class tx_th (threading.Threa
Read more

Attaching a WiFi Dongle to an AR Drone 2.0 (a.k.a. Compiling Drivers for ARM Based Devices)

Correction (4/24/2014): for your driver to work the AR Drone 2.0 you have to compile the kernel version provided by Parrot which can be found here https://devzone.parrot.com/projects/show/oss-ardrone2 One of the down sides of "out of the box" AR Drone 2.0 is that you can't control multiple drones from the same machine. Another down side is that you can't attach USB devices except flash memories and some other predefined devices due to the limited nature of the busybox deployed on the drone. To over come the first down side without manipulating the WiFi configurations of the built-in WiFi card (i.e. you don't want to mess up your new drone), you will need to overcome the second problem (i.e. install a WiFi dongle and its driver manually). In this tutorial, I try to walk you through the steps to do just that. I assume that you are working a Linux machine (seriously we are not going to compile drivers on Windows). Ubuntu is preferable ! Because the Drone has a
Read more

CUDA compilation on Linux (Makefiles)

I have been struggling with compiling complex CUDA code, with complex I mean a lot of .cu .F .cpp and .c files. I have created a makefile that can help you compile that kind of code. I'll try to give a quick view of it here explaining some parts: First you'll need to specify the CUDA path and the compilers and linkers. Here I am using gcc and g++ for .c and .cpp files and nvcc for .cu files: CUDA_INSTALL_PATH ?= /usr/local/cuda CXX := g++ CC := gcc LINK := g++ -fPIC NVCC := nvcc -ccbin /usr/bin Then you need to specify where to locate the CUDA header files : # Includes INCLUDES = -I. -I$(CUDA_INSTALL_PATH)/include # Common flags COMMONFLAGS += $(INCLUDES) NVCCFLAGS += $(COMMONFLAGS) CXXFLAGS += $(COMMONFLAGS) CFLAGS += $(COMMONFLAGS) Then you specify where to locate the CUDA binaries for linking : LIB_CUDA := -L$(CUDA_INSTALL_PATH)/lib -lcudart Then you specify the object files that the executable depends on and the name of the executable flle:
Read more