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

What should the output of this repository be? #1

Open
gwaybio opened this issue Jan 23, 2018 · 1 comment
Open

What should the output of this repository be? #1

gwaybio opened this issue Jan 23, 2018 · 1 comment

Comments

@gwaybio
Copy link
Collaborator

gwaybio commented Jan 23, 2018

In my vision, the purpose of the repository is to store the code we used for data downloading and processing, but we don't actually require a user to run it all.

We could provide a link to a versioned figshare url storing the processed datasets. Or maybe we could even build a python package to quickly fetch the data in some sort of matrix form already. We can build upon these ideas here.

Either way, I do not think its necessary for intermediate or final output files to live here.

@jaclyn-taroni
Copy link

I'm assuming that your concern is file size -- likely too big for git lfs?

We could provide a link to a versioned figshare url storing the processed datasets. Or maybe we could even build a python package to quickly fetch the data in some sort of matrix form already.

I'm down with both of these options. I think ideally we would do both rather than one or the other.

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