calkit-python 0.2.1

Reproducibility simplified.

Calkit

Calkit simplifies reproducibility, acting as a layer on top of Git, DVC, Zenodo, and more, such that all all aspects of the research process can be fully described in a single repository.

Why does reproducibility matter?

If your work is reproducible, that means that someone else can "run" it and get the same results or outputs. This is a major step towards addressing the replication crisis and has some major benefits for both you as an individual and the research community:

1. You will avoid mistakes caused by, e.g., running an old version of a script and including a figure that wasn't created after fixing a bug in the data processing pipeline.
2. Since your project is "runnable," it's more likely that someone else will be able to reuse part of your work to run it in a different context, thereby producing a bigger impact and accelerating the pace of discovery. If someone can take what you've done and use it to calculate a prediction, you have just produced truly useful knowledge.

Why another tool/platform?

Git, GitHub, DVC, Zenodo et al. are amazing tools/platforms, but their use involves multiple fairly difficult learning curves. Our goal is to provide a single tool and platform to unify all of these so that there is a single, gentle learning curve. However, it is not our goal to hide or replace these underlying components. Advanced users can use them directly, but new users aren't forced to, which helps them get up and running with less effort and training. Calkit should help users understand what is going on under the hood without forcing them to work at that lower level of abstraction.

Installation

Simply run

pip install calkit-python

Cloud integration

The Calkit cloud platform (https://calkit.io) serves as a project management interface and a DVC remote for easily storing all versions of your data/code/figures/publications, interacting with your collaborators, reusing others' research artifacts, etc.

After signing up, visit the settings page and create a token. Then run

calkit config set token ${YOUR_TOKEN_HERE}

Then, inside a project repo you'd like to connect to the cloud, run

calkit config setup-remote

This will setup the Calkit DVC remote, such that commands like dvc push will allow you to push versions of your data or pipeline outputs to the cloud for safe storage and sharing with your collaborators.

How it works

Calkit creates a simple human-readable "database" inside the calkit.yaml file, which serves as a way to store important information about the project, e.g., what question(s) it seeks to answer, what files should be considered datasets, figures, publications, etc. The Calkit cloud reads this database and registers the various entities as part of the entire ecosystem such that if a project is made public, other researchers can find and reuse your work to accelerate their own.

Design/UX principles

1. Be opinionated. Users should not be forced to make unimportant decisions. However, if they disagree, they should have the ability to change the default behavior. The most common use case should be default. Commands that are commonly executed as groups should be combined, but still available to be run individually if desired.
2. Commits should ideally be made automatically as part of actions that make changes to the project repo. For example, if a new object is added via the CLI, a commit should be made right then unless otherwise specified. This saves the trouble of running multiple commands and encourages atomic commits.
3. Pushes should require explicit input from the user. It is still TBD whether or not a pull should automatically be made, though in general we want to encourage trunk-based development, i.e., only working on a single branch. One exception might be for local experimentation that has a high likelihood of failure, in which case a branch can be a nice way to throw those changes away. Multiple branches should probably not live in the cloud, however, except for small, quickly merged pull requests.
4. Idempotency is always a good thing. Unnecessary state is bad. For example, we should not encourage caching pipeline outputs for operations that are cheap. Caching should happen either for state that is valuable on its own, like a figure, or for an intermediate result that is expensive to generate.
5. There should be the smallest number of frequently used commands as possible, and they should require at little memorization as possible to know how to execute, e.g., a user should be able to keep running calkit run and that's all they really need to do to make sure the project is up-to-date.