DaRL Handbook
  • 👋Welcome!
  • About us
    • 🚀Vision, Mission & Focus
      • Vision
      • Mission
      • Focus
    • 💖Values
  • Team
    • 👋Meet the Team!
  • Starting steps
    • 🐦Hello, DaRL!
  • Policies
    • 🌴Code of conduct
    • 📞Communication
    • 🛠️Project management
    • 🏠Day-to-day expectations
    • 🥸Mentorship
    • 📑Paper Writing
    • 📽️Presentation
    • 🧹Paper Maintenance
    • 👔Attending Conferences
  • Resources
    • ⌚Recurring activities
    • 🖥️Computing Resources
    • 📚Readings
    • 🖌️Paper Tips
      • Paper writing tips in DaRL Lab
      • Paper rebuttal tips in DaRL Lab
      • AI for research writing
      • Rules of thumb for writing research articles
      • Writing a Short Research Proposal as a Student
      • How to read paper (video)
      • How to (actively) read a paper
      • Writing Tips for Top Conference Papers Series on Zhihu
        • Writing Tips for Top Conference Papers (Part 1): Macro Structure and Avoiding 'Hard to Follow',"
        • Writing Tips for Top Conference Papers (Part 2): Refining to enhance "readability"
        • Writing Tips for Top Conference Papers (Part 3): Rebuttal
      • How to ML Series on Twitter
      • Latex Writing: Something to know
        • Latex fonts
        • Latex de facto
        • Predefined Latex commands
      • Presentation at Conference
      • Drafting Posters
      • See Your Research Soar with Social Media
      • Scientific Pictures
      • How to Respond to Reviewers Effectively: Good vs. Bad Rebuttal Responses
    • 🧰Things you may need
    • 💡The Scientific Workflow
  • References
    • 📜References of Handbooks
Powered by GitBook
On this page
  1. Policies

Paper Writing

PreviousMentorshipNextPresentation

Last updated 2 months ago

  • As a leading author, please highlight everyone’s contribution in time (not right before paper submission) so others know they have actually contributed along the way - that’s teamwork.

    • What is considered a contribution?

      • Discussions should not be counted as contributions; implementation/theoretically sound ideas could be.

      • Same for writing - proof-reading should not be counted as contributions; actual writing could be.

    • Also, if you contributed to anyone’s project, ask them to recognize your contribution in time if they did not.

All the co-authors are strongly encouraged to when preparing the manuscripts

  • Once a plan for submission to a conference is confirmed, the (lead) student should create an overleaf and invite immediately to Hua as a co-owner of the overleaf project.

  • 14 days before the deadline, a manuscript should be ready for collaborating students to review.

    • The lead author should read the requirements (call for papers) and create a submission on the conference submission site - this is very important since some conferences have abstract submission deadlines. The submission is not necessarily an ideal version)

    • Within the 14 days, the lead author should make sure there is at least one thorough read of the manuscript per day. This could be done collaboratively by different people across different days.

  • 7 days before the deadline, the manuscript should be ready for Hua to review. At this time:

    • All typos and obvious errors should be eliminated.

    • The main form of the figures and tables should be finalized.

    • The number of pages for the main body should be finalized.

      • Page shrinking tips:

    • Based on the quality of the manuscript, Hua is likely to organize an internal paper review session with invited participants (group members, collaborating faculties, or other people).

      • One day before the review session, the lead author should send out a pdf version to everyone.

        • Invited participants have to read the papers (in a paper version) before the meeting and bring the commented papers to the session.

          • During the meeting, every participant will point out the problems to the authors.

  • During the last week before the deadline, based on the quality of the manuscript, Hua is able to provide one version of feedback per day. To make full use of Hua and the review session, the authors are expected to finish the revision within 12 hours after receiving the feedback.

  • Two days before the deadline, the authors can request Hua for additional help on paper.

  • One day before the deadline, fix all the errors and warnings in Overleaf. Sometimes the warnings include duplicate definitions of a label, this could cause wrong references for figures/tables.

  • One hour before the deadline, finish the following checklist:

  • After submission (you should submit it at least 1 hour before the deadline), download your submission from the submission site and check the following:

    • Do the pages exceed the requirements?

    • Does the appendix satisfy the requirements?

  • One week after the submission deadline, you should:

    • Write a blog when your mind still remembers it. Details can be found in .

    • Think about "what's next?" after this paper and discuss it with Hua

read the paper writing tips
https://tutoring.asu.edu/expanded-writing-support
Paper Maintaining
📑
Page cover image