如何报告论文 下载本文

内容发布更新时间 : 2024/6/27 1:22:43星期一 下面是文章的全部内容请认真阅读。

如何报告论文:我的建议

吉 利 报告论文并非简单地朗读论文,建议你的演讲突出3个问题: (1)What is it?论文的研究主题。

(2)Why is it interesting?论文为什么值得一读,其实就是论文的贡献或创新。 (3)How is it done?论文的研究过程。

虽然以下并非一篇学术论文的组成部分,但建议你以以下内容来结束你的演讲:

(4)评论和讨论。作为一个报告者,你的任务不仅仅是报告论文,而且还要带领全班就论文的长处、不足以及其中蕴含的更广的含义进行讨论。为了更好地使全班的讨论集中起来,你可以以2、3个主要问题/争议来结束你的演讲。 (1)论文的研究主题

应该首先将论文的研究主题介绍给听众,简要阐述论文的研究背景,如果是众所周知的热点、难点问题(比如金融危机与公允价值计量、会计改革的经济后果),则无需多言,但应明确地定义论文所提出的命题。 (2)论文的贡献或创新

报告论文与写作的一个最大不同在于:应首先报告论文的主要结论,突出与前人研究的不同,就是用几句话告诉听众你将把他们引向何处。(比如“虽然之前的研究发现投资者并不关心综合收益,但在此论文中,我们将看到一定条件下,综合收益的市场反应。”) (3)论文的研究过程

你可以用回归模型、调查问卷、实验流程图等和计算机统计分析输出的图表来描述论文的研究过程,不要把论文中的细节部分都放在演讲中。(听众如果感兴趣可以在演讲结束后提问。) (4)评论

请用2、3个需要讨论的问题来结束你的演讲。这些问题可以是:论文本身的问题,你认为合适的、需要改进的;论文给我们的启示(要将论文放到整门课程,乃至你的研究生涯这个大背景中)。在这一点上,应特别鼓励听众讨论,但你应该提前准备好,提出问题来引起听众讨论。(比如在最后一张幻灯片上列出这些问题。) 其他提示:

掌控进度。对多数演讲来说,在演讲过程中不应打断,提问应在演讲结束后进行。对于这门课程宽松的讨论氛围来说,你可以选择鼓励提问或者将所有问题(除澄清之外的问题)推迟至演讲结束后回答。

表现出热情。热情和无聊都有感染性。

练习,练习,再练习。95%的工作在你进行演讲之前完成:幻灯片要按照以上所讲到的主要话题进行组织;你的幻灯片应当是整洁的,字体大,并且没有杂乱的东西;你了解每张幻灯片的要点,并已练习过如何叙述这些要点;你已经练习了整个的演讲,并解决了所有的“变数”;因为你的练习,你很自信你的演讲可以在期望的时间内进行,所以不需要赶时间或者考虑时间问题。你可以享受精心准备和展示的过程。

How to present a paper

(网络资源) 在准备一个paper presentation(别人的paper),查到了这个贴士感觉很实用

Some tips for preparing your paper presentation

First, organize your talk:

1. Read the entire paper at least 3 times.

2. You need to be able to explain the details in the paper (even the ugly tricky notation)

3. You need to be able to provide a critical analysis of the paper 4. Check out references in the related work section of the paper. (this will help you put the paper in context of a larger body of work and will help you critique the paper's results/contributions) 5. Look at Paper Reading Advice for more details. 6. Find the important ideas

7. A paper has many details but only one or two main ideas; structure your talk around these main ideas. 8. Create a Talk Outline

9. Your talk should be organized in a top-down manner.

10.You should have the following main sections in your talk:

o Introduction, The Big Picture: what, why, how, and why we should care (motivation). Be sure to include:

? a statement of the problem being solved (what) ? motivation and putting the work in context (why and why

should we care)

? a high-level view of the author's solution (how) o Details of solution

o Results demonstrating/proving their solution

o Critic of Work (possibly compare to related work) o Conclusions & Future Directions for this work The talk should be organized as the important ideas first, the details second, conclusions last. Each section of your talk should be organized in a similar manor: high-level important points first, details second, summarize high-level points last. If the paper is well written, you can use the paper's organization as a guide.

Next, Design your slides

1. Slide Organization

2. Your slides should be organized like an outline--a few main points, with sub points under each one.

3. Your slides are a guide for your talk not a word-for-word copy of your talk. List specific points that you want to talk about as sub-topics of each main topic. If there are particular details that you want to discuss, outline them on the slide and keep written notes for you to refer to in your talk rather than writing all the details on the slide. 4. Summarize Main Points

5. You should have a summary slide of the main ideas at the end. 6. If applicable, Include a list of open questions from the paper 7. It is okay to waste space 8. Add just enough prose prose to present the main points and highlight the main parts of each point. Use phrases rather than complete sentences and use large fonts. You can use acronyms and

abbreviations sparingly, however you should say the complete name when you talk about about them. For example, if you abbreviate processes to procs on a slide, say \when you talk about the point not \Similarly, if your create an acronym for your super fast multi-cast implementation SFMC and refer to the old slow multi-cast implementation as OSMC, then say \

multi-cast\\The exception is for well-known acronyms such as PVM, MPI, API, JVM, etc.

9. A picture is worth a thousand words

10.Use figures and graphs to explain implementation and results. It is very hard to describe a system implementation without having a picture of the components of the system. I once attended a talk about Intel's I64 architecture where the speaker tried to discuss the details of the layout of the chip and the interactions between the components without having any figures. It made for a very bad talk and a very hostile audience. 11. Number of Slides

12.As a general rule, it should take 2-3 minutes to talk through the material on one slide, so for a 45 minute talk you should have about 20 slides.