This follows post #90 rather than contradicting it.
Reading a preprint properly means doing some of the reviewer's job: methods first, then whether the analysis matches the plan, then the conclusion.
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
This follows post #90 rather than contradicting it.
Reading a preprint properly means doing some of the reviewer's job: methods first, then whether the analysis matches the plan, then the conclusion.
Sample size and pre-registration are checkable in a preprint exactly as in a paper, and they carry the same weight.
Small point, but it is the one that usually catches people.
Coming back to post #92, because the follow-up matters more than the original answer.
Retractions and corrections do not propagate well from preprint servers. A citation that was fine when made can quietly become wrong.
Picking up post #94: that is the part I would want checked first.
Two people in this thread mean different things by tracking a preprint and are disagreeing about the definition while believing they are disagreeing about the facts. Worth pausing to define it.
On post #92 — agreed on the reasoning, with one qualification.
Where a preprint's numbers are the basis of a claim being repeated here, someone should check whether the published version exists yet. That check is nearly always overdue.
What changes between preprint and publication: authors respond to reviewer comments, re-analyse data, correct errors found in peer review, and sometimes report different results from updated analyses. The published version is not the same as the preprint.
Worth one more sentence than it usually gets.
Version numbers on a preprint server matter. Citing version one of something now on version four is citing a document that has been superseded by its own authors.
I have deliberately not rounded that, because the rounding is where the argument starts.
Peer review catches some things reliably — missing methods, unsupported conclusions, statistical mistakes of the obvious kind — and misses others routinely. Knowing which is which makes preprint reading easier.
It is a small point and it changes the answer, which is an awkward combination.
A preprint with the data and code attached is frequently more checkable than a published paper without them. Reviewed and reproducible are different properties.
Post #98 and I disagree about the size of the effect, not about the direction.
Building anything durable on a preprint means committing to rebuild it. That is a reasonable trade for a fast-moving question and it should be an explicit one.
Post #100 answers the question as asked. The question underneath it is different.
Where a preprint contradicts a published trial, the prior should favour the trial. Where it extends one, the preprint can be genuinely useful.
Two sources, same conclusion, and I could not rule out that one copied the other.
Peer review as a filter: published papers have survived a review process that rejects many submissions. Preprints have not. Neither guarantees correctness, but publication history is a difference worth noting.
It cost nothing to check and would have cost something not to.
What changes between preprint and publication: authors respond to reviewer comments, re-analyse data, correct errors found in peer review, and sometimes report different results from updated analyses. The published version is not the same as the preprint.
This is the sort of thing that ought to be settled and apparently is not.
Helpful, and short, which on this subject is harder than long.
Narrowing post #104, because the general version has more than one answer.
For anyone finding this later: the short answer on tracking a preprint is that it depends on one thing, and the rest of the thread is people identifying which thing.
Everything in post #107 holds. The case it does not cover is the one I have.
Check whether it was later published: searching for the preprint's first author and keywords in PubMed might find a published version. The published version is the stronger citation if it exists.
Screening on a preprint server is minimal and is not review. It filters obvious problems and nothing more, which is what it is designed to do.
Anyone who has looked at this more carefully, please correct the record.
Say it is a preprint in the first line rather than the last. Everything downstream depends on that status and readers arriving from search will not scroll for it.
A partial answer, offered because a partial answer beats none.
Seconded. It reads as careful rather than confident, which is the right register.
A preprint that has been up for two years without appearing in a journal is telling you something, and it is not necessarily that the work is bad.
Narrowing post #113, because the general version has more than one answer.
Author track record is a weak signal and it is a signal. A group that has published carefully for years is a different prior from an unknown one.
It is worth checking rather than assuming, which costs nothing.
Posting my tracking a preprint numbers with the method attached so they can be discounted properly. Uncontrolled, unblinded, and collected by someone who wanted a particular answer.
I read post #113 twice before replying, because I had assumed the opposite.
Building anything durable on a preprint means committing to rebuild it. That is a reasonable trade for a fast-moving question and it should be an explicit one.
Not disagreeing with anyone above, just adding the bit I keep having to look up.
Post #117 answers the question as asked. The question underneath it is different.
A preprint with the data and code attached is frequently more checkable than a published paper without them. Reviewed and reproducible are different properties.
Posted with less confidence than the sentence structure implies.
This settles it for me, at least until somebody posts a reason it should not.