Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • tensor_toolbox tensor_toolbox
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tensors
  • tensor_toolboxtensor_toolbox
  • Merge requests
  • !25

Weighted bipartite matching method for ktensor/score.m function

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Grey Ballard requested to merge poly-time-score into master May 31, 2018
  • Overview 5
  • Commits 11
  • Changes 3

Weighted bipartite matching method for ktensor/score.m function. The score function used to compare two ktensors offers a 'greedy' option, which uses an algorithm that is efficient but may be inaccurate. For computing score exactly, the code uses an exhaustive search, which is an exponential-time algorithm and too slow. This change replaces the expotential algorith with a polynomial-time algorithm (a weighted bipartite matching problem).

Closes #28

Checklist

  • Issue Before the merge request, submit an issue for the change, providing as much detailed information as possible. For bug reports, please provide enough information to reproduce the problem.

  • Fork Create a branch or fork of the code and make your changes.

  • Help Comments Create or update comments for the m-files, following the style of the existing files. Be sure to explain all code options.

  • Tests Create or update tests in the tests directory, especially for bug fixes or strongly encouraged for new code.

  • Release Notes Update RELEASE_NOTES.txt with any significant bug fixes or additions.

  • Contributors List Update CONTRIBUTORS.md with your name and a brief description of the contributions.

  • Pass All Tests Confirm that all tests (including existing tests) pass in tests directory.

  • Merge Request At any point, create a work-in-progress merge request, referencing the issue number and with this checklist and WIP in the header.

Edited Jan 18, 2021 by Tammy Kolda
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: poly-time-score