Uploaded image for project: 'Terrier Core'
  1. Terrier Core
  2. TR-153

Update and move TRECResultMatching & friends to core

          Details

          • Type: New Feature
          • Status: Resolved
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 3.5
          • Component/s: .matching
          • Labels:
            None

            Description

            Update and move TRECResultMatching & friends to core

              Attachments

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                rodrygo Rodrygo L. T. Santos added a comment -

                Committed core/org.terrier.matching.TRECResultsMatching. Corresponding test class also committed to test/org.terrier.matching.TestTRECResultsMatching

                Note the change of spelling: "Results" rather than "Result". This is to avoid conflicts with the old TRECResultMatching, which is used by lots of other classes.

                Other changes in this class resolve issues TREC-204 and TREC-213.

                Show
                rodrygo Rodrygo L. T. Santos added a comment - Committed core/org.terrier.matching.TRECResultsMatching. Corresponding test class also committed to test/org.terrier.matching.TestTRECResultsMatching Note the change of spelling: "Results" rather than "Result". This is to avoid conflicts with the old TRECResultMatching, which is used by lots of other classes. Other changes in this class resolve issues TREC-204 and TREC-213 .
                Hide
                Permalink
                rodrygo Rodrygo L. T. Santos added a comment -

                Other things to notice:

                1) I've renamed properties from "trecresults.matching.xxx" to "matching.trecresults.xxx" so as to have a more top-down namespace, in line with other properties, such as "matching.dsms";
                2) "matching.trecresults.scores" now defaults to true, as this is the most frequent use case;
                2) I've opted for switching between docnos/docids as a property (matching.trecresults.format), rather than having separate classes.

                Show
                rodrygo Rodrygo L. T. Santos added a comment - Other things to notice: 1) I've renamed properties from "trecresults.matching.xxx" to "matching.trecresults.xxx" so as to have a more top-down namespace, in line with other properties, such as "matching.dsms"; 2) "matching.trecresults.scores" now defaults to true, as this is the most frequent use case; 2) I've opted for switching between docnos/docids as a property (matching.trecresults.format), rather than having separate classes.

                  People

                  • Assignee:
                    rodrygo Rodrygo L. T. Santos
                    Reporter:
                    craigm Craig Macdonald
                  • Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: