__Differences Between Papers
and Textbooks__

Reading journal &
conference papers is *MUCH* different from reading a textbook... because
papers are *written* much differently (and for much different reasons and
for much different audiences) than are textbooks. While textbooks are
written for students (readers who are likely seeing the ideas for the first
time) to provide an easily understood description, papers are written for
researchers (people who have seen and worked on these ideas for some time) to
document the author's contribution to the body of technical knowledge.
Thus, a lot of the supporting background is left out of the papers... because it
is assumed that the other researchers know it. Another thing that often
gets left out of papers is the details of how you get from one result to
another... because it is assumed that the other researchers can figure it out.

__Differences Between Journal
and Conference Papers__

There are two main differences here:

Journal papers are longer expositions than conference papers and can therefore afford to provide more detail

Journal papers are generally better written because they go through a peer-review & revision process and because they are often written as the culmination of a project (in contrast to conference papers which often are reporting on "work-in-progress") and therefore the ideas presented are often more completely worked out

__Pitfalls to Avoid__

There are two main pitfalls to avoid:

Ever-Expanding Inverted Pyramid: You start to read the paper and you are no farther into than the first paragraph and suddenly the author says something like "... the method we propose has none of the bad characteristics that limit the applicability of the method developed by I. M. A. Goodread [1]" and you immediately think "Gee, I don't a thing about that method let alone what its limitations are... I better read that before I go on." So you get that paper and you get into the first paragraph and find another reference to another paper... and so on. Given that each paper has a dozen or so references, pretty soon the task of reading theoriginalpaper has expanded into reading dozens and dozens of previous papers and you never get back to that original paper.

Gotta Know Every Detail: You are reading along in the paper and you hit one of two situations: (i) there is a step in the mathematical development that you can't seem to understand how they go from one result to the next, (ii) the author uses one of those ubiquitous phrases like "... it is easily seen that ..." but toyouit is NOT AT ALL easily seen, or (iii) the author uses the other favorite phrase "... as shown in [12] ..." and then you are back to the pyramid problem. In all of these cases there is a feeling that you can't go on reading until these details are fully understood.

__How to Avoid the Pitfalls__

The thing that you
have to realize is that you CAN read and understand __some__ of the paper
without chasing every reference and without working out every detail. Here
is how (it relies on the fact that papers are meant to be read using a
multi-pass algorithm):

The first time you read the paper: give it a quick, high-level read (don't go to any of the references and don't worry about how the math details follow). What you are shooting for here is a basic understanding of theRESULTS & CONCLUSIONSof the paper. You don't particularly care who else did what nor how the math was used to get there. For example, in a paper on a new method for emitter location you might only want to get things like "what is the signal model used," "what is the accuracy that is claimed," "what kind of processing is needed," "what statistical estimation method was used (e.g., least-squares or maximum likelihood)", "what are the main conclusions"

The second time you read the paper: After the first read you should be able to determine if the content of the paper is worth working to understand more fully. The second time through you are going to want to pay more attention to the mathematical development, but still avoid worrying about the details that aren't immediately obvious. Remember... what you should be getting out of the math is what the results sayaboutthe problem at hand - how you go from step-to-step is much less important at this point. Worrying about the "how you got there" rather than the "what it tells you" is sort of like going to see the movieJurassic Parkand spending the whole time wondering about how they made those fake dinosaurs do all that stuff BUT missing the whole plot of the movie (well... in my analogy IAMassuming that thereisa plot to Jurassic Park!). When you come out of the movie your friends are discussing the plot and you don't have a clue about that but you can sure talk about how they made the dinosaurs move! So when you see a line that says "... then by using (11) in (9) we see that..." you can just sit back and trust that the author (and the peer-reviewers) got it right and just ponder about the what the RESULT MEANS! (Of course, it is likely that later you'll want/need to get down to the details but avoid it at first)Now,

ifat this point there is a need to dig farther into the paper, THEN you can go chase the references and sit down and scratch your head over the fine points of the development

__Main Things to Observe__

The three main things from a paper that you want to be etched in your head when you done reading it are:

What signal model is used?

What assumptions were made about the signal?

What conditions must be met in order for the method and/or analysis to hold?

What ramifications do the results have on the problem?