If you were unethical, you could just go ahead and make up your data tho ;)
-
-
Agree and ALSO, open notebook science is the only complete, or closest to nearly complete, solution to the file-drawer problem. This is not talked about as much as it should be https://en.wikipedia.org/wiki/Open-notebook_science …
0 replies 1 retweet 4 likes -
Was just thinking the same. It needs to be solved. It's what
@LabArchives is for, and there are also other solutions for fields where people habitually keep lab notebooks. Also lab machines need to spit output into them. I can't recall anything that fits psychology workflows,1 reply 0 retweets 0 likes -
Replying to @ceptional @djnavarro and
while you can consider git + Jupyter / Rmarkdown notebooks as the solution for computational / no original data collection fields.
1 reply 0 retweets 1 like -
Replying to @ceptional @djnavarro and
http://Pavlovia.org is built on
#gitlab but for behavioural science. PsychoPy3 app has button to “sync” (which is commit+pull+push) so quietly encouraging version control in scientists that never heard of it. Would love to talk about more ways we could push this forwards1 reply 2 retweets 6 likes -
Replying to @psychopy @ceptional and
...e.g. maybe making it easier to tie git history/tags to OSF registrations or other DOIs
1 reply 1 retweet 2 likes -
Replying to @psychopy @ceptional and
That's cool. Automating commits/commit messages is a bit tricky for actually making good use of the repo/version control IMHO (unless you add one file at a time I guess). How do you navigate that? Does it ask for a message from the user or generate one based on diff?
1 reply 0 retweets 0 likes -
Replying to @o_guest @ceptional and
Yes, absolutely. Right now, when the user presses sync, they get to add a commit message to the whole set of changes but we’ll eventually make it easier to add/exclude subsets of files for logically sensible units to go with the message (as I do when writing code commits)
1 reply 0 retweets 1 like
Sounds good! 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.