Skip to content
Back to skills

3d Workflows

ASecurity

"Route StarDist 3D users through Config3D, ray and anisotropy

  • 247 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
devopsapibackend

Works with

  • api

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill 3d-workflows --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 3d Workflows?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 3d Workflows
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-3d-workflows/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-3d-workflows)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "3d-workflows"
description: "Route StarDist 3D users through Config3D, ray and anisotropy
  selection, volume data preparation, training, local or pretrained inference,
  thresholds, and bounded large-volume prediction."
metadata:
  disco-role: operating
disable-model-invocation: true
license: BSD 3-Clause
---

# StarDist 3D workflows

Use this sub-skill for volumetric images, `Config3D`, `StarDist3D`, ray
factories, anisotropic microscopy, and 3D block inference. The required
baseline is CPU TensorFlow 2.x, StarDist, and its compiled CPU extensions.
CUDA TensorFlow and OpenCL/gputools are optional accelerators; a visible CUDA
device does not prove OpenCL availability. BioImage.IO, QuPath, and OBJ/export
are optional integrations, not part of the CPU baseline; their workflows belong
to [`deployment-integration`](../deployment-integration/SKILL.md).

## Route

1. Establish `ZYX`/`ZYXC` axes, channel count, label convention, physical
   anisotropy, and a memory budget.
2. Choose one ray object and make its length equal `Config3D.n_rays` and every
   distance tensor's final dimension.
3. Validate paired image/mask volumes, grid-compatible patches, normalization,
   and class mappings before training.
4. Load/build a local or pretrained model, then use the verified
   `StarDist3D.predict_instances` contract with deliberate sparse/dense,
   threshold, scale, and tiling choices.
5. Use `predict_instances_big` only after checking per-axis object-size and
   the strict constraint `min_overlap+2*context < block_size`; consult
   [`troubleshooting.md`](references/troubleshooting.md) for recovery.

Detailed contracts and recipes:

- [`api-reference.md`](references/api-reference.md): Config3D, data, model,
  prediction, training, and threshold APIs.
- [`workflows.md`](references/workflows.md): 3D preparation, training,
  pretrained/local inference, multiclass, normalization, and smoke routes.
- [`rays-and-anisotropy.md`](references/rays-and-anisotropy.md): ray factories,
  physical conventions, scaling, and `dist_loss_weights`.
- [`large-data.md`](references/large-data.md): `n_tiles`, block inference,
  `labels_out`, memory, and seam constraints.
- [`troubleshooting.md`](references/troubleshooting.md): install/import,
  backend, axes/rays/grid, model-path, threshold, tiling, and OOM recovery.

Native repository evidence for this sub-skill is recorded by relative path:
`stardist/models/model3d.py`, `stardist/models/base.py`, `stardist/rays3d.py`,
`stardist/big.py`, `stardist/geometry/geom3d.py`, `examples/3D/1_data.ipynb`,
`examples/3D/2_training.ipynb`, `examples/3D/3_prediction.ipynb`,
`examples/other3D/README.md`, `tests/test_model3D.py`,
`tests/test_stardist3D.py`, `tests/test_nms3D.py`, and `tests/test_big.py`.
These paths are provenance only; runtime use requires no source checkout.

Files in this skill

  • SKILL.md2.8 KB
  • references/api-reference.md7.9 KB
  • references/large-data.md8.4 KB
  • references/rays-and-anisotropy.md8 KB
  • references/troubleshooting.md11.2 KB
  • references/workflows.md10.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…