Re: Outlier test fail

If I were to guess, it's -Duselongdouble.

I had build failures with this flag (and also quadmath) with my module JSON::SIMD. In my case I had to adapt some of the code to use a slower but more precise number parser.

You could either find a way to fix your algorithms so that the tests really pass even with these build flags, or if you decide that this loss of precision (that only happens with a build flag that's usually off anyway), you could fudge or disable the test with these flags.

Comment on Re: Outlier test fail Download Code

Replies are listed 'Best First'.
Re^2: Outlier test fail by Bod (Parson) on Jan 11, 2024 at 22:44 UTC
You could either find a way to fix your algorithms... I can't...the calculations are not performed by my module, they use Data::CosineSimilarity if you decide that this loss of precision... In every use case I'm aware of, precision isn't needed in Embeddings. Rather, they are rated in order from "1" (highest similarity) to "-1" (lowest similarity) to match the same meaning in the text being evaluated. So, from a use case the test failure is not an issue. But it doesn't strike me as good practice to publish tests that fail...	[reply]

Replies are listed 'Best First'.

Re^2: Outlier test fail
by Bod (Parson) on Jan 11, 2024 at 22:44 UTC

You could either find a way to fix your algorithms...

I can't...the calculations are not performed by my module, they use Data::CosineSimilarity

if you decide that this loss of precision...

In every use case I'm aware of, precision isn't needed in Embeddings. Rather, they are rated in order from "1" (highest similarity) to "-1" (lowest similarity) to match the same meaning in the text being evaluated.

So, from a use case the test failure is not an issue. But it doesn't strike me as good practice to publish tests that fail...

[reply]