problem-classifier

You can classify parsed subquestions into mathematical modeling problem types by providing a validated problem parse to the classifier. It generates a structured problem-type map that identifies the core task type for each subquestion.

Classifying mathematical modeling problem types requires a validated problem parse containing subquestions, goals, objects, constraints, data inventory, required outputs, and notes to accurately map the core task type.

Yes, problem classification output includes detailed explanations for classification reasons. It also lists candidate method families and flags common misclassification risks for each subquestion.

The best way to guide downstream tool usage is to generate a structured problem-classification artifact. This artifact directs subsequent pipeline steps like method selection and related paper analysis.

The structured problem classification artifact is saved under the workspace/problem/problem-classifier/ directory. This output drives subsequent skills in the mathematical modeling pipeline.

Problem-type classification is required before method selection because it converts validated problem parses into a problem-type map. This map identifies core task types to ensure downstream tools apply appropriate candidate method families.