I am trying to clarify the action of multiple weighted combine queries. Can you remove the nesting, as I have done below, and get the same result, or does the number of terms within each #combine matter. i.e. are these queries equivalent:
Yes, the number of terms makes a difference. By default, if no weights are specifically given for terms in the #combine, the resulting weights will simply be equally assigned amongst the terms.
Using Galago batch-search in verbose mode and terms from a TREC AP89 index gives the following results for your two query versions. The full query translations are not included to save space. Note the #combine weight indices are printed in lexographic rather than numeric order; a little annoying but not significant. Also note, some transformed weights differ slightly between versions. I believe this is nothing more than some print format rounding differences.
I am trying to clarify the action of multiple weighted combine queries. Can you remove the nesting, as I have done below, and get the same result, or does the number of terms within each #combine matter. i.e. are these queries equivalent:
query 1:
Query 2:
The two query forms are the same.
Yes, the number of terms makes a difference. By default, if no weights are specifically given for terms in the #combine, the resulting weights will simply be equally assigned amongst the terms.
Using Galago batch-search in verbose mode and terms from a TREC AP89 index gives the following results for your two query versions. The full query translations are not included to save space. Note the #combine weight indices are printed in lexographic rather than numeric order; a little annoying but not significant. Also note, some transformed weights differ slightly between versions. I believe this is nothing more than some print format rounding differences.
Many thanks, that is crystal clear.