TST: corr_nearest_factor, more informative tests #1885

Merged
merged 1 commit into from Aug 14, 2014

Projects

None yet

2 participants

@josef-pkt
Member

this add more test for parts of the result and for sparse.svds to get more information about the failing test in #1850

result will be visible in pythonxy 32-bit Ubuntu

@josef-pkt josef-pkt TST: corr_nearest_factor, add test for sparse svds, objective values
5ec9fc5
@josef-pkt
Member

@kshedden this is another try to get at the test failure in corr_nearest_factor
My main guess right now is the starting value or the initial stepsize.

I think adding a start_factor=None keyword would be helpful, unless you think there is no usecase for it.

@coveralls

Coverage Status

Coverage increased (+0.01%) when pulling 5ec9fc5 on josef-pkt:corr_nearest_factor_1850 into 20c59d2 on statsmodels:master.

@josef-pkt
Member

merging, more when the test results are in

@josef-pkt josef-pkt merged commit 0c5e6c2 into statsmodels:master Aug 14, 2014

2 checks passed

continuous-integration/appveyor AppVeyor build succeeded
Details
continuous-integration/travis-ci The Travis CI build passed
Details
@josef-pkt
Member

see #1850 for continuation

@josef-pkt josef-pkt added this to the 0.6 milestone Aug 24, 2014
@josef-pkt josef-pkt removed the PR label Aug 24, 2014
@josef-pkt josef-pkt deleted the josef-pkt:corr_nearest_factor_1850 branch Apr 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment