-
Notifications
You must be signed in to change notification settings - Fork 28
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
OLS #33
OLS #33
Conversation
return _table, _metadata, _tree | ||
|
||
|
||
def _transform(table, tree): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc string?
minor comments, 👍 otherwise |
""" | ||
_table, _metadata = match(table, metadata) | ||
_table, _tree = match_tips(table, tree) | ||
non_tips_no_name = [(n.name is None) for n in tree.levelorder() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should tree
here be _tree
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Thanks!
Thanks for the speedy feedback! I had just one question concerning the user interface. I updated the docstring in When users typically specify regressions in R, they specify something like as follows
where Now in this case, we are running a linear regression on each balance. So if there are For example, if we had 3 balances, the regression equations would look like as follows
Now, this isn't practical if there are 1000 of balances - you cannot ask the user to manually input 1000 regression formulas. Which is why that I knocked out the response variable from the equation. However, it may not be intuitive for the user that a regression is being run if no response variable is being run. One other idea that I had was maybe to put in a dummy variable like as follows
So that the user will know that the regression is being run directly on the balances. And have it throw an error if the response variable isn't specified correctly. What do you guys think? Do you think this PR is ok as is, or should we modify the regression formula handling? |
Meh, see if it actually ends up being confusing going forward and address On Wed, Aug 17, 2016 at 10:52 PM, Jamie Morton [email protected]
|
👍 Right on. In that case, all of the comments have been addressed. |
from gneiss.balances import balance_basis | ||
|
||
|
||
def _intersect_of_table_metadata_tree(table, metadata, tree): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this have returns, params, etc?
A few comments. |
👍 .... the code looks good. |
Comments have been addressed! |
Thanks @mortonjt. |
Depends on #32