Timeline for Why are papers without code but with results accepted?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2014 at 19:48 | comment | added | Stephan Kolassa | +1 for essentially casting this in signal detection terms. Nice! | |
| Jun 12, 2014 at 10:52 | comment | added | cbeleites | Very good point about the difference between nice-to-have and must-have features. I recall some paper (possibly an editorial?; Unfortunately right now I cannot find it) discussing a similar problematic for standards of reporting statistical analyses. The bottomline was that basically a check list for good practice is known, and it was suggested that everyone who knows and obeys it includes a single sentence stating this (or a more minute description). The idea is that this nice-to-have strategy will push quality without the need of consensus about must-have policies. | |
| Jun 11, 2014 at 20:32 | history | answered | rumtscho | CC BY-SA 3.0 |