You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The test_predict_exact() test in the test_dmd.py file ends up comparing two empty arrays, which doesn't seem to correctly assess for accurate dmd.predict outputs when exact=True. It seems that the expected array, which is used as the ground truth, is just an empty array. This array is then compared against dmd.predict(sample_data[:, 20:40]) when sample_data is only a (400, 15) array.
To Reproduce
Below is the test_predict_exact() test, with an additional print statement in order to highlight the issue.
Expected behavior dmd.predict(sample_data) and expected should be non-empty arrays so that test_predict_exact() actually tests for accurate dmd.predict outputs when exact=True.
Output expected turns out to be an empty array.
>>> []
The text was updated successfully, but these errors were encountered:
Describe the bug
The
test_predict_exact()
test in thetest_dmd.py
file ends up comparing two empty arrays, which doesn't seem to correctly assess for accuratedmd.predict
outputs whenexact=True
. It seems that theexpected
array, which is used as the ground truth, is just an empty array. This array is then compared againstdmd.predict(sample_data[:, 20:40])
whensample_data
is only a(400, 15)
array.To Reproduce
Below is the
test_predict_exact()
test, with an additionalprint
statement in order to highlight the issue.Expected behavior
dmd.predict(sample_data)
andexpected
should be non-empty arrays so thattest_predict_exact()
actually tests for accuratedmd.predict
outputs whenexact=True
.Output
expected
turns out to be an empty array.The text was updated successfully, but these errors were encountered: