Skip to content

clarify#4664

Merged
hmusum merged 1 commit intomasterfrom
kkraune-patch-1
Apr 22, 2026
Merged

clarify#4664
hmusum merged 1 commit intomasterfrom
kkraune-patch-1

Conversation

@kkraune
Copy link
Copy Markdown
Member

@kkraune kkraune commented Apr 22, 2026

No description provided.

@kkraune kkraune requested a review from hmusum April 22, 2026 05:53
@hmusum hmusum merged commit fe825cb into master Apr 22, 2026
@hmusum hmusum deleted the kkraune-patch-1 branch April 22, 2026 06:16
@bratseth
Copy link
Copy Markdown
Member

Imho duplicating info on how the relevance is calculated here is unnecessary (and in general the final value can also be calculated in some other way, e.g. if there are external third-phase rankers).

@kkraune
Copy link
Copy Markdown
Member Author

kkraune commented Apr 22, 2026

true. there was a user asking, from the result json page, where does this value come from. so maybe better to put a small section in https://docs.vespa.ai/en/ranking/ranking-intro.html and link to there from result json doc. It was not clear to him. and we can put the Nan stuff there too

@bratseth
Copy link
Copy Markdown
Member

I think the user question turned out to be more "why do I get this error", i.e. the NaN thing. Yes, we could point to ranking-intro with the word "relevance". That doc should be rewritten a lot btw ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants