I’ve handled the review of > 1000 papers at @nature. Over time, you notice aspects of presentation on which reviewers tend to comment. In the interests of minimizing hassles during review, I offer the following suggestions (a bit targeted to climate papers).
Double space: make it easy on the reader (and editor) by double spacing the entire text, including references and figure legends.
Use big fonts: again, make the paper easy to read. Tracking 30 words across one line in a tiny font is hard, especially if you are reading for hours at a time. Instead, use a font that provides about 12-15 words per line of text.
Use continuous line numbers: reviewers like to refer to specific line numbers and frequently comment on their absence.
Avoid subjective wording: reviewers will often object to words/phrases like “unprecedented”, “paradigm shift”, “amazing”, “dramatic”, and “remarkable”. Best to present your results, and let the readers make up their minds about the magnitude of the advance.
Avoid acronyms: a rule of thumb might be to use an acronym if the term is used at least five times. Do use common acronyms, like SST, CDW, NPP, AMOC. Avoid, if at all possible, inventing acronyms that are unique to your paper.
Avoid words like “influence”: instead, state the direction of the effect you’re describing. So, instead of hypothetically writing “Precipitation influences net primary production” write “Precipitation increases net primary production”. Better yet, use numbers.
Avoid using “significant” to mean “big” or “major”: too easily confused with the results of a statistical text. Even if you are reporting the results of a statistical test, it’s better to report the numerical results instead. In fact, best to avoid "significantly" entirely.
Define uncertainties: probably half of initial submissions do not fully define the meaning of error bars and/or uncertainties. 95% confidence intervals, ranges, 2 sigma? Is the box plot showing the interquartile range, or something else? Tell us, in the figure legend.
Consider accessibility: try to use colors in a way that won’t create problems for the many readers with some form of color blindness (for a good discussion and design suggestions see http://www.somersault1824.com/tips-for-designing-scientific-figures-for-color-blind-readers/ …).
Avoid rainbow color schemes: see #endrainbow for discussion, much of it from @ed_hawkins. For more, and palettes:
Use divergent colors when appropriate: in an anomaly graph, it’s often helpful to set zero as white and then ramp up to two colors. For example, panel f in Extended Data figure 6 in Cody Routson’s recent @nature paper https://www.nature.com/articles/s41586-019-1060-3 …. https://www.nature.com/articles/s41586-019-1060-3/figures/10 …
Simplify figures: we often see maps with colors and contours used to display the same data. This can be confusing, as the reader may think that different datasets are being displayed on the same map. Normally, one or the other is sufficient.
Use a declarative title: reviewers (and editors) will often recommend a declarative title. Instead of a hypothetical title like “Trends in groundwater storage” try “A doubling of groundwater loss since 2010”.
Follow a template for your abstract: The abstract/first paragraph of @nature papers is fairly standardized, and it can be helpful to follow our template, even for non-@nature papers. https://www.nature.com/documents/nature-summary-paragraph.pdf …
Provide short titles for figure legends: sometimes this can be descriptive, like “Study area”. But if possible, make the title declarative, like “Habitat fragmentation increases cloud condensation nuclei” (hypothetical!).
Provide inline figures and legends: at least for the purposes of review at @nature, it’s fine to provide figures and legends as part of a single PDF, with the figures placed at an appropriate location in the text.
I know that many of these suggestions must seem blindingly obvious and I hope not to have come across as condescending (particularly as I failed to implement many of these practices when I was an academic). Hopefully at least some will prove useful!
You can follow @MWClimateSci.
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.
Enjoy Threader? Sign up.
Threader is an independent project created by only two developers. The site gets 500,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Running this space is expensive and time consuming. If you find Threader useful, please consider supporting us to make it a sustainable project.