Reproducible_papers Alternatives

Similar projects and alternatives to reproducible_papers

zotero

254 9,225 9.9 JavaScript reproducible_papers VS zotero

Zotero is a free, easy-to-use tool to help you collect, organize, annotate, cite, and share your research sources.
sioyek

88 5,859 5.5 C reproducible_papers VS sioyek

Sioyek is a PDF viewer with a focus on textbooks and research papers
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
dendron

28 6,415 6.3 TypeScript reproducible_papers VS dendron

The personal knowledge management (PKM) tool that grows as you do!
org-ref

27 1,339 7.6 Emacs Lisp reproducible_papers VS org-ref

org-mode modules for citations, cross-references, bibliographies in org-mode and useful bibtex tools to go with it.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better reproducible_papers alternative or higher similarity.

Suggest an alternative to reproducible_papers

reproducible_papers reviews and mentions

Posts with mentions or reviews of reproducible_papers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-21.

Ask HN: Whats you're ideal PhD workflow
5 projects | news.ycombinator.com | 21 Aug 2021

My main workflow improvement over the course of my PhD has been making my papers reproducible. This means: I can clone a github repo and in a single command, re-run all computations, re-generate all figures and tables, and compile the final paper.
Any manual step like "resize the figure window until the proportions look good" or "run script A, then run script B", or "upload this file to Overleaf" creates an opportunity for your results (figures and tables) to become out of sync with your source code. This can cause big problems.
I use Makefiles to accomplish this [1], but the exact techniques don't matter. The main point is the end goal.
More broadly, in research it's always tempting to do things quick and dirty. Conference deadlines loom. Code bases are usually small and short-lived. But in my experience, your 4-months-later future self will appreciate tests, documentation, etc. just as much as your 4-years-later future self.
You can still be quick and dirty when it comes to project scope. This is where you get most of the speedup anyway. Go ahead write a function that doesn't handle edge cases, but add a comment about it!
[1] https://github.com/jpreiss/reproducible_papers