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
Four tests are failing on the .NetCore 3.0 builds: EnsemblesMultiAveragerTest EnsemblesMultiClassBootstrapSelectorTest EnsemblesMultiVotingCombinerTest EnsemblesMultiStackCombinerTest
The difference in the baselines is something like this: L1 regularization selected 13 of 15 weights. vs. L1 regularization selected 11 of 15 weights.
The text was updated successfully, but these errors were encountered:
Investigating now, caused by different version of CPUMath gives slightly different result
harishsk
added
P1
Priority of the issue for triage purpose: Needs to be fixed soon.
and removed
P0
Priority of the issue for triage purpose: IMPORTANT, needs to be fixed right away.
labels
Apr 21, 2020
The difference comes from CPUMath using different instruction set:
net framework and net core 2.1 uses CpuMathUtils.netstandard that uses SSE instruction set;
net core 3.1 uses CpuMathUtils.netcoreapp that uses AVX, SSE or direct floating point calculation depending on hardward avaibility.
AVX and SSE generates slightly different result due to nature of floating point math.
Use below issue to track: support AVX instruction set at CPUMath native #5044
Four tests are failing on the .NetCore 3.0 builds:
EnsemblesMultiAveragerTest
EnsemblesMultiClassBootstrapSelectorTest
EnsemblesMultiVotingCombinerTest
EnsemblesMultiStackCombinerTest
The difference in the baselines is something like this:
L1 regularization selected 13 of 15 weights.
vs.L1 regularization selected 11 of 15 weights.
The text was updated successfully, but these errors were encountered: