LensKit recommender toolkit.
Permalink
Failed to load latest commit information.
.vscode VS Code settings Aug 9, 2018
buildSrc Use new Maven publish (gradle loads) Jun 5, 2018
etc Update CI publication May 15, 2018
gradle Support SonaType credentials Jun 5, 2018
lenskit-all Merge -svd and -pf into -mf Dec 3, 2017
lenskit-api Relicense build scripts Oct 11, 2017
lenskit-cli Add a more proper run-script command Oct 7, 2018
lenskit-core Merge pull request #1059 from mdekstrand/feature/tweak May 15, 2018
lenskit-eval remove NDPM entirely May 31, 2018
lenskit-gradle Merge branch 'feature/deprecations' May 15, 2018
lenskit-groovy Update Gradle wrapper & Groovy version Nov 28, 2017
lenskit-integration-tests Test and debug batch prediction Aug 13, 2018
lenskit-knn Add a more proper run-script command Oct 7, 2018
lenskit-mf fsvd debugging Aug 23, 2018
lenskit-predict NPE in OrdRec May 15, 2018
lenskit-slopeone Another round of deprecation cleanups May 14, 2018
lenskit-svd Merge -svd and -pf into -mf Dec 3, 2017
lenskit-test Update Gradle wrapper & Groovy version Nov 28, 2017
src/main/dist remove .DS_Store files :( Jun 9, 2016
.gitattributes text files for gradle wrapper [skip ci] Apr 25, 2015
.gitignore VS Code settings Aug 9, 2018
.travis.yml Set _JAVA_OPTIONS Jun 5, 2018
CONTRIBUTING.md Update license settings Oct 11, 2017
CONTRIBUTORS.md Update CONTRIBUTORS.md Mar 1, 2017
LICENSE.md Update license settings Oct 11, 2017
README.md Update SonarCloud badges [skip ci] May 15, 2018
appveyor.yml Just Windows test on Java 8 Mar 23, 2018
build.gradle Change package for build tools Mar 22, 2018
gradlew Upgrade to Gradle 4.0 Jul 14, 2017
gradlew.bat Bump to Gradle 3.1 Mar 31, 2017
settings.gradle Merge -svd and -pf into -mf Dec 3, 2017

README.md

LensKit

Build Status Windows build status Test coverage SonarQube test coverage SonarQube technical debt Coverity Scan Build Status Join the chat at https://gitter.im/lenskit/lenskit

LensKit is an implementation of collaborative filtering algorithms and a set of tools for benchmarking them. This readme is about working with the LensKit source code. For more information about LensKit and its documentation, visit the web site or wiki. You can also find information on the wiki about how to use LensKit without downloading the source code. If this is your first time working with LensKit we recommend checking out the Getting Started guide.

LensKit is made available under the MIT license; see LICENSE.md.

Installation and Dependency Management

LensKit is built and deployed with Gradle and publishes its artifacts to Maven Central. To install it to the local Maven repository, making it available to other projects using standard Java-based tools, check out this repository and run ./gradlew install; it is then available to other projects by depending directly on it in your Maven, Gradle, Ivy, or SBT project. The source code can also be checked out and used in most Java IDEs.

Working with the Code

To work with the LensKit code, import the Gradle project into your IDE. Most modern Java IDEs include support for Gradle, including IntelliJ IDEA (used by most LensKit developers), Eclipse, and NetBeans.

No other particular setup is needed.

Modules

LensKit is comprised of several modules. The top-level lenskit module serves as a container to build them and provide common settings and dependencies. The other modules are as follows:

  • lenskit-api -- the common, public recommender API exposed by LensKit, independent of its actual implementations.
  • lenskit-test -- infrastructure and helper code for testing.
  • lenskit-core -- the core support code and configuration facilities for the rest of LensKit. It is the entry point for most of what you want to do with LensKit, providing support for configuring and building recommenders.
  • lenskit-knn -- k-NN recommenders (user-user and item-item collaborative filtering).
  • lenskit-svd -- the FunkSVD recommender (and eventually real SVD recommenders).
  • lenskit-slopeone -- Slope-One recommenders.
  • lenskit-eval -- the evaluation framework and APIs, along with a command line evaluation runner.
  • lenskit-groovy -- support for reading LensKit configurations from Groovy files.
  • lenskit-all -- a metapackage you can depend on to pull in the rest of the LensKit packages.
  • lenskit-cli -- the LensKit command line interface.
  • lenskit-gradle -- the Gradle plugin to script the LensKit evaluator
  • lenskit-integration-tests -- additional integration tests for LensKit.

Running the Tests

After you make changes, it's good to run the unit tests. You can run many of them from your IDE; run all tests in the org.grouplens.lenskit package (and subpackages) across all modules.

To run the full test suite, including data-driven unit tests and integration tests, use Gradle:

$ ./gradlew check

Copyright

LensKit is under the following copyright and license:

Copyright 2014-2017 LensKit Contributors. Copyright 2010-2014 Regents of the University of Minnesota Work on LensKit has been funded by the National Science Foundation under grants IIS 05-34939, 08-08692, 08-12148, and 10-17697.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Contributing to LensKit

We welcome contribution to LensKit. If you are looking for something to work on, we recommend perusing the open tickets on GitHub or asking on the mailing list.

We prefer to receive code submissions as GitHub pull requests. To do this:

  1. Fork the LensKit repository (lenskit/lenskit) on GitHub
  2. Push your changes to your fork
  3. Submit a pull request via the GitHub web interface

For additional details, including legal maters, please see CONTRIBUTING.md.