Egypt's Undergraduate Research is Rocking the WORLD!

Yesterday was my big day, I had to present both the demo and the poster. I had judges coming for SRC and for demo evaluation, and a huge load of scientists and professionals coming to check our work. I started asking new friends I met during MobiCom about the work, and got some very helpful feedback about how to present and also they gave me a heads up one some questions I'll need to answer. But they all thought the work was great.

Now it's time for presenting the work to EVERYONE!

At first people just passed me by not asking nor talking, only more people I met on earlier days. After a while I started getting people asking me about the work. After a while I got to move my poster to be next to my demo and that's when all the action started.
I had Microsoft Research people, professors, PhD students and masters students asking questions about DNIS and discussing what we've done and how we did it. The demo helped A LOT in showing them how real the work is and its significance in terms of network performance.

That's not the only news:

We are SRC (Student Research Competition)Undergrad Finalists



Being SRC Finalists we'll get to present our work to ALL of the MobiCom audience. So, ed3oly!
We're rocking the world guys!
This is to every Egyptian undergrad: YOU CAN ROCK THE WORLD TOO, JUST START WORKING ON IT
For more information about SRC check here and here

Comments

  1. UnknownSeptember 23, 2009 at 3:52 PM

    Congratulations man, and all the DNIS team 7ouda we 7abak :), you deserve it

    ReplyDelete
  2. Yasmine M. GaberSeptember 24, 2009 at 12:42 PM

    Congratulations Saeed and DNIS team. wish you the best on the final round. :)

    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