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

Get rid of .data_original #337

Open
olgabot opened this issue Aug 15, 2016 · 0 comments
Open

Get rid of .data_original #337

olgabot opened this issue Aug 15, 2016 · 0 comments

Comments

@olgabot
Copy link
Collaborator

olgabot commented Aug 15, 2016

It's confusing which dataset is stored -- .data or .data_original. It's much simpler to have a single dataframe for the user to itneract with, and then they'll know for sure which one gets saved. Right now, for study.expression, study.expression.data_original gets saved when you do study.save() but study.metadata.data does for metadata... it's confusing and easier to just assume the user has filtered their data exactly how they want already.

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

1 participant