Organizing a technical paper

This blog actually belongs to Dr. John Hansen, my advisor at University of Texas at Dallas. He took so much pain and put in efforts to tell us all about importance of writing a technical paper.

During the regular lab meeting today, June 11, 2008, John felt an urge to talk on paper writing.

To have a snap of what he talked, please view the image on left hand side of this blog. [thanks to Leo Chang, for copying this via his camera-phone onto my machine.]

John told us to layout the paper and explore the availability of estate for your writing.

You can, also lay the different sections on the paper. remember actual writing towards it will come latter on. right now, we are just in planning stage.

The very first thing that should come to your mind is:

What is the problem statement? - what are you trying to resolve or solve. what is your intention behind the research that you are continuing.

This will be about 3-4 sentences long (max).

what is new or contribution from your side towards the solution? are you talking about implementing a new feature for the long known problem, are you talking about a different algorithm for the long known problem, or it would be knowledge discovery / probe experiment conducted by you. Be clear on this, because, if more information you have on this - problem statement - more you can expand it latter on.

John gave an example of dialect classification - so, if you say that you

outline of the paper:

problem statement: New / Contribution - Feature, Training Algorithm, Knowledge.

Introduction: Background, Issues, New, Outline (flow of the paper).
CORPUS description:
Baseline Algorithm:
Proposed Algorithm:
Evaluations
Discussions and Conclusion:

Figures (Tables) : All titles/Text should be in Arial. label the axes properly.
Tables: highlight the values important to you. specify the units for the values.