Skip to content

Addressing LFDA sign indeterminacy #326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,5 @@ htmlcov/
.cache/
.pytest_cache/
doc/auto_examples/*
doc/generated/*
doc/generated/*
venv/
5 changes: 5 additions & 0 deletions doc/supervised.rst
Original file line number Diff line number Diff line change
Expand Up @@ -292,6 +292,11 @@ same class are not imposed to be close.
lfda = LFDA(k=2, dim=2)
lfda.fit(X, Y)

.. note::
LDFA suffers from a problem called “sign indeterminacy”, which means the sign of the ``components`` and the output from transform depend on a random state. This is directly related to the calculation of eigenvectors in the algorithm. The same input ran in different times might lead to different transforms, but both valid.

To work around this, fit instances of this class to data once, then keep the instance around to do transformations.

.. topic:: References:

.. [1] Sugiyama. `Dimensionality Reduction of Multimodal Labeled Data by Local
Expand Down