Writing Research Papers For Computer Science

  • Published on
    22-Feb-2016

  • View
    24

  • Download
    0

Embed Size (px)

DESCRIPTION

Writing Research Papers For Computer Science. Steve Blackburn Research School of Computer Science Australian National University. Why write?. Why Write?. The Moral Imperative. Who is paying you, anyway?. - PowerPoint PPT Presentation

Transcript

Slide 1

Writing Research PapersFor Computer ScienceSteve BlackburnResearch School of Computer ScienceAustralian National UniversityWhy write?2Steve Blackburn | Writing Research Papers | PhD Workshop May 20123Steve Blackburn | Writing Research Papers | PhD Workshop May 2012The Moral ImperativeWhy Write?Who is paying you, anyway?Scientists have a moral obligation to make their findings known to other scientists, and to professionals []Guidelines for Publication Ethics at the Karolinska Institute, 2002[] the obligation to publish research results can be regarded both as moral and epistemicstandards

Matthias Adam, in Science and Social: Knowledge, Epistemic Demands and Social Values, University of Pittsburgh Press, 2009communicate this knowledgeAs scientist and as thinkers, we share a moral imperative to communicate this knowledge, with each other, across disciplinary boundaries, and outside the academic and research spheres.

Kate Neville in The Science Creative Quarterly, Issue 6, 201134Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Where to PublishWhy Write?Communicate effectivelyThink seriously about the venueDiscus this early on in the projectIdeal venue will be sub-discipline-specificMaximize impactAim highDont fear rejectionFear of failure retards creativity and impact4Effective WritingTop Down5Steve Blackburn | Writing Research Papers | PhD Workshop May 20126Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Know Your AudienceWhat does this audience care about?What does this audience already know?

Think about the venueThink about the readershipThink about the reviewersLook at the program committee composition(It is probably not your mother)Effective Writing67Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Know Your MessageWhat have you donethat is interesting (to your audience, not you!)that is novelthat advances the field?that forms a single, coherent story?Important v necessaryInclude all that is necessary, but the focus must remain on the importantDetails of methodology etc must be reported, but in a way that does not dominate nor detract from the focus

Dont start writing until you have a single, clear, coherent storyEffective Writing78Steve Blackburn | Writing Research Papers | PhD Workshop May 2012The TitleIt is the first handle readers haveSuccinctMeaningfulIf youre lucky, memorableMake it meaningful and engagingEffective Writing89Steve Blackburn | Writing Research Papers | PhD Workshop May 2012The AbstractThis is the story of your workWrite v1.0 the day you start the projectIterate

If you cant capture your work in the modality of an abstract you probably dont know what youre doing and/or dont have enough perspective.Many people will only read your abstract...Effective Writing910Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Whats In An Abstract?With thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchEffective WritingContributionResultThis paper introduces a new context-sensitive and control-flow sensitive pointer alias analysis. We show that it is one hundred times faster than the prior state of the art.

10With thanks to Kathryn McKinley, University of Texas at Austin & Microsoft Research11Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Effective WritingProblem statementContributionResultMeaningPrecise flow and context sensitive pointer analysis is currently limited to programs with 100,000 or fewer lines of code. Pointer analysis clients, such as verification and testing, are consequently limited to small programs because they need high precision.Precise flow and context sensitive pointer analysis is currently limited to programs with 100,000 or fewer lines of code. Pointer analysis clients, such as verification and testing, are consequently limited to small programs because they need high precision. This paper introduces a new context-sensitive and control-flow sensitive pointer alias analysis.

Precise flow and context sensitive pointer analysis is currently limited to programs with 100,000 or fewer lines of code. Pointer analysis clients, such as verification and testing, are consequently limited to small programs because they need high precision. This paper introduces a new context-sensitive and control-flow sensitive pointer alias analysis. We show that it is one hundred times faster than prior algorithms and can analyze programs up to 1 million lines of code.

Precise flow and context sensitive pointer analysis is currently limited to programs with 100,000 or fewer lines of code. Pointer analysis clients, such as verification and testing, are consequently limited to small programs because they need high precision. This paper introduces a new context-sensitive and control-flow sensitive pointer alias analysis. We show that it is one hundred times faster than prior algorithms and can analyze programs up to 1 million lines of code. Future work should investigate its effects on the precision and scalability of client analysis.

1112Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Effective WritingProblem statementContributionResultMeaningPrecise flow and context sensitive pointer analysis is currently limited to programs with 100,000 or fewer lines of code. Pointer analysis clients, such as verification and testing, are consequently limited to small programs because they need high precision. This paper introduces a new context-sensitive and control-flow sensitive pointer alias analysis. Our key insight is that many pointers have the same aliases, and we show how to find and exploit this equivalence. We show that it is one hundred times faster than prior algorithms and can analyze programs up to 1 million lines of code. Future work should investigate its effects on the precision and scalability of client analysis.

and be preciseWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft Research1213Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Improving an abstractInterview the writerEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchUnderstandProblem statementContributionResultMeaning1314Steve Blackburn | Writing Research Papers | PhD Workshop May 2012The Rest of the PaperWriters (even technical ones) are story tellersEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchTell a single coherent storyLink and organize ideasRecursively at each level of the documentEmphasisEnsure your story shines throughDe-emphasize elements that are necessary but not key to the story1415Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Recursive structureWere computer scientists, after allEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchpapersectionparagraphsentenceContainers (paper, section, paragraph)StructureIntroduction, discussion, (conclusion)SentencesStructureSpecial rules for structuring sentencesLinkage of ideasStory has flowStructure reflects flow1516Steve Blackburn | Writing Research Papers | PhD Workshop May 2012The PaperEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchintroductionContainers (paper, section, paragraph)StructureIntroduction, discussion, (conclusion)SentencesStructureSpecial rules for structuring sentencesLinkage of ideasStory has flowStructure reflects flowdiscussionconclusion1617Steve Blackburn | Writing Research Papers | PhD Workshop May 2012SectionsEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchintroductionStructureComposed of paragraphs (or subsections)Introduction, discussion, (conclusion)Section titleShould be consistent with key idea reflected in first paragraphdiscussionconclusion1718Steve Blackburn | Writing Research Papers | PhD Workshop May 2012SentencesEffective WritingWith thanks to Kathryn McKinley, University of Texas at Austin & Microsoft ResearchFamiliar ideasActionNew ideassubjectverbobject18MechanicsA Laundry List19Steve Blackburn | Writing Research Papers | PhD Workshop May 201220Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Have a TemplateUse a template directory complete with defaultsInclude the common LaTeX practices you useInclude boilerplate for grant acknowlegmentsInclude a bibliographyUse a standard naming schemeMy lab uses keyword-venue-yearrc-ismm-2012, yinyang-isca-2012, etcCan be invaluableMechanics2021Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Version ControlWhy use version control?Versioning (especially for thesis!)Concurrent writingUse LaTeX and an SCM (svn, git, hg, etc)Break document into multiple filesPut tables etc. into separate filesUse the cloudGoogle docs etc.Write concurrently, leave comments, versionsWriting is a team sportMechanics2122Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Author OrderUnderstand the conventionEnsure roles are clearDiscuss it explicitlyNot something to leave to the last minute

Mechanics2223Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Spelling, Grammar & StyleEliminate passive voice whenever possiblePassivity introduces ambiguity, the antithesis of good science writingPractice, practice, practice, practiceUse available toolsReadInvite critiqueWriting errors distract the reviewer / readerMechanics23Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Spelling, Grammar & StyleCan be fun no, really.Mechanics

242425Steve Blackburn | Writing Research Papers | PhD Workshop May 2012CaptionsMake figure + caption stand-aloneCapture the insight and meaning in the caption if possibleCapture only most vital methodology in captionMany readers will only look at the picturesMechanics

2526Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Citations and BibliographyTake care to cite the appropriate work.Gratuitous citations do not impressIncorrect citations irritateMissed citations infuriateTake care with bib entriesInclude the DOI where possibleCheck the citation. Is it correct?Take special care when acknowledging prior workMechanics2627Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Feedback & ProofreadingYou will become blind to your failingsLoss of perspectiveFailure to explain key predicatesFamiliarity of own writing styleBlindness to typos, omissionsGet friends to proofreadBe open to critiqueCultivate a culture of honesty and directnessCan be invaluableMechanics2728Steve Blackburn | Writing Research Papers | PhD Workshop May 2012RebuttalIdentify key points, factor them outPoints for and points againstEnsure you address all major questionsEnsure you rebut all major concernsBe succinctBe politeBe directUse it wiselyMechanics2829Steve Blackburn | Writing Research Papers | PhD Workshop May 2012CredibilityIs your work reproducible?Does the paper contain enough information?Provide full proofsPublish as an abstract or tech reportPublish raw dataPut it on your web pageWhats the credibility of this work?Mechanics2930Steve Blackburn | Writing Research Papers | PhD Workshop May 2012IterateLearning to write well takes time and practiceYou cannot leave it to the last minuteI recommend a top-down approachAbstractStructureIteratively fill in contentStart writing early & iterateMechanics3031Steve Blackburn | Writing Research Papers | PhD Workshop May 2012Questions?Mechanics31