Skip to main content

FaissImputer

Warning: FaissImputer 0.1.x has a known neighbor-mapping bug that can produce incorrect imputations, and it is incompatible with scikit-learn 1.8+. Use version 0.2.0 or newer.

PyPI Version License

A scikit-learn-compatible missing-value imputer with Faiss-backed neighbor search.

Current release: 0.3.2. See Releases for version history.

Installation

FaissImputer requires Python 3.10 or newer.

python -m pip install --upgrade "faiss-imputer>=0.3.2"

Usage

Complete donors (default)

Training data must contain enough fully observed rows to supply n_neighbors donors.

import numpy as np

from faiss_imputer import FaissImputer

X_train = np.array(
    [
        [1.0, 10.0, 100.0],
        [2.0, 20.0, 200.0],
        [3.0, 30.0, 300.0],
    ],
    dtype=np.float32,
)
X_missing = np.array(
    [
        [1.5, np.nan, 150.0],
        [2.5, 25.0, np.nan],
    ],
    dtype=np.float32,
)

imputer = FaissImputer(n_neighbors=2)
X_imputed = imputer.fit(X_train).transform(X_missing)
print(X_imputed)

Expected output:

[[  1.5  15.  150. ]
 [  2.5  25.  250. ]]

Partially observed donors

Set donor_policy="available" to choose donors separately for each missing feature. No fully observed training row is required.

import numpy as np

from faiss_imputer import FaissImputer

# No training row is completely observed.
X_train = np.array(
    [
        [0.0, 10.0, np.nan],
        [2.0, 30.0, np.nan],
        [1.0, np.nan, 20.0],
        [3.0, np.nan, 40.0],
    ],
    dtype=np.float32,
)
X_missing = np.array(
    [[0.1, np.nan, np.nan], [np.nan, np.nan, np.nan]],
    dtype=np.float32,
)

imputer = FaissImputer(n_neighbors=1, donor_policy="available")
X_imputed = imputer.fit(X_train).transform(X_missing)
print(X_imputed)

Expected output:

[[ 0.1 10.  20. ]
 [ 1.5 20.  30. ]]

Both policies return a new NumPy float32 array. The training and query inputs are not modified.

Parameters

  • n_neighbors (default: 3): Positive integer specifying the maximum number of donors used for each missing feature. The complete-donor policy requires at least this many complete training rows.
  • metric (default: "l2"): Supports "l2" and "ip". Raw inner product is not cosine similarity. The available-donor policy requires "l2".
  • strategy (default: "mean"): Supports "mean" and "median" for aggregating donor values and calculating fallback column statistics.
  • index_factory (default: "Flat"): Faiss index description for the complete-donor policy. The available-donor policy accepts only "Flat" and uses the distance backend described below.
  • donor_policy (default: "complete"): Use fully observed training rows with "complete", or allow partially observed training rows with "available".

Important behavior

Shared behavior

  • Inputs must be two-dimensional numeric array-like data, with NaN marking missing values. Values are converted to float32; infinity is not accepted.
  • transform() requires the same number of features as fit().
  • An entirely missing query row uses column means or medians learned during fit().
  • A failed fit(), including a failed refit, clears the fitted state.

Complete-donor policy

  • Only fully observed training rows are used as donors. At least one complete row is required.
  • n_neighbors cannot exceed the number of complete donors.
  • Neighbor search uses only the originally observed columns of each query row.
  • The default index_factory="Flat" performs exact neighbor search.

Available-donor policy

  • Only metric="l2" and index_factory="Flat" are supported. Both "mean" and "median" strategies are supported.
  • A donor must observe the feature being imputed and share at least one originally observed feature with the query row.
  • Donors are ranked by squared L2 distance over shared observed features, scaled by the total feature count divided by the shared feature count.
  • Each missing feature uses up to n_neighbors eligible donors. Fewer eligible donors are allowed.
  • If no eligible donor exists for a feature, its fitted column mean or median is used.
  • Entirely missing training rows are ignored; entirely missing training columns are rejected.

The available-donor policy uses batched NaN-aware distances and Faiss neighbor selection, with float64 safeguards for detected numerical risks. This backend is also used when all training donors are complete.

Batching trades memory for throughput. Its internal batch-sizing budget is not a total process-memory limit: fitted donor data, distance calculations, and temporary arrays also consume memory. Larger batches can improve speed but increase peak memory usage. FaissImputer does not set the number of threads; configure thread limits in the application when needed.

Benchmarks

Performance depends on donor policy, data size, and missingness patterns. Neither faster execution nor lower memory use than KNNImputer is guaranteed. Similar average errors do not imply identical imputed values; ties and numerical precision can affect donor selection.

  • Available-donor batching and threads: compares 16/64/128 MiB batch budgets and 1/2/4 threads, including repeated 500,000-row measurements and a single-run million-row pilot. Documents both speed gains and memory tradeoffs.
  • Real-data pilot: compares SimpleImputer, KNNImputer, and both Faiss donor policies under MCAR and selected MAR missingness. This small dataset is not a scalability test.
  • Complete-donor patterns: measures the impact of training size and query missingness patterns.
  • Partial-donor development snapshot: historical results for measured commit 0a3cc077, not the final 0.3.0 implementation.
  • Historical 0.2.0 benchmark: results for the earlier complete-donor-only implementation.

Reports provide measurement conditions, results, and links to reproduction code and raw data.

Example notebook

See Imputing Missing Values with Faiss Imputer for a complete-donor example.

Contributing

Contributions are welcome! Please open an issue or create a pull request. Further work is tracked in the roadmap.

Author

License

This project is licensed under the MIT License.

Third-Party Licenses

FaissImputer depends on Meta's Faiss, which is distributed under the MIT License.

FaissImputer is not affiliated with or endorsed by Meta or the Faiss maintainers.

Metadata

Release files for faiss-imputer 0.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for faiss-imputer 0.3.2
File Size Uploaded Provenance Actions
faiss_imputer-0.3.2.tar.gz 19.4 kB With provenance Details for faiss_imputer-0.3.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for faiss-imputer 0.3.2
File Interpreter ABI Platform Actions
faiss_imputer-0.3.2-py3-none-any.whl Python 3 none any Details for faiss_imputer-0.3.2-py3-none-any.whl

Total release size: 29.0 kB

Release files / faiss_imputer-0.3.2.tar.gz

Download URL faiss_imputer-0.3.2.tar.gz
Size 19.4 kB
Tags Source
SHA-256 checksum
How to use checksums
e3105a02e670b1c49805ebcc2e92414e352576f26afe3a0e98db5a652c57a37f
BLAKE2b-256 checksum
How to use checksums
49680303b08e5ad5835a21a93be27dac1e32b3eb8a9854a7a5d827e7a4cb67b0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.

Transparency log

Release files / faiss_imputer-0.3.2-py3-none-any.whl

Download URL faiss_imputer-0.3.2-py3-none-any.whl
Size 9.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
72ceb2e09fce5b2675ece8195313c5e9db340146e55aad74b22923da24538509
BLAKE2b-256 checksum
How to use checksums
4026e04a1530fe2648262395017c7de882ac39661cf1c46c37b74d33eeebdda6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.

Transparency log

Security for faiss-imputer 0.3.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for faiss_imputer-0.3.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.3.2 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page