Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chemolytic.com/llms.txt

Use this file to discover all available pages before exploring further.

An experiment is where you train predictive models. You give it a dataset and a target property, choose a mode, and Chemolytic produces trained models you can deploy.

Hierarchy: experiment, job, trial

Three concepts, nested:
LevelDescription
ExperimentA container for one prediction problem (one dataset + one target property). Holds many jobs.
JobOne unit of background work. A job runs one or more trials.
TrialA single trained model: one preprocessing pipeline + one algorithm + one set of hyperparameters.
You don’t usually think about jobs in CoPilot mode. The hierarchy matters most in Scientist mode, where you create jobs one at a time.

Regression vs classification

The type of your target property determines whether the experiment is a regression or a classification problem. You don’t choose this manually.
Property typeExperiment typeModels predict
ContinuousRegressionA number (e.g., 18.5 °Bx)
CategoricalClassificationA category (e.g., “Arabica”)
This affects:
  • Which algorithms are available
  • Which metrics are reported
  • How results are visualized

CoPilot vs Scientist

Two modes for building models, set when you create the experiment.
ModeBest forWhat it does
CoPilotQuick results, no chemometrics expertise neededAutomatically tests 1000-3000 combinations of preprocessing + models, picks the best
ScientistSpecific configurations, expert usersYou add jobs one at a time with full control over preprocessing, model, and hyperparameters
You can’t switch modes after creation. If you change your mind, create a new experiment.

Experiments page

Go to Experiments in the project sidebar.
Experiments list page showing name, target property, dataset, mode, status, best model, and CV score
ColumnDescription
NameExperiment name and optional description
TargetThe property being predicted
DatasetDataset name and version
ModeCoPilot or Scientist
StatusPending, Running, Done, Failed, or Active (Scientist only)
Best modelAlgorithm name of the current best trial (e.g., PLS, Ridge, RF)
CV scoreBest trial’s primary cross-validation metric (RMSE for regression, F1 macro for classification)
CreatedDate created

Filters

FilterOptions
StatusAll / Pending / Running / Done / Failed
TypeAll / Regression / Classification
DatasetAll datasets, or a specific one
SearchFilters by name, description, or target property
The list polls every 3 seconds when any experiment is running, so progress updates live.

Status badges

StatusWhat it means
Pending (amber)Queued, training has not started yet
Running (flame, pulsing)Training in progress
Done (green)All work finished, best trial selected
Failed (red)Training failed; see the error on the detail page
Active (flame, pulsing)Scientist experiment is open and ready to accept new jobs

Plan limits

Two monthly quotas, shown at the top of the Experiments page:
QuotaWhat it counts
CoPilot runs this monthEach CoPilot experiment = 1 run
Scientist jobs this monthEach job you submit in a Scientist experiment = 1
Both reset at the start of your billing period. The widget shows when the next reset happens. If you hit a quota mid-month, you can still browse and inspect existing experiments; only creating new ones is blocked.

Deleting an experiment

Click the trash icon on a row, or the Delete action in the detail page.
Deleting an experiment removes all its jobs and trials permanently. Models that were registered from those trials still work (they have their own copies), but the trial details cannot be recovered.

What’s next