Also, on a side note, I submitted my fifth journal paper a few days back that has to do with tactical tracking for 3DLADAR applications.  When submitting it, it reminding me of a previous post of the importance of cover leters etc., and I have been getting a lot of feedback on how to respond to reviewers.  I intend to gather a few of my response letters and post a similar step by step procedure on how to effectively (and politely) respond to reviewers here soon.  At any rate, here’s the poster for the Summer School.

Till next time.

~rome

Nevertheless, this post concerns my PhD proposal examination this past Friday April 2nd, 2010.  Breathing a sigh of relief, I passed!  My projected thesis defense will hopefully be sometime in October.  Recently, I have been getting emails about certain research projects that I have worked on in the past so right now while I am taking the time to share that I passed my proposal, I thought it would be best to post my presentation online.  Note, this was done in keynote via a mac, but I am posting both the .pdf and .key files for your convenience.

Download Link:     Keynote Presentation PDF Presentation

That’s it for now, hope to post to you soon!

Best,

~rome

Hey everyone.  As the holiday season approaches, I am finding time to gather some MATLAB code that I did for research projects that were completed.  While it is already mentioned on my project’s page, I thought I point to an update that code for “A New Distribution Metric for Image Segmentation” is now available.  You can also find it on the Mathworks MATLAB file exchange.  At any rate, here’s a quick link to download the code for those that are interested.

Download Link:  New_Distribution_Metric_Active_Contour_Segmentation.zip

As always, if you have any questions or comments, feel free to ask!

The purpose of my trip was one motivated by a guest invitation to give a lecture about my on-going research in 3D visual tracking.  Of course, like traveling to conferences, it was also a time to meet fellow colleagues in the field and get a chance to visit an exotic place.  For now, I’ll just start summarizing the trip here and I’ll write a little more in-depth about the places we visited including pictures and opinions in the next post.

Day 1:

Jumping right in, my friend and colleague Shawn Lankton and I landed in Tel Aviv in the afternoon.  To our dismay, we didn’t realize how early the sun sets and how quickly it gets dark.  By the time we exited the airport, it felt like it was 9 PM (it was actually only 5 PM).  Nevertheless, we quickly rented our small and compact car, and were on our way to Haifa.  Being the “navigator” of the trip, I pulled out the maps and got familiar with the highway systems.  Here’s a quick google map look at the path we took all over Israel including the exact highways, toll roads, and places we visited during our stay.

View Larger Map

Becase we didn’t travel to all of these locations in one day, I’ll break up the trip by days beginning with our arrival in Tel Aviv. But before I do that, here’s a legend and short description of the places traveled (listed in order):

A:  Israel Airport. This is where we started. On the way back, we visisted Tel Aviv via highway 2.

B:  Haifa. This was where we were staying.  The Technion is located on the hills of Haifa, and it also allowed us to have a somewhat central position for visiting several places.  Each night except one night, we stayed in Haifa so a lot of the paths take us back here.

C:  Rosh HaNikra. This is the border between Lebanon and Israel where the Grottoes are located.

D:  Safed (Tsfat). This is a old city where Kabbalah originated from.

E:  Mt. Khermon. This is the tallest mountain in Israel and it happens to border Israel and Syria.  Interesting area since the U.N does not recognize this terrority as Israel, but is under Israeli control

F:  Tiberus and Sea of Galilee. These are historic areas that are attractive from both a tourist spot as well as historical biblical happenings.

G:  Jerusalem. Well, as our tour guide would put it, its the holiest of the … holies when it comes to cities.

H:  Ein Gedi and Masada. This was where we decided to float in the Dead Sea as well as hike up an old historic and relgious site of the Jewish people, which also happens to be located in the desert.  Absolutely beautiful.

I:  Haifa. This was where we were staying.

J:  Israel Airport. It was time to leave…

Not Listed.

Acre.  This is located on highway 4 going north to Rosh HaNikra.

Ceasera. This is located on highway 2 going south to Tel Aviv

Tel Aviv. We visited here on the way back to the airport.  Attraction as the biggest city in Israel.

Border Travels through Palestine. I was not the navigator here, but we followed our advisor through borders between Israel and Palestine.  We also passed through the area of where Amargeddon is suppose to happen (it was a peaceful agriculture field).  A bit hard to show on the map as these were smaller roads.

One thing that I will note here is that if you have ever traveled to Israel, it is quite fascinating how small the distances are from each of the major cities and even those cities that are located within Palestine.  Watching news, you sometimes get the feel that the areas are separated far apart, but in actuality, they are really close!  So close, that you can run from one city that is in Palestine to another located in Israel in less than 20 min (assuming there is no border patrol).  This was interesting for me since a major part of world conflict has to do with the state of Israel and Palestine.  Moreover, here we were driving on a highway and by using the naked eye, you could see the cities with relative ease as with neighbors in a suburb.

At any rate, since this was day 1, we finally reached the Technion and the local guesthouse.  Here’s a picture of the view from our balcony.

Day 2:

Waking up early from the mix of jet lag and with an early sun rise, Shawn and I explored the Technion.  Like that of Haifa, the university itself is built in levels on the mountainside.  The day consisted of working and meeting people and of course, we gave our lectures on the research projects that both Shawn and I are working on.  I have provided a preview here of my presentation as well as a downloadable link for those who are interested.  The main topic that I discuss is the framework of coupling 2D image segmentation and 3D pose estimation in a unified setting for the task of visual tracking.  Note:  Videos not included.

Download Link: Guest_Lecture_Presentation

Preview:

After the lectures, we ended walking by the beaches on the boardwalk of Haifa.  These beaches for me were one of the most relaxing and beautiful beaches that I went to, but perhaps this opinion is more slanted since I actually liked the city as a whole more so than others.  At any rate, let me conclude here.  In my next post, I’ll give a description of the places that we got to see and my novice travel tips for those that might be interested in visiting Israel soon!

Download Link:  Guest Lecture Invitation

Preview Invitation

At any rate, this time around, it dawned upon me of how engineering works even in the harshest conditions.  That is, whether we are playing music, or sending messages into deep space, coding theory and error correction is at the heart of designing the system.

For example, how can we transmit a message that is robust to transmision errors such as CD scratches? For now, we will assume our message consists of 1′s and 0′s.  The first step is called encoding.  In addition to just your message, encoding a message is done by appending what is known as parity bits in a unique fashion.  This results in a code word.  So why do this?

Well simply said, just because we would like to transmit a particular message over a channel, we might observe an entirely different message and code word at the receiver.  For those of you not familar with systems design, the transmitter can be considered a CD in our case and the reciever is your speakers.  The “channel” is the whole process of reading the data from the cd and interpreting it as music.  Now you can see that errors may be caused from scratches, dirt, and ware of your CD.  These parity bits that are discussed help and enable us to correct the underlying message and decode the correct data.

Lets dive right into an extremely popular coding scheme that is used, the 7-4 Hamming Code.  Here, our message is of length 4 bits (d₁d₂d₃d₄) with 3 appending parity bits (p₁p₂p₃), totally a code word of 7 bits (d₁d₂d₃d₄p₁p₂p₃).  Note, in reality, transmitted messages are much longer than our example since they are describing parts of data, i.e. track 5 of Pearl Jam “Black” on the Ten Album.  Let’s say that our message 1101.  How should we encode this?  Looking at the following figure should help us.

The 7-4 Hamming scheme encodes a message by making sure that if we input our data message into the above diagram at the specified locations, then the parity bits are added to ensure the sum of each circle is even.  Here I should note that we are using modulo 2 arithmetic for addition (e.g., 1+1 = 0, 1+0 = 1, …).  Doing so, we can then see the above message of 1101 is encoded as 1101100.  Hopefully this wasn’t bad!  Now, what happens if we transmitted this code word, but due to extraneous noise caused from our system, the message received is shown below.

We see here that our observed code word is 1111100.  The term “observed” here is important from a conceptual point of view.  That is, we have no idea of what the input code word is nor any of the system noise (we can only assume a general model for our system at best).  So how can we decode our message at the receiver with no knowledge of what the input is, but only that it was encoded via a 7-4 Hamming scheme?

One simple way is to put the code word in the above ven diagram, and see where the sum of each circle is not equal.  Doing so, one sees that the bottom two circles are not even in their sum.  But… should we flip the appropriate parity bits to be 1 rather than 0 or flip the third message bit from a 1 to a 0?  Either is a valid code word from a decoding point of view.  This means one can “correct” an error of the code word, but this code word may not be the underlying transmitted word.  This is known as a “decoding error.”  From this, the 7-4 Hamming code can be shown to correct at most 1 single bit error without resulting in a “decoding error.”  Unfortunately, there is no way around this and is dependent on the coding scheme that is used.  For the 7-4 Hamming code, if we have two or more bit errors in the transmission, the decoder may result in an error (but have a valid code). Because the decoder itself is beyond the scope of this post, I’ll refer you to this nice Wikipedia article. Also, given a coding scheme, different decoders may be used.  For example, if you use a convolution code (which can be found on my project’s page soon), one can use what is known as a Trellis Map to efficiently decode your message.  After we pass the information through the decoder, the correct code word will indeed be our transmitted code word.  While I have simplified this example and shown the use of the above ven diagram, more complex schemes will need a more powerful way of decoding involving parity check matrices (see wiki article).

Lastly, I will note that this coding scheme can only correct a single bit flip as opposed to several bits in a row, which is called a “burst error.”  So for our CD scratch example, where a scratch can be seen as several bits corrupted in a sequence, we will need to use other coding techniques in combination with the Hamming Code.

If you are interested, I have provided additional details on achieving a more efficient code via convolution codes.  This will soon be found on my projects page with MATLAB code for you to test out.  I have also written a short techncal summary that can be found on resume and publications page under “Technical Reports.  Here’s a quick link.

Journal Checklist:

1) Create a separate submission folder:
This seems somewhat trivially, but my main point here is to separate the manuscript.pdf from being editable. I have found that when I begin the submission process, I always am making minor grammatical or sentence style changes (e.g., Use “Moreover” vs. “In Addition”). There’s always something I can correct. My advice, if you get to this point, then your manuscript is ready to submit. In order from you to keep changing these details, make a submission folder and place that paper there and as the saying goes, “don’t look back.” That is until you finally get to the “approval of all documents” stage where you can view your submission online.

2) Create a cover letter:
I believe for most journals, you will need to create a cover letter identifying the paper’s title (and perhaps author list) as well as the main idea and contribution. This is pretty standard and can be likened to a cover sheet. Here’s a quick example of a cover letter that I just submitted.

Cover Letter

Please note that this is general, and check your journal guidelines to see if more information is needed.

3) Create a shortened abstract:
Now you might be able to skip this step depending on your paper, but each time that I have submitted a paper, whether it was to a journal or conference, I realized that my abstract went over the “word limit.” Ideally, an abstract should be the shortened version of the paper, but then again, it might be over by 30 words. So without distracting from the main idea, make sure that your abstract is short enough to submit, otherwise doing this on the fly can be sometimes distracting, let alone annoying!

4) Gather keywords describing your paper:
Keywords are important. It might seem that this is a minor detail in the submission process, but those few words that you choose matter alot! For example, the chosen keywords might play a factor on how the associate editor will distribute the paper amongst reviewers. Moreover, if your paper is to be accepted, other researchers in your area will usually perform a general search and these keywords aid in placing your paper corresponding to one’s search. So, take some time and choose a few sub areas that is representive of your work. This pretty much goes for conference papers too.

5) Create a summary of changes (if similar conference paper exists):
Usually, my collaborators and I tend to write to conferences before we submit to journals. The reason being is that we would like to get our preliminary results of the work out to the community, and it sets the foundation for the more important paper, its journal version (of course going on vacation to a nice place is not a bad consquence). Then again, if you decide to stick with research, I have seen some of my colleagues that prefer to just submit to journals. Nevertheless, should your journal submission be a more in depth and detail work of a similar conference paper, most journals ask for a “summary of changes.” This short one page or less document is simply a description of the extensions and changes or differences from your conference work. For example, your extensions might be to broaden a certain framework in a theoretical setting and to include more experiments. Basically, the journal paper is seen to be the more “complete” work, but you need to have differences between the two works and they must be documented and presented. Here’s my recent “summary of changes” example:

Journal and Conference Summary of Differences

One thing that I will note about this document is to be honest! I have found that some people tend to exaggerate the differences between the two papers. My advice is don’t. Be forthcoming about your research, even showing both the success and failures. I was once told that at most a person would be lucky to have a total of 3 to 5 great ideas in their lifetime. So if you feel strong about your work, let it speak for itself. Being on the side of a reviewer, I know that one thing that will annoy him or her when critique’n your paper is if you exagerate the actual accomplishments. It might sound naive, but your reviewers are human beings too and they will appreciate the full assesement of your contribution.

6) Prepare a list of reviewers:
Most IEEE journals allow you to have a “preferred” and “non-preferred” list of reviewers and associate editors. This is up to you and is not necessary to fill out, but there might be a research group or a few people who might better understand your work. You can suggest these people during the submission process so keep this in mind.

7) Submission and Copyright form:
After you proof read your current submission that is the database, its the dreaded “submit” button that everyone always thinks at least twice before hitting. However, if you are submitting to an IEEE journal, you will find out that the process does not stop here just yet, which leads to more confusion! You have one extra step, which is the online copyright form. Don’t worry, its extremely simple. All you have to do is follow the instructions and type in your name that you agree to the rights and guidelines. This beats printing the form, signing it, and faxing it over.

Hopefully, this will help you when it is time to submit your journal. In the future, I will try to discuss major revisions, minor revisions, and final acceptance submission associated with the whole journal process.