Concrete meta research - how to collect, manage, and read papers?

945 views
865 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
945
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Concrete meta research - how to collect, manage, and read papers?

  1. 1. CONCRETEMETA-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
  2. 2. CONCRETEMETA-RESEARCH “Our professors often talk abstractly and high-level?” 2/68
  3. 3. Motivation of this talk Share research tools and experience Discover stains and pitfalls of my habits 3/68
  4. 4. How to access Internet without limits? 4/68
  5. 5. VPNs goagent  http://code.google.com/p/goagent/ “越过长城,走向世界” 5/68
  6. 6. Auto Proxy for browsers Switchy!  http://code.google.com/p/switchyplus/  Auto Switch Rules: 6/68
  7. 7. How to find first-tierconferences/journals in a specificresearch area? 7/68
  8. 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. 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. 10. WIKIPEDIA List of computer science conferences  http://en.wikipedia.org/wiki/List_of_computer_science_conferences 10/68
  11. 11. How to get the paper list of aparticular conference? 11/68
  12. 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
  13. 13. DBLP (Digital Bibliography &Library Project) 13/68
  14. 14. DBLP (Digital Bibliography &Library Project) 14/68
  15. 15. DBLP (Digital Bibliography &Library Project) 15/68
  16. 16. DBLP (Digital Bibliography &Library Project) 16/68
  17. 17. DBLP (Digital Bibliography &Library Project) 17/68
  18. 18. DBLP (Digital Bibliography &Library Project) 18/68
  19. 19. How to search a paper? (in others‟references, by author name, bykeyword) 19/68
  20. 20. Complete Search DBLP http://www.dblp.org/search/ 20/68
  21. 21. Complete Search DBLP Ranked by publication time Based on Ajax query 21/68
  22. 22. Google Scholar Ranked by relevance and citation number Show versions through different databases 22/68
  23. 23. Google Scholar Ranked by relevance and citation number Show versions from different databases 23/68
  24. 24. Google Scholar Ranked by relevance and citation number Show versions from different databases 24/68
  25. 25. What are the common researchdatabases in Computer Science? (forthe purpose of downloading full-textpapers) 25/68
  26. 26. IEEE Xplore http://ieeexplore.ieee.org/Xplore/guesthome.jsp 26/68
  27. 27. IEEE Xplore 27/68
  28. 28. ACM Digital Library http://dl.acm.org/ 28/68
  29. 29. ACM Digital Library 29/68
  30. 30. How to manage papers in local host? 30/68
  31. 31. Note Express Tortoise  http://682.116.65.75/c/document_library/get_file?folderId=1& name=DLFE-381.ppt 31/68
  32. 32. How to search papers in local host? 32/68
  33. 33. Everything Much faster than the original „find‟ tool  http://www.voidtools.com/ 33/68
  34. 34. Note Express 34/68
  35. 35. How to take notes for papers? 35/68
  36. 36. Note Express You can even copy screenshots into a note! 36/68
  37. 37. Google Notebook HTML format-copy Synchronization 37/68
  38. 38. Google Notebook Export as HTML 38/68
  39. 39. How to generate citation? 39/68
  40. 40. IEEE Xplore 40/68
  41. 41. ACM Digital Library 41/68
  42. 42. Note Express 42/68
  43. 43. ACM Ref 43/68
  44. 44. What resources can we utilize in ourlibrary? 44/68
  45. 45. Resources in our library Please visit - http://library.sysu.edu.cn/web/guest/fwzn/dzpx 45/68
  46. 46. How to get a quick preview ofterminology? 46/68
  47. 47. WIKIPEDIA E.g., „mutation testing‟ 47/68
  48. 48. How to find similar papers? 48/68
  49. 49. Keywords 49/68
  50. 50. Keywords 50/68
  51. 51. ReferencesJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 51/68
  52. 52. References  Names of authorsJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 52/68
  53. 53. References  TitleJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 53/68
  54. 54. References  Conference name or journal nameJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 54/68
  55. 55. References  AddressJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 55/68
  56. 56. References  Digital object identifierJames A. Jones, James F. Bowring, and Mary Jean Harrold.2007. Debugging in Parallel. In Proceedings of the 2007international symposium on Software testing andanalysis (ISSTA 07). ACM, New York, NY, USA, 16-26.DOI=10.1145/1273463.1273468http://doi.acm.org/10.1145/1273463.1273468 56/68
  57. 57. Homepage of authors Google it! 57/68
  58. 58. Homepage of authors 58/68
  59. 59. Homepage of laboratory We can find technical reports here  E.g. (http://swerl.tudelft.nl/bin/view/Main/TechnicalReports) 59/68
  60. 60. How to read a paper? 60/68
  61. 61. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release of a program. Our approach consists of atechnique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 61/68
  62. 62. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release of a Background program. Our approach consists of atechnique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 62/68
  63. 63. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release of a MotivationOur approach consists of a program.technique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 63/68
  64. 64. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release The authors‟ approach of a program. Our approach consists of atechnique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 64/68
  65. 65. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release ofinsights of thisOur approach consists of a Brief a program. approachtechnique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 65/68
  66. 66. Papers are written in *one* template?Abstract The presence of multiple faults in a program can inhibit the abilityof fault-localization techniques to locate the faults. This problemoccurs for two reasons: when a program fails, the number of faults is,in general, unknown; and certain faults may mask or obfuscate otherfaults. This paper presents our approach to solving this problem thatleverages the well-known advantages of parallel work flows to reducethe time-to-release of a program. results Evaluation and Our approach consists of atechnique that enables more effective debugging in the presence ofmultiple faults and a methodology that enables multiple developers tosimultaneously debug multiple faults. The paper also presents anempirical study that demonstrates that our parallel-debugging technique and methodology can yield a dramatic decreasein total debugging time compared to a one-fault-at-a-time, orconventionally sequential, approach. 66/68
  67. 67. I hope this talk will be helpful… Q&A 67/68
  68. 68. Thank you!Contact me via elfinhe@gmail.com 68/68
  69. 69. Outline Tools  Cross the Great Wall via VPNs  Databases of publications  Local management  Everything  Note Express Rules  Top conferences/journals 69/68
  70. 70. Tools 工 欲 善 其 事 必 先 利 其 器 70/68
  71. 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 viaimprovement, and validation) statistical analysis) asking questions) emails) 71/68
  72. 72. Others Springer Online Library Wiley Inter Science Elsevier Online Library Science Direct 72/68
  73. 73. Resources in our library Please visit - http://library.sysu.edu.cn/web/guest/fwzn/dzpx 73/68
  74. 74. Massive resources Please visit - http://library.sysu.edu.cn/web/guest/fwzn/dzpx 74/68
  75. 75. Open courseware 75/68

×