profile-imaging

Featured

Profile a medical-imaging dataset before any modelling decision is made — the acquisition grid, voxel spacing and orientation spread, the intensity domain, which label values are actually present, how much of the volume the target occupies, and how large the target is in millilitres — then gate that profile against the researcher's declared plan. Catches, at the point where it is still cheap, the dataset facts that otherwise surface after a training run: a "test set" that carries no ground truth, labels whose grid does not match their image, a stray label index, a target occupying a fraction of a percent while accuracy is planned as a metric, and acquisition heterogeneity nobody declared a resampling decision for. Emits a dataset-profile JSON and a deterministic gate that reads it (stdlib-only, so an audit travels with the JSON). It describes the data and audits the plan against it; it does not preprocess, split, or train.

Data & Documents 220 stars 55 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
78
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Profile-Imaging Skill ## Purpose A dataset decides more of a study than the architecture does, and it decides it **first**. Before anything is preprocessed, split, or trained, a handful of facts are already true about the data, and each one closes off or opens up a research plan: - If the target occupies 0.4 % of the volume, accuracy is not a metric — predicting background everywhere scores 99.6 %. - If through-plane spacing runs 1.5–8 mm inside a single institution, resampling is not a default to accept quietly; it is the most consequential preprocessing choice in the study, and it is also the axis along which an external dataset will differ. - If the directory named `imagesTs` has no labels, it is not a test set, and the held-out set has to come from somewhere else — better known before training than after. - If the organ volume spans 56–502 mL when normal is roughly 100–250, the cohort contains disease that a subgroup analysis should be **pre-specified** for, rather than discovered post hoc. None of that requires a model, a GPU, or an engineer. It requires reading every file once and writing down what is there. This skill does that, and then audits the plan against it. It is the **front door** of the model-engineering lane: `profile-imaging (describe)` → `/design-study` + `/architecture-zoo` (decide) → `/preprocess-imaging` (plan the pipeline) → `/model-scaffold` (build) → `/model-validation` → `/model-evaluation`. ## When to use - You have a dataset and ...

Details

Author
Aperivue
Repository
Aperivue/medsci-skills
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

profile-dataset

Produce a coverage & quality profile of a Narrative dataset (or access rule): row count, per-column null/fill rate, cardinality, ranges, top-values, inferred column shape, and quality flags. Reads bundled stats + sample first, recovers missing/stale stats by configuring and recalculating them, and escalates to a cheap `/write-nql` query only for a measure no stat can provide. Descriptive, not prescriptive. Use when: "profile dataset N", "what does dataset N look like", "coverage and quality of <dataset>", "what id types does N emit", "null rates / cardinality for <dataset>", "is this dataset's stats fresh". (narrative-common)

7 Updated today
narrative-io
Data & Documents Featured

preprocess-imaging

Design or audit the data-preparation stage of a medical-imaging model — DICOM/NIfTI intake, resampling and intensity normalisation, and the augmentation plan — so the pipeline is leakage-safe before model-scaffold builds the training repo. Emits a declarative preprocessing manifest and a deterministic data-stage leakage gate that catches the leaks a split table cannot see: a dataset-level normaliser fit on non-train data, any data-fitted transform run before the split, and the same patient's slices crossing splits. Integrates MONAI / TorchIO transforms; it does not reimplement them, and it never runs preprocessing on real patient data.

220 Updated today
Aperivue
Data & Documents Listed

data-profiling

Profile and map raw data BEFORE designing a schema. One-time exploratory analysis to learn the true shape of a dataset — row/column counts, null rates, cardinality, value distributions, ranges, data types, candidate keys, duplicates, referential relationships — then a source-to-target field mapping and an ER diagram. Use this skill whenever the user has data in hand and needs to understand it before modeling, is about to design a schema, asks "what does this data actually look like", needs to find the primary/composite key of an unfamiliar table, or must map source fields to a target model. This is exploratory and one-time; ongoing production validation is data-quality's job, and modeling patterns are schema-design's job.

1 Updated 1 weeks ago
Methasit-Pun