3 ms·
Its too bad research papers can't be organized like a git history. We'd see many forks that never end up as pull requests that are merged back to main. And prob
by notjoemama 2y ago
Its too bad research papers can't be organized like a git history. We'd see many forks that never end up as pull requests that are merged back to main. And probably forks of forks that stray too far from the founding paper's intent. It would be nice to more easily identify original versus derivative research. Maybe that solves a different problem. I like their suggestion though:
"I offer a pragmatic criterion: what makes a criticism important is how much it could change a result if corrected and how much that would then change our decisions or actions: to what extent it is a “difference which makes a difference”.
This is why issues of research fraud, causal inference, or biases yielding overestimates are universally important: because a ‘causal’ effect turning out to be zero effect or grossly overestimated will change almost all decisions based on such research; while on the other hand, other issues like measurement error or distributional assumptions, which are equally common, are often not important: because they typically yield much smaller changes in conclusions, and hence decisions."
So, 2 papers, both with data and claims.
The first is critiqued on its claim because the data, while correct with quality methodology, doesn't support the extent made in the claim. This critique is more meaningful because it changes the outcome of the paper and any decisions following its publication.
The second's claim is within the bounds of the data but there is a discrepancy in the data collection which is the source its its critique. Fixing that doesn't change the claim but may indicate more research is needed. This critique could change decisions made from publishing, but if the claim is still within the reason of the data, then likely not.
I had to think through that and I think I like it.
- aredox 2y agoGit is not a good tool for this, as history can be rewritten. Conceptually, Fossil would be the right tool. See chapter 2.7: https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki#history https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...
- scott_s 2y agoMany computer scientists could literally show you a git history. All of the papers I have written were done so in Latex, and tracked in some version control system. More recent ones have been git.
- notjoemama 2y agoReplies summarized: that already exists
- appplication 2y agoThey already are, you can form a graph of research papers based on citations. Dead ends don’t get links.