How to read a paper efficiently

Structure of a Journal a Journal Article

1. Title
2. Keywords
3. Abstract
4. Introduction
5. Experimental
6. Results and Discussion
   • Tables, Figures
7. Summary/Conclusions
8. References

Two-phase process

Phase 1: Surveying the Article

to see if it‘s really worth investing a lot of time

1. Read title and keywords (these are probably what got you look at the paper)
2. Read the abstract
3. Read the conclusions

Feel free to stop reading the article at any point

Phase 2: Reading the Article

1. Look at the tables and figures (including captions)

   This is really what was done in the work. This does not take much time so it is worth looking at before really getting into the details which will slow down the reading.

2. Read the introduction

   This is the background needed and why the study was done

3. Read the results and discussion

   This is the heart of the paper

   The discussion of the research results, to answer the reader‘s possible questions, and to dig out all the clues from the experimental results. This is the place to see the real kung fu.
   Even in the face of the same information, some people can mine and analyze the content, which is much richer than others.

   Only when you think that the author‘s discussion part is valuable, you really need to read the most difficult part of the paper - experiment.

4. Read the experimental

   This is how they did the work. You only get to this point if you are really interested and need to understand exactly what was done to better understand the meaning of the data and its interpretation.

   In this part, you have to read it carefully from beginning to end, and the speed must slow down and spend more time.

   From the perspective of pursuing efficiency, only truly valuable things are worth your precious time.

Research note

faintest writing is better than the best memory

do not in the PDF, you need a special tool.

reference：https://www.youtube.com/watch?v=IeaD0ZaUJ3Y

How to read a paper efficiently

原文：https://www.cnblogs.com/icodeworld/p/11043769.html