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

Dealing with missingness #3

Open
chadhazlett opened this issue May 5, 2017 · 2 comments
Open

Dealing with missingness #3

chadhazlett opened this issue May 5, 2017 · 2 comments
Assignees

Comments

@chadhazlett
Copy link
Collaborator

Ideally we'd deal with missingness much as lm does -- i.e. it is na.omitted internally but then the predictions etc. are put back into the full length vector with the NA intermixed.

@lukesonnet
Copy link
Owner

What about in the returned K, U, etc?

@chadhazlett
Copy link
Collaborator Author

I would propose we leave out the missingness in those objects and just keep NAs in all the fit/predict type objects. Main motive for this would be that if people are generating predictions by multiple procedures then it needs to be easy to weave them together.

@lukesonnet lukesonnet self-assigned this Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants