As it should be. There's no point doing research if you don't publish all the relevant information. Now that journals are electronic, you can and there's no excuse not to.
If you don't know why the appendix exists, try reading it.
A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
As it should be. There's no point doing research if you don't publish all the relevant information. Now that journals are electronic, you can and there's no excuse not to.
If you don't know why the appendix exists, try reading it.
No need to rush to conclusions, I do read appendices when needed. My point is not that authors should cut the appendices or compromise on any other good open science practices. The point is that disproportionately large appendices make one wonder if some of that stuff actually belongs in the main text. If it is just a robustness check that gives a similar result, fine, make a footnote in the main text and put the analysis in the appendix. But what if it is actually relevant information that changes the perception of the main text?
Eh, "data available upon request" - fuck you, just add a table in the extra materials part. Also applies to any code written for a project.
I am doing a data analysis that has been described in another paper. Somewhat complex equations, but I managed to put them into code. Except when I use my code to reproduce figures from the paper two of five equations are off by a factor of kT/E_phonon (empirically determined by me, it's just a value that makes my plots correspond with theirs). I have absolutely no effing clue where that discrepancy is coming from. They clearly wrote code for their paper but it's not online and while I did have a pleasant correspondence with the author, they (understandably) do not have time to go digging for 10 year old code.