Skip to main content

Fixerpy helper to clone/build/run the NVIDIA Fixer container and run inference on example images.

Usage requires Docker (with GPU support for best performance) and the uv tool.

Quickstart

  • Clone + build + download weights + run inference on Fixer examples:
    • uv run fixer

Details

  • What uv run fixer does:
    • Clones https://github.com/nv-tlabs/Fixer.git into .fixer_work/Fixer (if missing)
    • Builds the Docker image from Dockerfile.cosmos with tag fixer-cosmos-env
    • Downloads model weights via hf download nvidia/Fixer --local-dir models into the cloned repo
    • Runs the container per Fixer README, mounting the repo to /work and invoking the inference script on example images:
      • python /work/src/inference_pretrained_model.py --model /work/models/pretrained/pretrained_fixer.pkl --input /work/input --output /work/output --timestep 250
    • Outputs are saved to ./output (relative to current working directory)

CLI options

  • --dest-root PATH: Working directory (default: .fixer_work)
  • --input PATH: Input directory (default: <dest-root>/Fixer/examples)
  • --output PATH: Output directory (default: ./output)
  • --timestep INT: Inference timestep (default: 250)
  • --batch-size INT: Batch size (default: 1)
  • --test-speed: Run speed benchmark before inference
  • --no-gpus: Disable GPU pass-through for the container
  • --platform linux/amd64|linux/arm64: Build target platform (auto-detected by default)

Examples

  • Run with defaults (examples → output):
    • uv run fixer
  • Run with custom input/output:
    • uv run fixer --input /path/to/images --output /path/to/out --timestep 250
  • Force platform (for cross-arch hosts or when needed):
    • uv run fixer --platform linux/amd64

Notes

  • This project uses Docker and the Fixer README’s recommended /work mount layout.
  • Weights are downloaded to .fixer_work/Fixer/models via Hugging Face CLI.
  • Ensure your Docker supports GPU (--gpus all) if you want GPU acceleration.

Metadata

Release files for fixerpy 0.1.0

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

Source distribution (sdist)

Source distribution for fixerpy 0.1.0
File Size Uploaded Provenance Actions
fixerpy-0.1.0.tar.gz 4.5 kB With provenance Details for fixerpy-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fixerpy 0.1.0
File Interpreter ABI Platform Actions
fixerpy-0.1.0-py3-none-any.whl Python 3 none any Details for fixerpy-0.1.0-py3-none-any.whl

Total release size: 10.7 kB

Release files / fixerpy-0.1.0.tar.gz

Download URL fixerpy-0.1.0.tar.gz
Size 4.5 kB
Tags Source
SHA-256 checksum
How to use checksums
643c2ba56cbbf5ba55e5dc52b067db0f4f5a1b32e91d84bd401418b189fad0f9
BLAKE2b-256 checksum
How to use checksums
28393f9db662e8a35de7f897848cdefa2dd8c1d8882675017a3f43657a46b2f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 2, 2026.

Transparency log

Release files / fixerpy-0.1.0-py3-none-any.whl

Download URL fixerpy-0.1.0-py3-none-any.whl
Size 6.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f4cc4cb55e43b5481e7899f9dc0ffff55e4d59a6c928560d3dec5909db2adc46
BLAKE2b-256 checksum
How to use checksums
df66d74f832a95af9ce2383e32f54c44ce2d7bcf1e66c7284c608ea953352356
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 2, 2026.

Transparency log

Security for fixerpy 0.1.0

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for fixerpy-0.1.0.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 Jan 2, 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.1.0 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