Sharing one idea I found useful for paper writing:
Do NOT ask people to solve correspondence problems.
Some Dos and Don'ts examples below:
*Figures*: Don't ask people to match (a), (b), (c) ... with the descriptions in the figure caption.
*Figure caption*
Use "self-contained" caption. It's annoying to dig into the texts and match them to the figures. Ain't nobody got time for that! ⌚️
Also, add a figure "caption title" (in bold fonts). It allows readers to navigate through figures quickly.
*Notations*
Give specific, meaningful names to your math notations. For example, the readers won't need to go back and forth to figure what each term means.
*Which*
I found that many of my students love to use "which" in their sentences. I hate it ... because I often cannot figure out what exactly "which" refers to. Break it down into simple sentences and spell out what that subject of the sentence is.
*Respectively*
It's hard to parse which corresponds to which in the sentence that ends with "respectively" (have to solve a long-range correspondence problem). Break them them so that one sentence talks about one thing.
*Citations*
People like to use many acronyms for their methods. It may be hard for readers to memorize/match which method/dataset/metric you are referring to. Adding citations is an easy way to fix this.
*Names for notations*
When using notations in the sentences, mention their "names" as well. The readers won't need to flip through your papers to look up what these notations mean.
*Connect figures with equations, notations, and sections*
I view the overview figure in a paper a centralized hub that connects all the important equations, notations, and sections in one place. This makes it easy for people to understand how everything fits together.
*Tables*
Factorize the variants/attributes of different methods so that it becomes clear to compare one with another.
*One table, one message*
Decompose your big table so that each table conveys exactly one thing. This avoids people from having to compare results from distant rows. Having multiple smaller tables gets the point across easier. (Don't worry about the redundancy.)
*Group subfigures*
Don't ask readers to figure out the grouping (b-c) and (d-e) in the caption when you explicitly group them.
When applicable, use repetitive grammatical elements in your sentence. It helps the readers to easily parse the parallel concepts you want to convey.
*Table organization*
Merge tables sharing the same structure. Label the metric (the larger/smaller the better) with up-arrow and down-arrow so that your readers don't need to look them up.
*Shape attributes*
Leverage the shape attributes (color, thickness) to encode the message.
Also, use a deemphasized image in the background to avoid mental matching.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Writing an effective rebuttal helps answer questions, address reviewers' concerns, clarify misunderstandings, and help the AC make an informed decision.
But it takes work to write a good one. 😟
Sharing some tips I found useful. 🧵
*Start positive*
Start with summarizing all the strengths noted by the reviewers and adding quotes to provide evidence.
Remind the reviewers and AC of
"Why should this paper be accepted?"
*Neutralize negative comments*
AC and other reviewers may only see all the NEGATIVE comments you responded to.
Junior students often feel stressed before the weekly meeting with their advisors because their experiments do not go well. 😩😰😱
Some tips on why, what, and how to do experiments. 🧵
*Why? 🤔*
❌ Do an experiment to get improved performance.
✅ Do an experiment to test a hypothesis.
Many students trying to show improved results with experiments are missing the point.
Your goal of experiments should be to validate/test your research questions.
*What? 🤔*
What experiments should we do?
This involves three main steps:
1⃣ identify key research questions
2⃣break them down into baby steps
3⃣design experiments that best answer those questions