fix infinite variance handling in GaussEst, DiscreteEst, LinEst and ReLUEst #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The infinite variance handling in GaussEst and DiscreteEst was broken, because it passed avg_var_cost into the ind_out parameter of est_init().
The infinite variance code path in ReLUEst was broken as well, because
zhat0_map
andrelated variables did not get set in this code path.
Infinite variance handling was also added to LinEst and the unit tests for all four estimators have been extended to test the infinite variance cases.