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

debug irmi #42

Merged
merged 10 commits into from
Apr 22, 2020
Merged

debug irmi #42

merged 10 commits into from
Apr 22, 2020

Conversation

GregorDeCillia
Copy link
Contributor

@GregorDeCillia GregorDeCillia commented Apr 21, 2020

close #16 and #17 by investigating the behavior of irmi() with unexpected/untested vector types

@coveralls
Copy link

coveralls commented Apr 21, 2020

Coverage Status

Coverage increased (+0.2%) to 61.961% when pulling 8156ca3 on debug_irmi into 8062003 on master.

@GregorDeCillia
Copy link
Contributor Author

@alexkowa could you please take a look at 480dda8 and tell me if this makes sense from a methodological standpoint?

  • For responses, I am treating logicals as binary variables in kNN() and aggregate the neighbors with maxCat().
  • If logical variables are used as regressors, they are treated as factors.

Maybe it would make more sense to treat them as factors under both circumstances.

- avoid assigning variables in if-else blocks
- enable logicals for noise calculation (L476)
@GregorDeCillia GregorDeCillia marked this pull request as ready for review April 22, 2020 14:24
@GregorDeCillia GregorDeCillia merged commit ac387aa into master Apr 22, 2020
@GregorDeCillia GregorDeCillia deleted the debug_irmi branch April 22, 2020 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

irmi() fails with integer columns Imputation fails with error on logical data
3 participants