Skip to content

Inspect a Dataset

Inspector starts with dataset selection and empty-state troubleshooting, then moves into overview cards, balance analysis, per-class controls, stats, recommendations, and readiness checks.

Labels Ready 4 classes Metadata Ready source OIDs present Balance Check review minority class

Class balance preview

Example modulation classes before and after curation checks.

BPSKQPSK8PSK16QAM
  • Before
  • After
Data table
SeriesBPSKQPSK8PSK16QAM
Before32 slices18 slices12 slices9 slices
After28 slices27 slices25 slices24 slices

Model comparison placeholder

Compare candidate metrics before choosing an export artifact.

TinyBaseTuned
  • Validation score
Data table
SeriesTinyBaseTuned
Validation score0.71 score0.79 score0.86 score

Inspector troubleshooting

Imbalanced classes

Collect, synthesize, or curate more examples for minority classes before trusting comparisons.

Missing metadata

Check source OIDs, label names, qualifiers, sample shape, and split fields.

Too few examples

Avoid launching a run when each class has only a handful of slices unless the task is explicitly a smoke test.

Invalid split assumptions

Confirm that train and validation examples do not leak from the same source interval when independence matters.

  • Train the model — When inspection passes, continue to Train a Model to configure and launch a Model Builder run.
  • Re-curate if needed — If issues are found, return to Curation and Labeling to adjust the slicer or qualifier settings.