You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alan Woodward (JIRA)" <ji...@apache.org> on 2017/10/25 10:04:00 UTC

[jira] [Commented] (LUCENE-8012) Improve Explanation class

    [ https://issues.apache.org/jira/browse/LUCENE-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218331#comment-16218331 ] 

Alan Woodward commented on LUCENE-8012:
---------------------------------------

+1 to take Number.  I tried converting things to use doubles as a followup to LUCENE-7741, but this then complicated things in the various Similarity implementations that use Explanation as a way of passing internal values around.  Using Number should tidy that up nicely.

> Improve Explanation class
> -------------------------
>
>                 Key: LUCENE-8012
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8012
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>
> Explanation class is currently nice and simple, and float matches the scoring api, but this does not work well for debugging numerical errors of internal calculations (it usually makes practical sense to use 64-bit double to avoid issues).
> Also it makes for nasty formatting of integral values such as number of tokens in the collection or even document's length, its just noise to see {{10.0}} there instead of {{10}}, and scientific notation for e.g. number of documents is just annoying. 
> One idea is to take Number instead of float? Then you could pass in the correct numeric type (int,long,double,float) for internal calculations, parameters, statistics, etc, and output would look nice.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org