Use Drake for data workflows

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
data-engineering, tooling

Research direction

No files, tests, or entry points are mentioned. Start by reviewing the repository's Chef recipes and current workflow setup, then clarify the intended Drake integration and define what adoption across the project would include before implementation.

Written by the indexing model from the issue text.

Description

@hunterowens and @matthewgee : I've recently started using Drake to organize data projects, and it's amazing.

You specify and input and output data file, and then some series of shell commands that get you from here to there. It handles dependencies, so if some day in your pipeline has changed, it recomputes everything downstream.

Not only does it help with development, deployment (not to production, but running things locally), and getting collaborators up and running quickly, but it's the best form of project-level documentation I've run into. "Here's how all these files and scripts fit together into a coherence workflow or set of analyses." You guys should get everyon to use it, to save us the headaches we had at the end of last summer where we couldn't make sense of all the stuff in the repos.

Dominant language
Ruby
Stars
1
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.