Software-only · one stage · USD 500
Know what runs
before you rebuild.
Bring one existing workstation and one rights-cleared event-camera dataset. We reproduce one named stage of the public OpenHI pipeline, record the environment and commands, and return a clear go/no-go report.
The fit check asks for metadata only. No data upload or payment until the software, licenses, handling rules, and exact stage are accepted in writing.
One workstation · one dataset · one repository stage · one correction pass.
A small, inspectable experiment
Run. Record.
Decide.
What comes back
A result another lab member can inspect.
The delivery keeps the input assumptions, commands, outputs, and unresolved failures together instead of reducing the work to a screenshot.
Environment record
Repository revision, operating system, Python and package versions, available device details, required SDKs, and the exact agreed input shape.
Reproduction packet
Pinned commands and parameters, generated plots or artifacts, final logs, and a compact ledger of fixes, warnings, and remaining blockers.
Go/no-go report
A written result for the agreed stage and setup, plus the boundary of any separate work needed for different data, hardware, calibration, or algorithms.
A software reproducibility sprint
Hardware remains a separate decision.
The fixed USD 500 scope does not include a camera, optics, acquisition, component sourcing, physical alignment, optical calibration, proprietary SDK procurement, custom algorithm development, production integration, or a guarantee of scientific or publication results.
You provide
Setup metadata, the exact question, one authorized dataset or public sample, and working access to any required vendor software under your own license.
We agree first
The repository revision, pipeline stage, success signal, source-transfer method, confidentiality, retention, automation policy, and output list.
You keep control
Your data stays out of public proof unless you separately approve it. New hardware, experiments, claims, and publication decisions remain with your laboratory.
Public scientific and software proof
Inspect the method before sharing data.
A frozen synthetic run shows the exact delivery pattern. The MIT-licensed OpenHI repository accompanies the peer-reviewed Optica article “Self-calibrated neuromorphic hyperspectral derivative imaging.”
Frozen execution packet
Fixture, environment, command, log, output, and hashes.
The sample runs one public weighted-cumulative visualization stage at a pinned OpenHI revision. It records a narrow GO for that file/interface path and a NO-GO boundary around acquisition, compensation, calibration, reconstruction accuracy, and hardware.
Read the accompanying Optica article →
The sample is project-owned workflow evidence, not a customer result or a promise that an unfamiliar setup will reproduce.
Working terms
The exact stage is fixed before payment.
Timing
The written scope sets the delivery date after payment, complete setup metadata, the agreed data, and working licensed dependencies are available. Only one OpenHI sprint is active at a time.
Correction pass
One consolidated list of factual corrections is included within seven calendar days after delivery. A different dataset, workstation, repository stage, or new output is a new scope.
Cancellation and refund
Cancel before private data transfer or processing begins for a full refund. Once work starts, the written scope assigns the USD 500 price across the environment record, reproduction packet, and report; only undelivered items are refunded.
Data and support
Working data copies are deleted within fourteen calendar days after delivery, cancellation, or refund unless the accepted scope requires earlier deletion. Support is limited to written clarification during the correction window.
OpenHI software reproducibility · USD 500
Start with the smallest stage that answers the decision.
Describe the environment and target stage first. If it fits, both sides accept the data-handling and delivery scope before a Stripe request or private transfer.