domains / families / science / nv-segment-ct

nv-segment-ct

separate

Used for running NV-Segment-CT VISTA3D on CT NIfTI volumes and recording label-map evidence.

When to use

• Used for running NV-Segment-CT VISTA3D on CT NIfTI volumes and recording label-map evidence. Not for clinical interpretation.
• Use the wrapper exactly as documented; do not replace the upstream entrypoint with a handwritten implementation.
• Manifest I/O: inputs are `ct_volume`; outputs are `label_map` and `result_json`.

When not to use

• This is a thin wrapper. Inference, preprocessing, and postprocessing are delegated entirely to the official `hugging_face_pipeline.HuggingFacePipelineHelper` in bundle/. Do not modify code under bundle/.
• `transformers==4.46.3` is the wrapper compatibility overlay tested with the upstream requirements' Torch 2.0.1; newer Transformers releases can disable that older Torch backend.
• The pinned upstream requirements include Torch 2.0.1. Use only the pinned NVIDIA model assets; do not load untrusted checkpoints in this legacy reproduction environment.
• Device auto-detected (cuda if available, else cpu); `--device` flag overrides.
• Output may be schema-valid but semantically empty (e.g. label prompts that do not match the input anatomy). Sanity gates assert at least one foreground voxel per requested anatomy.
• Not for clinical deployment, clinical interpretation, autonomous diagnosis, regulatory submission.

Skill page

Source