Concrete meta research - how to collect, manage, and read papers?
1. CONCRETE
META-RESEARCH
- How to collect, manage, and read papers?
Tao He
elfinhe@gmail.com
Software Engineering Laboratory
Department of Computer Science, Sun Yat-Sen University
With thanks to our supervisors: Prof. Li and Prof. Zhou
October 2011
Sun Yat-Sen University, Guangzhou, China
1/68
6. Auto Proxy for browsers
Switchy!
http://code.google.com/p/switchyplus/
Auto Switch Rules:
6/68
7. How to find first-tier
conferences/journals in a specific
research area?
7/68
8. Microsoft Academic Search
Top conferences ( find research trends)
http://academic.research.microsoft.com/RankList?entitytype=3&topDomainID=2&subD
omainID=4&last=5&start=1&end=100
8/68
9. Microsoft Academic Search
Top journals ( find evaluation methods)
http://academic.research.microsoft.com/RankList?entitytype=4&topDomainID=2&subD
omainID=4&last=0&start=1&end=100
9/68
10. WIKIPEDIA
List of computer science conferences
http://en.wikipedia.org/wiki/List_of_computer_science_conferences
10/68
11. How to get the paper list of a
particular conference?
11/68
12. DBLP (Digital Bibliography &
Library Project)
DBLP listed more than 1.3 million articles
on computer science in January 2010.
http://www.informatik.uni-trier.de/~ley/db/conf/
12/68
51. References
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
51/68
52. References
Names of authors
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
52/68
53. References
Title
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
53/68
54. References
Conference name or journal name
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
54/68
55. References
Address
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
55/68
56. References
Digital object identifier
James A. Jones, James F. Bowring, and Mary Jean Harrold.
2007. Debugging in Parallel. In Proceedings of the 2007
international symposium on Software testing and
analysis (ISSTA '07). ACM, New York, NY, USA, 16-26.
DOI=10.1145/1273463.1273468
http://doi.acm.org/10.1145/1273463.1273468
56/68
61. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release of a program. Our approach consists of a
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
61/68
62. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release of a Background
program. Our approach consists of a
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
62/68
63. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release of a MotivationOur approach consists of a
program.
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
63/68
64. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release The authors‟ approach
of a program. Our approach consists of a
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
64/68
65. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release ofinsights of thisOur approach consists of a
Brief a program. approach
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
65/68
66. Papers are written in *one* template?
Abstract
The presence of multiple faults in a program can inhibit the ability
of fault-localization techniques to locate the faults. This problem
occurs for two reasons: when a program fails, the number of faults is,
in general, unknown; and certain faults may mask or obfuscate other
faults. This paper presents our approach to solving this problem that
leverages the well-known advantages of parallel work flows to reduce
the time-to-release of a program. results
Evaluation and Our approach consists of a
technique that enables more effective debugging in the presence of
multiple faults and a methodology that enables multiple developers to
simultaneously debug multiple faults. The paper also presents an
empirical study that demonstrates that our parallel-
debugging technique and methodology can yield a dramatic decrease
in total debugging time compared to a one-fault-at-a-time, or
conventionally sequential, approach.
66/68
69. Outline
Tools
Cross the Great Wall via VPNs
Databases of publications
Local management
Everything
Note Express
Rules
Top conferences/journals
69/68
71. Skills of graduate students
Skills of graduate
students
Information acquisition Presentation (e.g. giving
Technical skills (e.g. Evaluation skills ( e.g.
skills (e.g. paper-reading, a talk and
programming, performance empirical study and
points extraction, and communication via
improvement, and validation) statistical analysis)
asking questions) emails)
71/68
72. Others
Springer Online Library
Wiley Inter Science
Elsevier Online Library
Science Direct
72/68