Two more retractions and a discussion of what we learned. 🧵

#CRAVEFiles

A researcher whose work we were examining asked our chair to investigate concerns about somebody else’s publications at the same university (different field).

Our investigation was now generating further allegations from someone already under scrutiny.

#CRAVEFiles

Last thread tomorrow at 9AM ET.

#CRAVEFiles

Previous thread: bsky.app/profile/i4re...

One of us thought it would be a good idea to check the original authors’ public git history. We found deleted data…

🧵#2

#CRAVEFiles

Our chair and a few replicators investigated a paper about elite footballers. And missed the bigger story.

An independent researcher showed us what we had failed to see.

This is I4R’s CRAVE–football investigation. It starts with a PNAS paper.

#CRAVEFiles

"We have successfully replicated our own results."

"Amazing! Can we see your data and code?”

Get prepared to see the craziest p-curve we’ve ever seen at I4R. And more duplicates.

More tomorrow at 9AM ET. #CRAVEFiles

You agree to the retraction, but "the factor structure originally reported in the article has been replicated in multiple language versions of the CRAVE using independent samples"

That’s great. Can you share the data and codes for these other articles?

🧵#3

#CRAVEFiles

We thought this was game over.

It was far from over… We found data the authors believed they had permanently deleted in the public Git history and a LOT more!

See you tomorrow at 9AM ET. #CRAVEFiles

We thought this was it. We looked at the articles with data. Some authors simply refused to share data.

Game over, right? Nope. Gets worse. Something that resembles more the plot of the Wire than I4R’s day to day email exchange with authors.

More tomorrow at 9AM ET. #CRAVEFiles