I moved the label processing code from TrainMLModelParser to a common LabelHelper class, so it can be used by multiple instructions. The original label processing code in ExploratoryAnalysis was too simple to deal with label positive_class definitions (necessary when testing SequenceAbundance encoder in expl. analysis). Now both TrainMLModelParser and ExploratoryAnalysisParser use LabelHelper to construct their LabelConfiguration.
I moved the label processing code from TrainMLModelParser to a common LabelHelper class, so it can be used by multiple instructions. The original label processing code in ExploratoryAnalysis was too simple to deal with label positive_class definitions (necessary when testing SequenceAbundance encoder in expl. analysis). Now both TrainMLModelParser and ExploratoryAnalysisParser use LabelHelper to construct their LabelConfiguration.