lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cpoersc...@apache.org
Subject [2/2] lucene-solr:jira/solr-8542-v2: SOLR-8542: overview.html proof-read/tweak
Date Mon, 31 Oct 2016 17:58:36 GMT
SOLR-8542: overview.html proof-read/tweak


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/e17a3430
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/e17a3430
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/e17a3430

Branch: refs/heads/jira/solr-8542-v2
Commit: e17a3430f05cd2072f32bbd42faf93f5150e8533
Parents: 363233d
Author: Christine Poerschke <cpoerschke@apache.org>
Authored: Mon Oct 31 17:55:23 2016 +0000
Committer: Christine Poerschke <cpoerschke@apache.org>
Committed: Mon Oct 31 17:55:23 2016 +0000

----------------------------------------------------------------------
 solr/contrib/ltr/src/java/overview.html | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e17a3430/solr/contrib/ltr/src/java/overview.html
----------------------------------------------------------------------
diff --git a/solr/contrib/ltr/src/java/overview.html b/solr/contrib/ltr/src/java/overview.html
index 7b8198c..47179f0 100644
--- a/solr/contrib/ltr/src/java/overview.html
+++ b/solr/contrib/ltr/src/java/overview.html
@@ -29,7 +29,7 @@ functions like TF-IDF or BM25.
 </p>
 <p>
 This module allows to plug a reranking component directly into Solr, enabling users
-lto easily build their own learning to rank systems and access the rich
+to easily build their own learning to rank systems and access the rich
 matching features readily available in Solr. It also provides tools to perform
 feature engineering and feature extraction.
 </p>
@@ -37,7 +37,7 @@ feature engineering and feature extraction.
 <p>
 A Learning to Rank model is plugged into the ranking through the {@link org.apache.solr.search.LTRQParserPlugin},
 a {@link org.apache.solr.search.QParserPlugin}. The plugin will
-read from the request the model (instance of {@link org.apache.solr.ltr.LTRScoringQuery})
+read from the request the model (instance of {@link org.apache.solr.ltr.LTRScoringModel})
 used to perform the request plus other
 parameters. The plugin will generate a {@link org.apache.solr.search.LTRQParserPlugin.LTRQuery
LTRQuery}:
 a particular {@link org.apache.solr.search.RankQuery}
@@ -63,7 +63,7 @@ into the framework  by extending {@link org.apache.solr.ltr.model.LTRScoringMode
 The {@link org.apache.solr.ltr.LTRScoringQuery} will take care of computing the values of
 all the features (see {@link org.apache.solr.ltr.feature.Feature}) and then will delegate
the final score
 generation to the {@link org.apache.solr.ltr.model.LTRScoringModel}, by calling the method
-{@link org.apache.solr.ltr.model.LTRScoringModel#score(float[] modelFeatureValuesNormalized)
score(float[] modelFeatureValuesNormalized)}.
+{@link org.apache.solr.ltr.model.LTRScoringModel#score(float[] modelFeatureValuesNormalized)}.
 </p>
 <p>
 A {@link org.apache.solr.ltr.feature.Feature} will produce a particular value for each document,
so
@@ -72,17 +72,17 @@ it is modeled as a {@link org.apache.lucene.search.Query}. The package
 of features. One benefit of extending the Query object is that we can reuse
 Query as a feature, see for example {@link org.apache.solr.ltr.feature.SolrFeature}.
 Features for a document can also be returned in the response by
-using {@link org.apache.solr.response.transform.DocTransformer DocTransformer}
+using the FeatureTransformer (a {@link org.apache.solr.response.transform.DocTransformer
DocTransformer})
 provided by {@link org.apache.solr.response.transform.LTRFeatureLoggerTransformerFactory}.
 </p>
 <p>
-{@link org.apache.solr.ltr.store} contains all the logic to store all the features and the
models
-added by a user. Models are registered into a unique {@link org.apache.solr.ltr.store.ModelStore
ModelStore},
+{@link org.apache.solr.ltr.store} contains all the logic to store all the features and the
models.
+Models are registered into a unique {@link org.apache.solr.ltr.store.ModelStore ModelStore},
 and each model specifies a particular {@link org.apache.solr.ltr.store.FeatureStore FeatureStore}
that
 will contain a particular subset of features.
 <p>
 </p>
-A user can manage features and models through a REST API, provided by the
+Features and models can be managed through a REST API, provided by the
 {@link org.apache.solr.rest.ManagedResource Managed Resources}
 {@link org.apache.solr.ltr.store.rest.ManagedFeatureStore ManagedFeatureStore}
 and {@link org.apache.solr.ltr.store.rest.ManagedModelStore ManagedModelStore}.


Mime
View raw message