IT. Expert System.

Direct Known Subclasses:

StochasticLinearRankerWithPrior

public class StochasticLinearRanker
extends Object

• Nested Class Summary

  Nested Classes

  Modifier and Type	Class and Description
  static class	StochasticLinearRanker.Model

• Field Summary

  Fields

  Modifier and Type	Field and Description
  static int	VAR_NUM

• Constructor Summary

  Constructors

  Constructor and Description
  StochasticLinearRanker() Initializing a ranker

• Method Summary

  Methods

  Modifier and Type	Method and Description
  protected void	finalize() Invoked when the garbage collector has detected that this instance is no longer reachable.
  StochasticLinearRanker.Model	getUModel() Get the current model and parameters of ranker
  boolean	loadModel(StochasticLinearRanker.Model model) load the given model and parameters to the ranker
  void	print(StochasticLinearRanker.Model model) Print a model for debugging
  void	resetRanker() Reset the ranker
  float	scoreSample(String[] keys, float[] values) Get the rank score of the sample, a sample is a list of key, value pairs.
  boolean	setModelParameter(String key, String value)
  boolean	setModelWeights(String[] keys, float[] values, float normalizer)
  boolean	updateClassifier(String[] keys_positive, float[] values_positive, String[] keys_negative, float[] values_negative) Train the ranker with a pair of samples.

  • Methods inherited from class java.lang.Object

    clone, equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

• Field Detail

  • VAR_NUM

    public static int VAR_NUM

• Constructor Detail

  • StochasticLinearRanker

    public StochasticLinearRanker()

    Initializing a ranker

• Method Detail

  • resetRanker

    public void resetRanker()

    Reset the ranker

  • updateClassifier

    public boolean updateClassifier(String[] keys_positive,
                           float[] values_positive,
                           String[] keys_negative,
                           float[] values_negative)

    Train the ranker with a pair of samples. A sample, a pair of arrays of keys and values. The first sample should have higher rank than the second one.

  • scoreSample

    public float scoreSample(String[] keys,
                    float[] values)

    Get the rank score of the sample, a sample is a list of key, value pairs.

  • getUModel

    public StochasticLinearRanker.Model getUModel()

    Get the current model and parameters of ranker

  • loadModel

    public boolean loadModel(StochasticLinearRanker.Model model)

    load the given model and parameters to the ranker

  • setModelWeights

    public boolean setModelWeights(String[] keys,
                          float[] values,
                          float normalizer)

  • setModelParameter

    public boolean setModelParameter(String key,
                            String value)

  • print

    public void print(StochasticLinearRanker.Model model)

    Print a model for debugging

  • finalize

    protected void finalize()
                     throws Throwable

    Description copied from class: Object
    Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

    Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

    If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

    Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

    Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

    Overrides:

    finalize in class Object

    Throws:

    Throwable