Archive for Research

Keep It Simple

KISS — keep it simple,stupid.

“Keep it simple”是一种非常有用的方法。隐藏在复杂的方法,繁琐的细节背后的想法往往是极其简单的,也正因此才显出优美。看问题就应该如此。

Leave a Comment

计算机工程专业,如何找paper?[zz]

http://zeal.haliluya.org/blog/2006/05/26/how-to-find-computer-engineering-papers/

学了几年的Computer Engineering,虽然学无所成,但是对于怎么找到专业相关的paper(尤其是电子版)还是有一点心得。今天特总结一下,供后来人参考。本文应该也普遍适用于Computer Science。

1. 搜索引擎,这个其实是最简单有效的方法了。

推荐使用:

Google Scholar

Citeseer

DBLP

Google
Scholar对每一篇paper一般能返回若干个结果,可以点开group看,默认结果通常是链接向ACM或者IEEE的Digital
Library的,是收费的。如果你的学校没有订阅的话,你是下载不了的。所以最好在group里面寻找一个链向作者主页的,实验室主页之类的,通常可以
直接下载。Citeseer里面,很多文章的电子版都直接在citeseer的数据库里,可以直接下载。DBLP本身不提供论文下载,但是相当一部分
paper是有链接指向ACM和IEEE的。DBLP的好处是对论文进行了系统的分类,按作者,按会议,按期刊等等。Citeseer主要是根据
citation来把paper串起来的。

2. ACM Digital Library

如果你所在的学校和机构订阅了ACM Digital
Library的话,那么这里是一个不错的跟踪ACM会议和期刊的好地方。因为ACM的期刊和会议一般都是该领域内最好的之一。所以,建议
Graduate
Student们养成定期到这里看最新的会议proceedings和最新的transaction的习惯,尤其是conference的
proceedings
(计算机专业重conference)。ACM因为会议和期刊并不是很多(从而也保证了相当的质量),所以分类很清晰。而且一篇paper的
citation也尽量提供了链接。

ACM Journals

ACM Transactions

ACM Conference Proceedings

3. IEEE Computer Society Digital Library

如果你跑到ieee.org,而不是computer.org,你会发现那里paper不是那么容易找。其实计算机专业的,到computer.org更容易找paper一点。这里也是需要订阅的,不是免费的。另外一方面,IEEE的会议多而杂,有好的会议,但是绝大部分会议是不如ACM的,所以在这里跟会议的proceedings一定要有针对性。 IEEE的几个magzine还是做得挺不错的,可以读读。

4. 寻找BibTeX

如果你用LaTeX写论文的话,手边备有几个地方可以找到现成的BibTeX entry还是很省事的 (平时自己一定要积累,比如没看一篇paper,都把相应的bibtex entry整理好,放进自己的bib文件)。

ACM Digital Library的每篇文章,都提供BibTeX的。IEEE则不提供。Citeseer也提供能找到的文章的BibTeX,DBLP也是。另外还有一个网站,专门收集paper的BibTeX,叫做The Collection of Computer Science Bibliographies,也是一个不错的地方。

经常需要用的就是这些了,其实不用我这篇文章,大家也都知道。 也欢迎同行们来补充一下。

Powered by ScribeFire.

Leave a Comment

Sources About DB

Database Research and Development by Area
http://www-ccs.cs.umass.edu/db/research-areas.html

University of Washington database group
http://data.cs.washington.edu/

Stanford CS346 Database System Implementation  http://infolab.stanford.edu/~widom/cs346/

berkeley CS262 Readings in Database Systems  http://db.cs.berkeley.edu/cs262/syllabus.php
http://redbook.cs.berkeley.edu/redbook3/lecs.html

VLDB2007 http://www.vldb2007.org/(点击左侧Best Paper Awards)

Powered by ScribeFire.

Leave a Comment

Resources About Research

为学之道 
http://www.jdl.ac.cn/how_to_research/index1_1.htm#0

Advice on Research and Writing
http://www.cs.cmu.edu/~mleone/how-to.html

Hints for research students http://www.virtosphere.de/schillo/research/tips.html#presentingPaper

Graduate Research, Writing, and Careers in Computer Science  http://www.cs.iastate.edu/~honavar/grad-advice.html

A Reading List for Computer Scientists 
http://john.regehr.org/reading_list/#fic

Powered by ScribeFire.

Leave a Comment

HOW TO READ A RESEARCH PAPER

HOW TO READ A RESEARCH PAPER

Spencer Rugaber

Among the questions that you should ask yourself when reading a research paper are the following.

1. What is the research paradigm that the author is using? Example paradigms are psychological experiments, formalization and theorem proving, and artifact design and construction. If the paper is part of a well established field, you should describe the field and its current state.

2. What is the problem area with which the paper is concerned? For example,”Automatic Generation of Compilers from Denotational Semantic Descriptions of the Source Code” would describe a research paper on compilation.

3. What is the author’s thesis? That is, what is he/she trying to convince you of?

4. Summarize the author’s argument. That is, how does the author go about trying to convince you of the thesis?

5. Does the author describe other work in the field? If so, how does the research described in the paper differ from the other work?

6. Does the paper succeed? Are you convinced of the thesis by the time that you have finished reading the paper?

7. Does the author indicate how the work should be followed up on? Does the paper generate new ideas.

8. Some papers implicitly or explicitly provide a new way of doing things or of thinking about problems. If your paper does so, describe the approach.

Leave a Comment