=== START program2: ./run inspect ../dataset1/train
=== END program2: ./run inspect ../dataset1/train --- OK [207s]
=== START program2: ./run inspect ../dataset1/test
=== END program2: ./run inspect ../dataset1/test --- OK [92s]
supervised-learning-processor: Main entry point for validating and inspecting a dataset for supervised learning datasets.
(Dataset) neut_0.-.005: Task: text sentiment analysis.
Features: text term/freq counts, along with other real-valued features.
Labels: binary sentiment score.
(Program[Inspect]) binary-utils: Validates and inspects a dataset in BinaryClassification format.
(Program[Split]) binary-utils: Validates and inspects a dataset in BinaryClassification format.
Go to the page for the run and look at the log file for signs of the responsible error.
You can also download the run and run it locally on your machine (a README file should
be included in the download which provides more information).
We said that a run was simply a program/dataset pair, but that's not the full story.
A run actually includes other helper programs such as the evaluation program and
various programs for reductions (e.g., one-versus-all, hyperparameter tuning).
More formally, a run is a given by a run specification,
which can be found on the page for any run.
A run specification is a tree where each internal node represents a program
and its children represents the arguments to be passed into its constructor.
For example, the one-versus-all program takes your binary classification program
as a constructor argument and behaves like a multiclass classification program.