Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide easy execution of data cleaning code #52

Closed
1 task
MagicMilly opened this issue Apr 9, 2020 · 5 comments
Closed
1 task

Provide easy execution of data cleaning code #52

MagicMilly opened this issue Apr 9, 2020 · 5 comments
Assignees

Comments

@MagicMilly
Copy link
Contributor

MagicMilly commented Apr 9, 2020

Goal: Make it easier for collaborators / researchers to reproduce and run data cleaning code in notebooks

Steps

  • Put everything in one repository, with README saying what needs to be done
    • Use static input data files for now, later can replace w/ downloading
    • then lets review with Tyson and Ryan re next steps
@MagicMilly MagicMilly self-assigned this Apr 9, 2020
@MagicMilly
Copy link
Contributor Author

Moving to next Sprint (binder button or other easy execution of notebook / script)

@MagicMilly MagicMilly changed the title Add binder button for easy execution of data cleaning notebooks Provide easy execution of data cleaning code May 7, 2020
@MagicMilly
Copy link
Contributor Author

Having difficulty with binder and input files, but am converting notebooks to scripts for the Data Repo, so am looking at other options that will be easy for others to use.

@MagicMilly
Copy link
Contributor Author

@rbartelme has helped me with examples of CLI arguments, working with static data living on CyVerse. This should be done by the end of this Sprint, and for Sprint 36 I can incorporate pulling updated / dynamic data into the script.

@MagicMilly
Copy link
Contributor Author

Need to talk to David about this during our 1:1 on 2020-06-08

@dlebauer dlebauer removed this from the Sprint 35 (May 25 - Jun 7, 2020) milestone Jun 8, 2020
@MagicMilly
Copy link
Contributor Author

Removing points and closing issue due to newer, more specific tickets being worked on now like Issue #109

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants