Opened 15 years ago
Closed 15 years ago
#476 closed discussion (fixed)
NNI algorithms return wrong number of rows not imputed
Reported by: | Jari Häkkinen | Owned by: | Jari Häkkinen |
---|---|---|---|
Priority: | major | Milestone: | yat 0.5 |
Component: | test | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
The estimate function of the NNI algos are supposed to return the number of not imputed rows. The current implementation says that a row was not imputed as soon as one value on that row was not imputed. Is this what we want? I think the that no imputed rows should be rows where no value was imputed ... this also implies that rows with all weights equal to zero will become no impute rows.
We are keeping the current implementation. The expected return value is zero, the return value can be used to detect poor imputation. The estimate() function doc will be improved. Also a test for the return values should be added to the test suite.
Change History (6)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
The doc on he estimate() function is
/// Function doing the imputation. /// /// @return number of rows not imputed
but it should say something smarter like expect a zero return value for a good imputation ... or should we remove the return value and forget about it?
comment:3 Changed 15 years ago by
Would it speed up the function if we made it void
?
I think we can keep it, and modify the docs as you suggested.
comment:4 Changed 15 years ago by
Status: | new → assigned |
---|
comment:5 Changed 15 years ago by
Description: | modified (diff) |
---|
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I think as it is what we wanted. I guess the idea was that if the return is zero, everything is fine, i.e., all values have been imputed. If it returns anything else, you have a problem. I don't remember why we wanted that information though; was it a simple error check?