opener-opinion-detector-basic 2.0.0 → 2.0.1

data/core/vendor/src/liblbfgs/ChangeLog

@@ -1,120 +0,0 @@
-2010-xx-xx  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.10:
-	- Fixed compiling errors on Mac OS X; this patch was kindly submitted by Nic Schraudolph.
-	- Reduced compiling warnings on Mac OS X; this patch was kindly submitted by Tamas Nepusz.
-
-
-2010-01-29  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.9:
-	- Fixed a mistake in checking the validity of the parameters "ftol" and "wolfe"; this mistake was discovered by Kevin S. Van Horn.
-
-
-2009-07-13  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.8:
-	- Accepted the patch submitted by Takashi Imamichi; the backtracking method now has three criteria for choosing the step length.
-	- Updated the documentation to explain the above three criteria.
-
-
-2009-02-28  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.7:
-	- Improved OWL-QN routines for stability.
-	- Removed the support of OWL-QN method in MoreThuente algorithm
-	  because it accidentally fails in early stages of iterations for some
-	  objectives. Because of this change, the OW-LQN method must be used
-	  with the backtracking algorithm (LBFGS_LINESEARCH_BACKTRACKING), or
-	  the library returns LBFGSERR_INVALID_LINESEARCH.
-	- Renamed line search algorithms as follows:
-	    - LBFGS_LINESEARCH_BACKTRACKING: regular Wolfe condition.
-	    - LBFGS_LINESEARCH_BACKTRACKING_LOOSE: regular Wolfe condition.
-	    - LBFGS_LINESEARCH_BACKTRACKING_STRONG: strong Wolfe condition.
-	- Source code clean-up.
-
-
-2008-11-02  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.6:
-	- Improved line-search algorithm with strong Wolfe condition, which
-	  was contributed by Takashi Imamichi. This routine is now default for
-	  LBFGS_LINESEARCH_BACKTRACKING. The previous line search algorithm
-	  with regular Wolfe condition is still available as
-	  LBFGS_LINESEARCH_BACKTRACKING_LOOSE.
-	- Configurable stop index for L1-norm computation. A member variable
-	  lbfgs_parameter_t::orthantwise_end was added to specify the index
-	  number at which the library stops computing the L1 norm of the
-	  variables. This is useful to prevent some variables from being
-	  regularized by the OW-LQN method.
-	- A sample program written in C++ (sample/sample.cpp).
-
-
-2008-07-10  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.5:
-	- Configurable starting index for L1-norm computation. A member
-	  variable lbfgs_parameter_t::orthantwise_start was added to specify
-	  the index number from which the library computes the L1 norm of the
-	  variables.
-	- Fixed a zero-division error when the initial variables have already
-	  been a minimizer (reported by Takashi Imamichi). In this case, the
-	  library returns LBFGS_ALREADY_MINIMIZED status code.
-	- Defined LBFGS_SUCCESS status code as zero; removed unused constants,
-	  LBFGSFALSE and LBFGSTRUE.
-	- Fixed a compile error in an implicit down-cast.
-
-
-2008-04-25  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.4:
-	- Configurable line search algorithms. A member variable
-	  lbfgs_parameter_t::linesearch was added to choose either MoreThuente
-	  method (LBFGS_LINESEARCH_MORETHUENTE) or backtracking algorithm
-	  (LBFGS_LINESEARCH_BACKTRACKING).
-	- Fixed a bug: the previous version did not compute psuedo-gradients
-	  properly in the line search routines for OW-LQN. This bug might quit
-	  an iteration process too early when the OW-LQN routine was activated
-	  (0 < lbfgs_parameter_t::orthantwise_c).
-	- Configure script for POSIX environments.
-	- SSE/SSE2 optimizations with GCC.
-	- New functions lbfgs_malloc and lbfgs_free to use SSE/SSE2 routines
-	  transparently. It is uncessary to use these functions for libLBFGS
-	  built without SSE/SSE2 routines; you can still use any memory
-	  allocators if SSE/SSE2 routines are disabled in libLBFGS.
-
-
-2007-12-16  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.3:
-	- An API change. An argument was added to lbfgs() function to receive
-	  the final value of the objective function. This argument can be set
-	  to NULL if the final value is unnecessary.
-	- Fixed a null-pointer bug in the sample code (reported by Takashi
-	  Imamichi).
-	- Added build scripts for Microsoft Visual Studio 2005 and GCC.
-	- Added README file.
-	
-
-2007-12-13  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.2:
-	- Fixed a serious bug in orthant-wise L-BFGS. An important variable
-	  was used without initialization.
-	- Configurable L-BFGS parameters (number of limited memories, epsilon).
-	
-	
-2007-12-01  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.1:
-	- Implemented orthant-wise L-BFGS.
-	- Implemented lbfgs_parameter_init() function.
-	- Fixed several bugs.
-	- API documentation.
-	
-	
-2007-09-20  Naoaki Okazaki  <okazaki at chokkan org>
-
-	* libLBFGS 1.0
-	- Initial release.
-

data/core/vendor/src/liblbfgs/INSTALL

@@ -1,231 +0,0 @@
-Installation Instructions
-*************************
-
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
-Software Foundation, Inc.
-
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-
-Basic Installation
-==================
-
-These are generic installation instructions.
-
-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
-
-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-
-The simplest way to compile this package is:
-
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.  If you're
-     using `csh' on an old version of System V, you might need to type
-     `sh ./configure' instead to prevent `csh' from trying to execute
-     `configure' itself.
-
-     Running `configure' takes awhile.  While running, it prints some
-     messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.
-
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-Compilers and Options
-=====================
-
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about.  Run `./configure --help' for
-details on some of the pertinent environment variables.
-
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
-   If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory.  After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
-By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc.  You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PREFIX'.
-
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-give `configure' the option `--exec-prefix=PREFIX', the package will
-use PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS KERNEL-OS
-
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
-

data/core/vendor/src/liblbfgs/Makefile.am

@@ -1,10 +0,0 @@
-# $Id$
-
-SUBDIRS = lib sample
-
-docdir = $(prefix)/share/doc/@PACKAGE@
-doc_DATA = README INSTALL COPYING AUTHORS ChangeLog NEWS
-
-EXTRA_DIST = \
-	autogen.sh \
-	lbfgs.sln