4.1. Experimental Settings and Evaluation Methods
To evaluate the proposed framework under variable operating conditions and the run-disjoint protocol, the experiments examined partitioning protocols, support-set sizes, diagnostic methods, class-level performance, feature contributions, operating-condition generalization, and computational efficiency. All methods used identical fold partitions, random seeds, candidate support runs, and query runs.
RPN employed a three-channel ResNet1D encoder containing two residual blocks, each with two one-dimensional convolutional layers, 128 output channels, and a kernel size of 5. Adaptive global average pooling followed by normalization produced a 128-dimensional embedding for each window. The encoder was pretrained for up to 60 epochs using the AdamW optimizer implemented in PyTorch 2.5.1, with an initial learning rate of 0.001, a batch size of 64, and multilabel binary cross-entropy over 14 atomic fault nodes. The encoder checkpoint with the lowest validation loss on the validation combinations was retained. During target-task evaluation, the frozen window embeddings were averaged first within each run and then across support runs of the same class to construct prototypes; query runs were classified using cosine similarity.
RPN used the training combinations to pretrain its encoder, whereas Random Forest implemented in scikit-learn 1.7.2 and XGBoost 3.2.0 fitted task-specific classifiers using only the support set of each target task. Therefore, the comparison reflects different few-shot adaptation paradigms under identical target tasks rather than models trained with identical source-data budgets.
To broaden the comparison with optimization-based meta-learning approaches, standard second-order MAML [
34] and ANIL were additionally implemented as controlled few-shot baselines. Both methods used a three-channel ResNet1D backbone with two residual blocks and a 128-dimensional representation. Group normalization was used instead of batch normalization to avoid task-dependent running-state leakage during functional inner-loop adaptation. For MAML, both the encoder and classification head were updated during inner-loop adaptation, whereas for ANIL only the classification head was adapted. The outer-loop parameters were trained using only the training combinations of each fold, and hyperparameters and checkpoints were selected exclusively using the corresponding validation combinations. The target test combinations were not accessed before the final evaluation. Because each outer fold contained only two validation compound-fault combinations, validation episodes were necessarily two-way, whereas meta-training and final target evaluation remained three-way.
The compared methods included the run-level prototypical network (RPN), Random Forest, full-feature XGBoost, MAML, and ANIL. RPN represents a metric-based few-shot approach using pretrained deep representations, Random Forest represents a bagging-based tree ensemble, XGBoost is the gradient-boosted tree classifier adopted in the proposed workflow, and MAML and ANIL represent optimization-based meta-learning baselines. The main procedures, input representations, prior source-training usage, and target-task adaptation strategies of the five methods are summarized in
Table 6.
All five methods used identical target support and query tasks. However, their prior-data usage differed. XGBoost and Random Forest did not use a pretrained source model, whereas RPN, MAML, and ANIL used the training combinations for representation or meta learning and the validation combinations for model selection. Therefore, comparisons across these paradigms should be interpreted as practical comparisons between different few-shot adaptation strategies rather than as comparisons under identical total training-data budgets.
Three additional controlled variants were constructed to investigate the effects of correlated support windows, input representation, and classifier design under the strict three-shot setting. For Run-XGBoost, the eight 48-dimensional feature vectors belonging to each complete run were arithmetically averaged before classifier fitting, such that each support run contributed exactly one 48-dimensional training vector. Consequently, each three-way three-shot task contained only nine classifier-training samples. The feature standardizer was fitted using these nine support-run vectors, and the same frozen XGBoost hyperparameters as in the principal experiments were retained without additional tuning.
For Feature-Proto, exactly the same standardized 48-dimensional run-mean vectors as those used by Run-XGBoost were employed. A prototype was constructed by averaging the three support-run vectors belonging to each target class, and query runs were classified using cosine similarity. Thus, Run-XGBoost and Feature-Proto differed primarily in classifier design while sharing the same handcrafted run-level representation.
For Embedding-XGBoost, the validation-selected and frozen RPN encoder was reused without retraining. The eight 128-dimensional window embeddings of each run were averaged to obtain the same run-level representation used by RPN. XGBoost was then fitted using the target support-run embeddings with the frozen XGBoost hyperparameters. Therefore, RPN and Embedding-XGBoost shared exactly the same learned run-level representation but used different classifiers. No query labels were used for preprocessing, fitting, or parameter selection in any of these controlled variants.
Random Forest consisted of 500 decision trees, with n_jobs = 10 and a random seed corresponding to the current task. All remaining parameters retained the default settings of scikit-learn 1.7.2. Both XGBoost and Random Forest used 10 CPU threads in the computational-efficiency experiments.
As shown in
Table 7, each method was evaluated using three folds, five random seeds, and three episodes for each seed, resulting in 45 repeated task instances. Task-level means and standard deviations were used to describe the performance distributions across different target-class combinations and support tasks. However, these task instances were not treated as mutually independent physical experimental samples.
For statistical inference regarding the difference between the one-shot and three-shot settings, the predicted probabilities of the same query run were first averaged across different episodes. Each unique run ID was then treated as the paired statistical unit. A class-stratified bootstrap procedure with 10,000 resamples was conducted according to the true compound fault classes, and 95% confidence intervals were reported.
An analogous protocol-specific paired bootstrap was performed for the matched Run-disjoint versus Window-mixed comparison. Because the same physical query run could appear in multiple support episodes, repeated class-probability predictions were first averaged separately within each protocol and unique query-run ID. This produced one aggregated prediction for each physical query run under each protocol. A class-stratified paired bootstrap with 10,000 resamples was then performed over the unique run IDs, with exactly the same resampled run IDs used for both protocols in each bootstrap replicate. The bootstrap statistic was defined as The 2.5th and 97.5th percentiles of the bootstrap distribution were used to construct the 95% confidence interval. The task-level mean difference and the unique-run bootstrap estimate are reported separately because they use different statistical units.
The diagnostic results were evaluated at both the compound fault class level and the atomic fault component level. For class
, precision, recall, and F1-score are defined as follows, respectively:
where
,
, and
denote the numbers of true-positive, false-positive, and false-negative predictions for class
, respectively.
Macro-F1 and run-level accuracy are defined as follows, respectively:
where
is the number of candidate compound fault classes in the current task,
is the number of query runs, and
and
are the true compound fault class and run-level predicted class of the r-th query run, respectively.
To provide an auxiliary evaluation of the compound-fault predictions from the perspective of their constituent fault components, the Present-Component Macro-F1, abbreviated as PC-Macro-F1, was employed.
Let the set of atomic fault components present in the test set of the e-th evaluation unit be
, where
indicates whether the r-th query run contains atomic fault component
. PC-Macro-F1 is then defined as follows:
where
denotes the number of atomic fault components present in the current test set.
The true and predicted compound fault classes of each query run were first converted into binary atomic fault component vectors according to the predefined mapping between compound faults and atomic components. For each fold-seed-episode evaluation unit, only atomic fault components with at least one positive sample in the current test set were retained. The binary F1-score was calculated separately for each of these present components and then macro-averaged.
The test sets of Fold A, Fold B, and Fold C contained five, four, and five present atomic fault components, respectively. Across the three folds, six distinct atomic fault components were covered: severe bearing inner-race fault, severe bearing outer-race fault, broken rotor bar, dynamic eccentricity, severe static eccentricity, and severe winding fault. This metric was obtained by mapping run-level compound-fault class predictions to atomic component labels. It does not indicate that an additional independent multilabel atomic-fault classifier was trained.
4.2. Comparison Between the Run-Disjoint and Window-Mixed Protocols
To directly verify the necessity of run-level data separation, a matched-query partitioning-protocol comparison was designed. The Run-disjoint and Window-mixed protocols used exactly the same 27 query run IDs, 144 query windows, and 24 support windows per class.
Each class initially contained nine query runs and 72 candidate query windows, with eight windows extracted from each run. For the matched protocol comparison, 24 windows per class were selected according to the same predefined allocation rule for support-set construction, leaving 48 query windows per class and 144 query windows in total. Both protocols used exactly these 144 query windows. Under the run-disjoint protocol, the support windows were obtained from separate support-run IDs, whereas under the window-mixed protocol, the support windows were obtained from runs that also contributed retained query windows. Run-level probabilities were calculated by averaging all retained query-window probabilities belonging to each query run.
The only difference between the protocols was whether the support windows were allowed to originate from query runs. Under the run-disjoint protocol, the support and query run IDs were completely nonoverlapping. Under the window-mixed protocol, different windows from the same run could be assigned to the support and query sets. The results are presented in
Table 8 and
Figure 3.
As shown in
Table 8, the window-mixed protocol increased the task-level mean window-level Macro-F1, run-level Macro-F1, run-level accuracy, and PC-Macro-F1 by 0.0549, 0.0722, 0.0691, and 0.0612, respectively. Because the query runs, query windows, and support-window budget were held fixed, these task-level results show that allowing support windows to originate from query runs can produce optimistic estimates under particular few-shot support-task realizations.
The 0.0722 value represents the difference between the mean run-level Macro-F1 values across the 45 matched support-task instances and should not be interpreted as an effect size based on 45 independent physical experiments. An additional paired bootstrap analysis therefore treated the unique query-run ID as the statistical unit. After repeated class-probability predictions were averaged separately within each protocol and unique run, 108 unique physical query runs remained. The aggregated run-disjoint and window-mixed Macro-F1 values were 0.9907 and 1.0000, respectively, corresponding to a unique-run difference of 0.0093. The 10,000-replicate class-stratified paired bootstrap yielded a 95% percentile confidence interval of [0.0000, 0.0282].
The difference between the task-level estimate and the unique-run estimate indicates that the apparent magnitude of the leakage-related performance difference depends strongly on the statistical unit and on how repeated support-task realizations are aggregated. Therefore, the 0.0722 difference is interpreted as descriptive task-level inflation, whereas the unique-run bootstrap provides the physical-run-level statistical assessment. Because the lower percentile bound of the 95% confidence interval was 0.0000, the unique-run result is not interpreted as evidence of a strictly positive effect at the 95% confidence level. Nevertheless, strict run-ID separation remains necessary to prevent the same physical acquisition from contributing to both support and query sets by construction.
4.7. TreeSHAP-Based Feature-Attribution Results
To investigate the decision basis of full-feature XGBoost, the TreeSHAP contributions obtained across different folds, random seeds, and support tasks were first aggregated. The global feature-contribution distribution is presented in
Figure 6.
As shown in
Figure 6, the
X-axis normalized dominant frequency exhibited the largest global relative TreeSHAP contribution (8.49%), followed by the
X-axis second-band relative energy (8.28%),
Z-axis skewness (7.73%), and
Y-axis skewness (6.78%). The Top 15 features covered all four feature categories, including time-domain amplitude, impulsiveness and statistical distribution, zero-crossing characteristics, and frequency-domain structure. Frequency-position and band-energy descriptors occupied several of the highest-ranking positions, indicating that spectral-location and energy-distribution information played an important role in the classifier decisions. Distribution-related features, particularly skewness, also contributed strongly across multiple vibration directions.
As a robustness check, the normalized global ranking was compared with the original ranking obtained from unnormalized mean absolute TreeSHAP values. The two rankings showed a Spearmans’ rank correlation of 0.9959, with complete Top 10 and Top 15 feature-set overlap. Thus, normalization altered several relative ranks and magnitudes but did not materially change the set of dominant features identified by the analysis.
The class-specific TreeSHAP contributions for the nine compound fault classes under the strict three-shot protocol are shown in
Figure 7.
Figure 7 reveals distinct class-specific feature-attribution patterns. BOI relies strongly on
X-axis second-band energy, whereas DEI and SEO assign the largest relative contribution to the
X-axis normalized dominant frequency. BBO is most strongly associated with the
X-axis zero-crossing rate, while WI is dominated by
Y-axis skewness. Other classes show broader combinations of spectral, distribution-related, and multiaxis features. These class-dependent patterns indicate that the classifier distinguishes different compound-fault combinations using different mixtures of vibration characteristics rather than a single universally dominant feature.
From a vibration-physics perspective, the dominant attribution patterns are qualitatively consistent with different properties of motor vibration signals. Spectral-position and band-energy features characterize changes in periodic or modulated vibration energy, whereas skewness and other distribution-related features reflect waveform asymmetry and impulsive behavior. Zero-crossing rate further characterizes changes in oscillatory sign-transition behavior. These signal properties can be affected by bearing, rotor, eccentricity, and winding-related disturbances. However, the present 48-dimensional representation does not explicitly encode shaft-order components or analytical bearing characteristic frequencies. Therefore, the TreeSHAP results are interpreted as feature-attribution-based evidence of the signal characteristics used by the classifier rather than as direct identification of individual physical fault mechanisms.
4.8. Diagnostic Results Under Strict Operating-Condition Separation
The main experiments evaluated few-shot diagnostic performance when the task data covered multiple speeds and loads. They did not require the support and query sets to be completely separated along a particular operating-condition dimension.
All controlled operating-condition experiments retained the run-disjoint three-way 3-shot setting. For each target class, the support runs were selected exclusively from the designated support condition, while the query runs were collected from the completely nonoverlapping target condition. Feature standardization was fitted using only the support runs, and the classifier settings were identical to those used in the main experiments. The reported results were calculated over 45 repeated task instances.
To further investigate the applicability boundaries of XGBoost, Random Forest, and RPN, three cross-speed tasks were constructed in which the support and query speeds were completely nonoverlapping. Two cross-load tasks were also constructed in which the support and query loads were completely nonoverlapping. The results are presented in
Table 15 and
Figure 8.
In the two strict cross-load tasks, XGBoost achieved Macro-F1 values of 1.0000 and 0.9836 for the 20 → 40 N·m and 40 → 20 N·m directions, respectively. Random Forest achieved similarly high values of 0.9975 and 0.9950. These results demonstrate that the multidomain vibration features maintained stable diagnostic performance across the investigated load changes.
In the strict cross-speed tasks, RPN achieved the highest mean Macro-F1 in all three directions. XGBoost obtained Macro-F1 values of 0.4067, 0.6238, and 0.5667, with its best result observed when the support runs were collected at 2000 r/min. The contrast between the cross-load and cross-speed results suggests that the fixed-frequency features are more strongly affected by rotational-frequency shifts than by the load variations represented in the dataset. This finding motivates the future incorporation of order-domain or rotational-speed-normalized spectral features.
Accordingly, the present results should not be interpreted as evidence of general cross-speed robustness. The variable-condition experiments primarily demonstrate diagnosis when multiple operating conditions are represented within the few-shot tasks and under the investigated cross-load transfers, whereas strict cross-speed generalization remains a limitation of the current fixed-frequency representation.