id stringlengths 11 26 | subset stringclasses 2
values | task_category stringclasses 5
values | asset_class stringclasses 8
values | source_dataset stringlengths 3 23 | question stringlengths 56 1.36k | question_operator_style stringlengths 0 167 | required_tools listlengths 0 8 | procedure stringlengths 20 1.34k | ground_truth stringlengths 124 1.82k | metadata stringlengths 111 763 | known_issue stringlengths 0 190 |
|---|---|---|---|---|---|---|---|---|---|---|---|
pdm_rul_001 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD001 | I am managing a fleet of aircraft engines and need to know which ones are running on fumes. Can you predict the remaining useful life for all test engines in the CMAPSS FD001 dataset? I need predictions for every unit, verification against the actual RUL values we have, and then tell me which 10 engines are most likely... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | {"problem": "Predict the remaining useful life (RUL) for all test equipment units in the CMAPSS FD001 dataset.", "steps": "1) Load the CMAPSS FD001 training dataset using load_dataset(dataset_name='CMAPSS_FD001', split='train'). 2) Load the corresponding test dataset using load_dataset(dataset_name='CMAPSS_FD001', spli... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 17.6, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_mae": 10.49, "sota_model": "CAELSTM", "sota_rmse": 14.44, "sota_source": "Nature Scientific Reports 2025 - Deep learning-based prognostic approach"}, "expected_m... | {"dependency_analysis": "Sequential dependencies: load_dataset(train) -> provides training data for model training; load_dataset(test) -> provides test units for prediction; load_ground_truth -> required for verification and metric calculation. train_rul_model -> produces model object that must be used in predict_rul c... | ||
pdm_rul_002 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD002 | We have got bearing vibration data from CWRU and I need to figure out which bearings are about to give out. Can you predict how much life each test bearing has left, check those predictions against the actual failure times we recorded, and then show me degradation curves for the 5 bearings most at risk? I need the accu... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"detect_degradation_trend",
"calculate_rmse"
] | {"problem": "Predict RUL for bearing units in the CWRU dataset and analyze degradation trends.", "steps": "1) Load CWRU training data using load_dataset(dataset_name='CWRU', split='train'). 2) Load CWRU test data using load_dataset(dataset_name='CWRU', split='test'). 3) Load ground truth RUL values. 4) Train a bearing-... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 29.67, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "dataset_characteristics": "6 operating conditions, 1 fault mode (HPC degradation)"}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "Range [10, 25] ... | {"dependency_analysis": "Data loading -> model training -> prediction -> verification -> metric calculation -> visualization. The plot_degradation_trends tool requires both predictions and ground_truth, and operates on the top 5 risk units identified from predictions."} | The question text names CWRU, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_003 | rotating_aero | RUL Prediction | Bearing | FEMTO | The FEMTO dataset has bearings running under three different operational scenarios, and I suspect the RUL predictions might vary by scenario. Can you predict remaining life for all test bearings, break down the accuracy (MAE, RMSE) for each of the three operational scenarios separately, and tell me which scenario gives... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"analyze_engine_signals",
"calculate_rmse"
] | {"problem": "Predict RUL for bearings in FEMTO dataset across three operational scenarios and compare performance.", "steps": "1) Load FEMTO training data. 2) Load FEMTO test data. 3) Load ground truth RUL. 4) Identify three operational scenarios using identify_operational_scenarios(dataset='FEMTO'). 5) Train scenario-... | {"algorithm_reference": {"baseline_mae": 0.056, "baseline_model": "TCNMABG", "baseline_rmse": 0.082, "baseline_source": "MDPI Applied Sciences 2024", "metric_note": "FEMTO metrics in percentage of lifetime (0-1 scale)", "sota_model": "CNN-GRU-MHA", "sota_rmse": 0.0443, "sota_source": "MDPI 2024 - Transfer Learning for ... | {"complexity_level": "medium", "dependency_analysis": "Load data -> identify scenarios -> train separate models per scenario -> predict per scenario -> verify per scenario -> calculate metrics per scenario -> comparative analysis."} | FEMTO: the expected MAE/RMSE ranges do not state their unit (rul_percentage is 0-1); a constant 50% prediction lands just outside the MAE range. | |
pdm_rul_004 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD004 | The XJTU dataset has bearings with five different fault types, and I want to see if our RUL predictions are more accurate for certain fault types. Can you predict remaining life for all test bearings, give me overall accuracy numbers, then break it down by fault type so I can see which fault types we predict best? This... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"classify_faults",
"calculate_rmse"
] | {"problem": "Predict RUL for XJTU bearing dataset considering five different fault types.", "steps": "1) Load XJTU training and test data. 2) Load ground truth RUL. 3) Analyze fault types present using analyze_fault_types(dataset='XJTU'). 4) Train fault-type-specific RUL models. 5) Predict RUL for all test units. 6) Ve... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 31.84, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "dataset_characteristics": "6 operating conditions, 2 fault modes (HPC degradation + Fan degradation), most complex CMAPSS subset"}, "expected_mae_range": [10, 25], "... | {"dependency_analysis": "Data loading -> fault type analysis -> train fault-specific models -> predict -> verify -> calculate overall metrics -> calculate per-fault metrics -> comparative analysis."} | The question text names XJTU, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_005 | rotating_aero | RUL Prediction | Bearing | FEMTO | The IMS dataset has very high-frequency vibration data, and I am worried that units showing anomalies might have different RUL prediction accuracy. Can you predict remaining life for all test bearings, detect any anomalies in the sensor data, and then compare prediction accuracy between units with anomalies versus norm... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"detect_degradation_trend",
"calculate_rmse"
] | {"problem": "Predict RUL for IMS high-temporal-resolution bearing data with anomaly detection integration.", "steps": "1) Load IMS training data (high temporal resolution). 2) Load IMS test data. 3) Load ground truth RUL. 4) Perform anomaly detection on test data using detect_anomalies(dataset='IMS', method='isolation_... | {"algorithm_reference": {"baseline_model": "TCNMABG", "baseline_rmse": 0.082, "baseline_source": "MDPI Applied Sciences", "metric_note": "FEMTO metrics in percentage of lifetime (0-1 scale)", "sota_model": "TcLstmNet-CBAM", "sota_source": "Nature Scientific Reports 2025"}, "expected_mae_range": [10, 25], "expected_mae_... | {"dependency_analysis": "Load data -> anomaly detection -> model training -> prediction -> anomaly flagging -> verification -> overall metrics -> anomaly-stratified metrics."} | The question text names IMS, while the `source_dataset` field and ground truth refer to FEMTO; the ground-truth units could not be re-derived from files in the repository. | |
pdm_rul_006 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD001 | The HUST dataset has bearings tested under different speeds and loads, which is great for seeing if our RUL predictions work across diverse conditions. Can you predict remaining life for all test bearings, give me overall accuracy, then break it down by speed/load combinations? I need to know if the model generalizes w... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"analyze_engine_signals",
"calculate_rmse"
] | {"problem": "Predict RUL for HUST bearings under varying speeds and loads, analyzing generalization across operating conditions.", "steps": "1) Load HUST training data (collected under varying speeds and loads). 2) Load HUST test data. 3) Load ground truth RUL. 4) Analyze operating conditions using analyze_operating_co... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 17.6, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Self-attention+BiGRU+BiLSTM", "sota_rmse": 11.74, "sota_source": "ScienceDirect 2024 - Multiscale Deep Transfer Learning"}, "expected_mae_range": [10, 2... | {"dependency_analysis": "Load data -> analyze operating conditions -> train model -> predict -> verify -> overall metrics -> group by conditions -> per-condition metrics -> generalization assessment."} | The question text names HUST, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_007 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD002 | The MFPT dataset was captured at a very high sampling rate (97.656KHz), so there is probably useful information in the frequency domain. Can you predict remaining life for all test bearings using both time and frequency domain features, verify the predictions, and tell me if adding frequency analysis improves accuracy ... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"analyze_engine_signals",
"calculate_rmse"
] | {"problem": "Predict RUL for MFPT bearings using high-frequency vibration data (97.656KHz sampling rate) with frequency domain analysis.", "steps": "1) Load MFPT training data (high sampling rate). 2) Load MFPT test data. 3) Load ground truth RUL. 4) Perform frequency domain analysis using analyze_frequency_domain(data... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 29.67, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "dataset_characteristics": "6 operating conditions, frequency domain analysis applicable"}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "Range [10... | {"dependency_analysis": "Load data -> frequency domain analysis -> feature extraction -> train model with combined features -> predict -> verify -> calculate metrics -> compare feature contributions."} | The question text names MFPT, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_008 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD003 | The Paderborn dataset has multiple sensor types-vibration, motor current, torque, and speed-and I want to know which ones actually help predict bearing failure. Can you predict remaining life using all sensors together, then test each sensor type individually to see which gives the best predictions? I need to know if w... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"analyze_engine_signals",
"calculate_rmse"
] | {"problem": "Predict RUL for Paderborn bearings using multimodal sensor data (vibration, motor current, torque, speed).", "steps": "1) Load Paderborn training data (multimodal: vibration, current, torque, speed). 2) Load Paderborn test data. 3) Load ground truth RUL. 4) Analyze multimodal sensor contributions using ana... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 17.62, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Self-attention+BiGRU+BiLSTM", "sota_rmse": 13.5, "sota_source": "ScienceDirect 2024 - Multi-attention Mechanism"}, "expected_mae_range": [10, 25], "exp... | {"dependency_analysis": "Load multimodal data -> analyze sensor contributions -> train model with all sensors -> predict -> verify -> calculate metrics -> train separate models per sensor -> compare accuracy -> rank sensor importance."} | The question text names Paderborn, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_009 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD004 | The Mendeley dataset has bearings running at speeds that constantly change between 600 and 1800 RPM, making the vibration signals non-stationary. Can you predict remaining life for all test bearings, accounting for these changing conditions, and show me how prediction accuracy varies across different speed ranges? I ne... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | {"problem": "Predict RUL for Mendeley bearings under non-stationary conditions (varying speed 600-1800RPM).", "steps": "1) Load Mendeley training data (non-stationary: speed 600-1800RPM). 2) Load Mendeley test data. 3) Load ground truth RUL. 4) Handle non-stationary signal characteristics using handle_non_stationary_da... | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 31.84, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Multi-attention Mechanism", "sota_rmse": 26.5, "sota_source": "ScienceDirect 2024"}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "R... | {"dependency_analysis": "Load non-stationary data -> apply non-stationary handling -> train adapted model -> predict -> verify -> calculate metrics -> analyze by speed range."} | ||
pdm_rul_010 | rotating_aero | RUL Prediction | Bearing | FEMTO | The Azure dataset is huge-over 876,000 samples-so I need RUL predictions that can actually run efficiently. Can you predict remaining life for all test units, verify the predictions, give me accuracy numbers, and also tell me how long it took and how much memory it used? I need to know if this is practical for producti... | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | {"problem": "Predict RUL for Azure dataset (876K+ samples) requiring efficient large-scale processing.", "steps": "1) Load Azure training data (876K+ samples, efficient loading required). 2) Load Azure test data. 3) Load ground truth RUL. 4) Handle large dataset efficiently using handle_large_dataset(dataset='Azure', m... | {"algorithm_reference": {"baseline_mae": 0.056, "baseline_model": "TCNMABG", "baseline_rmse": 0.082, "baseline_source": "MDPI 2024 - Temporal Convolutional Multi-Attention", "sota_model": "CNN-GRU-MHA", "sota_rmse": 0.0443, "sota_source": "MDPI 2024 - Transfer Learning for Bearing RUL"}, "expected_mae_range": [10, 25],... | {"dependency_analysis": "Load large dataset efficiently -> batch processing -> train with batches -> batch prediction -> verify -> calculate metrics -> performance benchmarking."} | FEMTO: the expected MAE/RMSE ranges do not state their unit (rul_percentage is 0-1); a constant 50% prediction lands just outside the MAE range. | |
pdm_fault_001 | rotating_aero | Fault Classification | Bearing | CWRU | I have got CWRU bearing data with different fault types-inner race defects, outer race defects, and ball race defects. Can you classify which fault type each test bearing has, check those classifications against the actual fault labels, and give me accuracy numbers plus a breakdown of how well you classified each fault... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify bearing faults in CWRU dataset (inner race, outer race, ball race defects).", "steps": "1) Load CWRU training data. 2) Load CWRU test data. 3) Load ground truth fault labels. 4) Train fault classification model using train_fault_classifier(dataset='CWRU', fault_types=['inner_race', 'outer_race', '... | {"algorithm_reference": {"baseline_accuracy": 0.99, "baseline_model": "CNN-LSTM-GRU", "baseline_source": "MDPI 2024 - Hybrid Deep Learning for Bearing Fault Classification", "sota_accuracy": 1.0, "sota_model": "CNN-BLSTM", "sota_source": "Wiley 2021 - Bidirectional LSTM for Rotating Machinery Fault Diagnosis"}, "expect... | {"dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate overall accuracy -> generate confusion matrix -> calculate per-fault metrics."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_002 | rotating_aero | Fault Classification | Bearing | XJTU | The XJTU dataset has five different fault types, and I suspect we might classify early-stage faults differently than late-stage ones. Can you classify all test bearings by fault type, give me overall and per-fault-type accuracy, and then break down accuracy by fault severity? I need to know if we catch faults better wh... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify five different fault types in XJTU dataset and analyze classification performance by fault severity.", "steps": "1) Load XJTU training data. 2) Load XJTU test data. 3) Load ground truth fault labels (5 fault types). 4) Analyze fault severity levels using analyze_fault_severity(dataset='XJTU'). 5) ... | {"algorithm_reference": {"baseline_accuracy": 0.92, "baseline_model": "CNN", "baseline_source": "XJTU-SY benchmark papers", "sota_accuracy": 0.97, "sota_model": "Transfer Learning CNN", "sota_source": "Domain adaptation for bearing fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_range_rat... | {"dependency_analysis": "Load data -> analyze severity -> train classifier -> classify -> verify -> overall accuracy -> per-fault accuracy -> severity-stratified analysis."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_003 | rotating_aero | Fault Classification | Electric motor | ElectricMotorVibrations | We have both acoustic and vibration data for electric motors, and I want to know if using both helps classify faults better than using just one. Can you classify all test motor faults using the combined acoustic and vibration data, then test each modality separately to see which gives better accuracy? I need concrete n... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy",
"analyze_engine_signals"
] | {"problem": "Classify motor faults using multimodal acoustic and vibrational data from Electric Motor Vibrations dataset.", "steps": "1) Load Electric Motor Vibrations training data (acoustic + vibrational). 2) Load test data. 3) Load ground truth fault labels. 4) Analyze multimodal signal contributions using analyze_m... | {"algorithm_reference": {"baseline_accuracy": 0.9, "baseline_model": "Single-modal CNN", "baseline_source": "Electric motor fault diagnosis benchmarks", "sota_accuracy": 0.97, "sota_model": "Multimodal Fusion CNN", "sota_source": "Acoustic-vibration fusion for motor diagnostics"}, "expected_accuracy_range": [0.85, 0.98... | {"dependency_analysis": "Load multimodal data -> analyze modalities -> train combined classifier -> classify -> verify -> calculate accuracy -> train separate classifiers per modality -> compare accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_004 | rotating_aero | Fault Classification | Induction motor | RotorBrokenBar | We have induction motor data with broken rotor bars, and the severity ranges from 1 to 4 broken bars. Can you classify the severity level for each test motor, verify against the actual labels, and give me accuracy broken down by severity level? I also need a confusion matrix to see if the model confuses certain severit... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify broken rotor bar faults in induction motors with severity levels (1-4 broken bars).", "steps": "1) Load RotorBrokenBar training data. 2) Load test data. 3) Load ground truth labels (severity: 1-4 broken bars). 4) Analyze fault severity levels using analyze_fault_severity_levels(dataset='RotorBroke... | {"algorithm_reference": {"baseline_accuracy": 0.88, "baseline_model": "CNN", "baseline_source": "Rotor fault severity classification benchmarks", "sota_accuracy": 0.95, "sota_model": "Deep Residual Network", "sota_source": "Induction motor fault severity diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_a... | {"dependency_analysis": "Load data -> analyze severity levels -> train multi-class classifier -> classify -> verify -> overall accuracy -> per-severity accuracy -> confusion matrix generation."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_005 | rotating_aero | Fault Classification | Gearbox | PlanetaryPdM | The planetary gearbox dataset has faults in different components-sun gear cracks, planet spalling, ring gear issues. Can you classify which component has the fault for each test gearbox, verify those classifications, and give me accuracy numbers overall and per component? This is for root cause analysis, so I need to k... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify and localize faults in planetary gearbox (sun gear crack, planet spalling, etc.) for root cause analysis.", "steps": "1) Load PlanetaryPdM training data. 2) Load test data. 3) Load ground truth fault labels (component-specific: sun gear, planet, etc.). 4) Localize fault components using localize_f... | {"algorithm_reference": {"baseline_accuracy": 0.89, "baseline_model": "CNN-1D", "baseline_source": "Planetary gearbox fault diagnosis benchmarks", "sota_accuracy": 0.96, "sota_model": "Attention-based CNN", "sota_source": "Component-level gearbox fault localization"}, "expected_accuracy_range": [0.85, 0.98], "expected_... | {"dependency_analysis": "Load data -> component localization -> train component-specific classifier -> classify and localize -> verify -> overall accuracy -> per-component accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_006 | rotating_aero | Fault Classification | Bearing | Paderborn | The Paderborn dataset has both artificially induced and naturally occurring bearing faults. Can you classify the fault types for all test bearings, distinguish whether each fault was artificial or natural, and compare classification accuracy between the two? I need to know if our model works equally well on both types ... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify bearing faults in Paderborn dataset, distinguishing between artificially induced and naturally induced degradation.", "steps": "1) Load Paderborn training data (artificial + natural faults). 2) Load test data. 3) Load ground truth labels (fault type + induction method). 4) Distinguish artificial v... | {"algorithm_reference": {"baseline_accuracy": 0.91, "baseline_model": "CNN", "baseline_source": "Paderborn bearing fault benchmark", "sota_accuracy": 0.99, "sota_model": "FaultNet", "sota_source": "arXiv - Deep Learning for Bearing Fault Diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_range_rat... | {"dependency_analysis": "Load data -> distinguish induction methods -> train classifier -> classify -> verify -> overall accuracy -> separate accuracy for artificial vs. natural -> comparison analysis."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_007 | rotating_aero | Fault Classification | Bearing | HUST | The HUST dataset has 5 different bearing types with 6 fault categories, all tested under varying speeds and loads. Can you classify the fault category for each test bearing, give me overall accuracy plus breakdowns by fault category and bearing type, and check if accuracy changes with operating conditions? I need a com... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy",
"analyze_engine_signals"
] | {"problem": "Classify 6 fault categories across 5 bearing types in HUST dataset under varying speeds and loads.", "steps": "1) Load HUST training data (5 bearing types, 6 fault categories, varying conditions). 2) Load test data. 3) Load ground truth labels. 4) Analyze operating conditions using analyze_operating_condit... | {"algorithm_reference": {"baseline_accuracy": 0.88, "baseline_model": "CNN", "baseline_source": "HUST bearing fault benchmark", "sota_accuracy": 0.95, "sota_model": "Condition-aware Deep Network", "sota_source": "Multi-condition bearing fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_rang... | {"dependency_analysis": "Load data -> analyze conditions -> train classifier -> classify -> verify -> overall accuracy -> per-category accuracy -> per-bearing-type accuracy -> condition-stratified accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_008 | rotating_aero | Fault Classification | Bearing | MFPT | The MFPT dataset has bearings with inner and outer race defects tested under different load conditions. Can you classify which type of defect each test bearing has, verify the classifications, and show me if accuracy changes with load? I need to know if we should account for load when classifying faults. | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy",
"analyze_engine_signals"
] | {"problem": "Classify inner/outer race bearing defects in MFPT dataset under varying load conditions.", "steps": "1) Load MFPT training data (inner/outer race defects, varying loads). 2) Load test data. 3) Load ground truth labels. 4) Analyze load conditions using analyze_load_conditions(dataset='MFPT'). 5) Train fault... | {"algorithm_reference": {"baseline_accuracy": 0.94, "baseline_model": "CNN", "baseline_source": "MFPT bearing fault benchmark", "sota_accuracy": 0.98, "sota_model": "Load-aware CNN", "sota_source": "Variable-load bearing fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_range_rationale": "R... | {"dependency_analysis": "Load data -> analyze load conditions -> train classifier -> classify -> verify -> overall accuracy -> per-fault-type accuracy -> load-stratified accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_009 | rotating_aero | Fault Classification | Bearing | Mendeley | The Mendeley dataset has bearings with changing speeds (600-1800 RPM), making the signals non-stationary. Can you classify the fault types for all test bearings, accounting for these changing conditions, and show me how accuracy varies across speed ranges? I need to know if non-stationary conditions hurt classification... | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | {"problem": "Classify bearing faults in Mendeley dataset under non-stationary conditions (speed 600-1800RPM).", "steps": "1) Load Mendeley training data (non-stationary). 2) Load test data. 3) Load ground truth labels. 4) Handle non-stationary classification using handle_non_stationary_classification(dataset='Mendeley'... | {"algorithm_reference": {"baseline_accuracy": 0.87, "baseline_model": "CNN", "baseline_source": "Non-stationary bearing fault classification", "sota_accuracy": 0.94, "sota_model": "Speed-Invariant CNN", "sota_source": "Adaptive feature extraction for variable-speed machinery"}, "expected_accuracy_range": [0.85, 0.98], ... | {"dependency_analysis": "Load non-stationary data -> apply non-stationary handling -> train adapted classifier -> classify -> verify -> overall accuracy -> speed-range-stratified accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_010 | rotating_aero | Fault Classification | Gearbox | GearboxUoC | I have gearbox data from UoC and need to classify which components have faults. Can you classify the fault types for all test gearboxes, verify the classifications, and break down accuracy by gearbox component? I need to know which parts are hardest to diagnose. | [
"load_dataset",
"load_ground_truth",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy",
"analyze_engine_signals"
] | {"problem": "Classify gearbox faults in UoC dataset, analyzing classification performance across gearbox structural components.", "steps": "1) Load GearboxUoC training data. 2) Load test data. 3) Load ground truth fault labels. 4) Analyze gearbox structure using analyze_gearbox_structure(dataset='GearboxUoC'). 5) Train... | {"algorithm_reference": {"baseline_accuracy": 0.9, "baseline_model": "CNN", "baseline_source": "Gearbox fault diagnosis benchmarks", "sota_accuracy": 0.96, "sota_model": "Multi-scale CNN", "sota_source": "Structural component-aware gearbox fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_r... | {"dependency_analysis": "Load data -> analyze structure -> train classifier -> classify -> verify -> overall accuracy -> component-stratified accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_cost_benefit_001 | rotating_aero | Cost-Benefit Analysis | Turbofan engine | CMAPSS_FD001 | I am managing a fleet of aircraft engines and need to decide whether to do preventive maintenance or wait until failure. Can you predict remaining life for all test engines, calculate what it would cost to maintain them preventively versus letting them fail, and find the optimal maintenance threshold that minimizes tot... | [
"load_dataset",
"predict_rul",
"calculate_maintenance_cost",
"calculate_failure_cost",
"optimize_maintenance_schedule"
] | {"problem": "Perform cost-benefit analysis for CMAPSS FD001 engines comparing preventive maintenance vs. reactive maintenance strategies.", "steps": "1) Load CMAPSS FD001 test data. 2) Predict RUL for all test engines using predict_rul(dataset='CMAPSS_FD001'). 3) Calculate preventive maintenance cost using calculate_ma... | {"expected_cost_range": {"optimized": [3000, 40000], "preventive": [5000, 50000], "reactive": [50000, 500000]}, "expected_mae_range": [7, 18], "expected_mae_range_rationale": "MAE is calculated across ALL 100 test units in CMAPSS_FD001, not just the top 10 high-risk units. Ground truth statistics - Mean RUL: 75.5, Rang... | {"dependency_analysis": "Load data -> predict RUL -> calculate preventive cost -> calculate reactive cost -> optimize schedule -> compare strategies -> identify optimal threshold."} | Expected cost ranges depend on unit costs the question does not state; the MAE range is not meaningful for datasets without RUL labels. | |
pdm_cost_benefit_002 | rotating_aero | Cost-Benefit Analysis | Bearing | CWRU | We have bearings with different fault types-inner race, outer race, and ball race defects-and each costs different amounts to fix. Can you classify the fault type for each test bearing, calculate maintenance and failure costs for each fault type, prioritize which bearings to fix first based on cost-benefit, and tell me... | [
"load_dataset",
"classify_faults",
"calculate_maintenance_cost",
"optimize_maintenance_schedule",
"calculate_failure_cost"
] | {"problem": "Perform cost-benefit analysis for CWRU bearings comparing maintenance costs by fault type (inner race, outer race, ball race).", "steps": "1) Load CWRU test data. 2) Classify faults for all test bearings using classify_faults(dataset='CWRU'). 3) Calculate fault-specific maintenance costs using calculate_fa... | {"expected_cost_range": {"optimized": [3000, 40000], "preventive": [5000, 50000], "reactive": [50000, 500000]}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in CWRU, not just the top 10 high-risk units. Range represents typical model performance for this datas... | {"dependency_analysis": "Load data -> classify faults -> calculate fault-specific costs -> calculate fault-specific failure costs -> optimize priority -> compare costs -> identify best ROI fault type."} | Expected cost ranges depend on unit costs the question does not state; the MAE range is not meaningful for datasets without RUL labels. | |
pdm_cost_benefit_003 | rotating_aero | Cost-Benefit Analysis | Bearing | FEMTO | The FEMTO dataset has bearings running under three different operational scenarios, and maintenance costs vary by scenario. Can you predict remaining life for all test bearings in each scenario, calculate maintenance and failure costs per scenario, optimize the maintenance strategy for each scenario separately, and tel... | [
"load_dataset",
"predict_rul",
"analyze_engine_signals",
"calculate_maintenance_cost",
"optimize_maintenance_schedule"
] | {"problem": "Perform cost-benefit analysis for FEMTO bearings across three operational scenarios, optimizing maintenance strategy per scenario.", "steps": "1) Load FEMTO test data. 2) Identify three operational scenarios using identify_operational_scenarios(dataset='FEMTO'). 3) Predict RUL for all test units per scenar... | {"expected_cost_range": {"optimized": [3000, 40000], "preventive": [5000, 50000], "reactive": [50000, 500000]}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in FEMTO, not just the top 10 high-risk units. Range represents typical model performance for this data... | {"dependency_analysis": "Load data -> identify scenarios -> predict RUL per scenario -> calculate scenario costs -> optimize per scenario -> compare scenarios -> identify most critical scenario."} | Expected cost ranges depend on unit costs the question does not state; the MAE range is not meaningful for datasets without RUL labels. | |
pdm_cost_benefit_004 | rotating_aero | Cost-Benefit Analysis | Bearing | XJTU | For the XJTU bearings, I need a comprehensive maintenance plan that considers both how much life is left and what type of fault is present, since different faults cost different amounts to fix. Can you predict remaining life and classify fault types for all test bearings, calculate combined maintenance and failure cost... | [
"load_dataset",
"predict_rul",
"classify_faults",
"calculate_maintenance_cost",
"optimize_maintenance_schedule"
] | {"problem": "Perform integrated cost-benefit analysis for XJTU bearings combining RUL prediction and fault classification for comprehensive maintenance optimization.", "steps": "1) Load XJTU test data. 2) Predict RUL for all test units. 3) Classify fault types for all test units. 4) Calculate combined maintenance costs... | {"expected_cost_range": {"optimized": [3000, 40000], "preventive": [5000, 50000], "reactive": [50000, 500000]}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in XJTU, not just the top 10 high-risk units. Range represents typical model performance for this datas... | {"dependency_analysis": "Load data -> predict RUL -> classify faults -> calculate combined costs -> optimize multi-objective -> generate prioritized list."} | Expected cost ranges depend on unit costs the question does not state; the MAE range is not meaningful for datasets without RUL labels. | |
pdm_cost_benefit_005 | rotating_aero | Cost-Benefit Analysis | Industrial engine | Azure | We have a huge fleet (876K+ units) and I am wondering if we can save money by doing maintenance in bulk batches instead of individually. Can you predict remaining life for all test units, calculate what it costs to maintain them individually versus in bulk batches, optimize a fleet-wide maintenance schedule that takes ... | [
"load_dataset",
"predict_rul",
"calculate_maintenance_cost",
"optimize_maintenance_schedule"
] | {"problem": "Perform fleet-wide cost-benefit analysis for Azure dataset (876K+ samples) optimizing bulk maintenance scheduling.", "steps": "1) Load Azure test data (large-scale). 2) Predict RUL for all test units. 3) Calculate bulk maintenance costs using calculate_bulk_maintenance_cost(units=all_units, base_cost=3000,... | {"expected_cost_range": {"optimized": [3000, 40000], "preventive": [5000, 50000], "reactive": [50000, 500000]}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in Azure, not just the top 10 high-risk units. Range represents typical model performance for this data... | {"dependency_analysis": "Load large dataset -> predict RUL -> calculate bulk costs -> calculate individual costs -> optimize fleet schedule -> analyze economies of scale -> identify optimal batch sizes."} | Expected cost ranges depend on unit costs the question does not state; the MAE range is not meaningful for datasets without RUL labels. | |
pdm_safety_001 | rotating_aero | Safety/Policy Evaluation | Turbofan engine | CMAPSS_FD001 | I am responsible for aircraft engine safety and need to identify which engines pose safety risks. Can you predict remaining life for all test engines, flag any with less than 20 cycles left as high risk, assess the safety risks (catastrophic failure, safety hazards, environmental impact), check if they comply with FAA ... | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | {"problem": "Assess safety risks and policy compliance for CMAPSS FD001 engines with low predicted RUL.", "steps": "1) Load CMAPSS FD001 test data. 2) Predict RUL for all test engines. 3) Identify engines with predicted RUL < 20 cycles (high risk). 4) Assess safety risk for high-risk engines using assess_safety_risk(un... | {"expected_mae_range": [7, 18], "expected_mae_range_rationale": "MAE is calculated across ALL 100 test units in CMAPSS_FD001, not just the top 10 high-risk units. Ground truth statistics - Mean RUL: 75.5, Range: 7-145. Expected MAE range represents typical model performance for this dataset.", "expected_output_format":... | {"dependency_analysis": "Load data -> predict RUL -> identify high-risk units -> assess safety risk -> check compliance -> generate recommendations -> classify risk levels."} | ||
pdm_safety_002 | rotating_aero | Safety/Policy Evaluation | Bearing | CWRU | Different bearing fault types have different safety implications. Can you classify the fault types for all test bearings, assess the safety impact of each fault type (vibration severity, failure probability, downtime risk), check compliance with ISO and ANSI vibration standards, and generate safety protocols for each f... | [
"load_dataset",
"classify_faults",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | {"problem": "Assess safety impact of different bearing fault types (inner race, outer race, ball race) and generate safety protocols.", "steps": "1) Load CWRU test data. 2) Classify faults for all test bearings. 3) Assess safety impact by fault type using assess_fault_safety_impact(fault_types=['inner_race', 'outer_rac... | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in CWRU, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": ["low", "... | {"dependency_analysis": "Load data -> classify faults -> assess safety impact per fault type -> check standards -> generate protocols -> rank by criticality."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_003 | rotating_aero | Safety/Policy Evaluation | Electric motor | ElectricMotorVibrations | Electric motor failures can be dangerous, especially with electrical hazards and fire risks. Can you classify the motor faults, assess safety risks (electrical hazards, fire risk, mechanical failure), check compliance with IEC and NEMA standards, and generate emergency shutdown protocols for high-risk motors? I need cl... | [
"load_dataset",
"classify_faults",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | {"problem": "Assess safety risks for electric motor faults and generate emergency shutdown protocols.", "steps": "1) Load Electric Motor Vibrations test data. 2) Classify motor faults. 3) Assess motor safety risks using assess_motor_safety(faults=classifications, risk_factors=['electrical_hazard', 'fire_risk', 'mechani... | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in ElectricMotorVibrations, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk... | {"dependency_analysis": "Load data -> classify faults -> assess motor safety -> check electrical standards -> generate shutdown protocols -> classify risk levels."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_004 | rotating_aero | Safety/Policy Evaluation | Induction motor | RotorBrokenBar | Broken rotor bars in induction motors get more dangerous as severity increases. Can you classify the severity level (1-4 broken bars) for each test motor, assess safety risks for each severity level, check compliance with IEEE and IEC motor standards, and generate maintenance policies that specify when to shut down imm... | [
"load_dataset",
"classify_faults",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | {"problem": "Assess safety risks for broken rotor bar faults with severity levels (1-4 bars) and generate maintenance policies.", "steps": "1) Load RotorBrokenBar test data. 2) Classify fault severity (1-4 broken bars). 3) Assess safety by severity level using assess_severity_safety(severity_levels=[1,2,3,4], safety_me... | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in RotorBrokenBar, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels":... | {"dependency_analysis": "Load data -> classify severity -> assess safety per severity -> check standards -> generate policies -> define action thresholds."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_005 | rotating_aero | Safety/Policy Evaluation | Gearbox | PlanetaryPdM | Planetary gearboxes have complex structures, and faults in different components have different safety implications. Can you classify the faults and identify which component (sun gear, planet, ring gear) is affected, assess safety risks for each component type, check compliance with AGMA and ISO gear standards, and gene... | [
"load_dataset",
"classify_faults",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | {"problem": "Assess safety risks for planetary gearbox component-specific faults and generate component-targeted zsafety policies.", "steps": "1) Load PlanetaryPdM test data. 2) Classify faults and localize components (sun gear, planet gear, ring gear). 3) Assess gearbox safety by component using assess_gearbox_safety(... | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in PlanetaryPdM, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": [... | {"dependency_analysis": "Load data -> classify and localize faults -> assess safety per component -> check standards -> generate component policies -> rank by criticality."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_rul_011 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD001 | Predict remaining useful life for IMS equipment and identify the 5 units most at risk. | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | Predict RUL for IMS dataset and identify top 5 risk units. | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 17.6, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_mae": 10.49, "sota_model": "CAELSTM", "sota_rmse": 14.44, "sota_source": "Nature Scientific Reports 2025 - Deep learning-based prognostic approach"}, "expected_m... | {"complexity": "Medium", "dependency_analysis": "Load data -> train model -> predict -> verify -> rank by risk."} | The question text names IMS, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_012 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD002 | Predict remaining useful life for HUST equipment and identify the 5 units most at risk. | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | Predict RUL for HUST dataset and identify top 5 risk units. | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 29.67, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Multi-attention Mechanism", "sota_rmse": 23.5, "sota_source": "ScienceDirect 2024"}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "R... | {"complexity": "High", "dependency_analysis": "Load data -> train model -> predict -> verify -> rank by risk."} | The question text names HUST, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_013 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD003 | Predict remaining useful life for MFPT equipment and identify the 5 units most at risk. | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | Predict RUL for MFPT dataset and identify top 5 risk units. | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 17.62, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Self-attention+BiGRU+BiLSTM", "sota_rmse": 13.5, "sota_source": "ScienceDirect 2024 - Multi-attention Mechanism"}, "expected_mae_range": [10, 25], "exp... | {"complexity": "Medium", "dependency_analysis": "Load data -> train model -> predict -> verify -> rank by risk."} | The question text names MFPT, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_014 | rotating_aero | RUL Prediction | Turbofan engine | CMAPSS_FD004 | Predict remaining useful life for Paderborn equipment and identify the 5 units most at risk. | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | Predict RUL for Paderborn dataset and identify top 5 risk units. | {"algorithm_reference": {"baseline_model": "BiLSTM", "baseline_rmse": 31.84, "baseline_source": "arXiv 2025 - Uncertainty-Aware Deep Learning Framework", "sota_model": "Multi-attention Mechanism", "sota_rmse": 26.5, "sota_source": "ScienceDirect 2024"}, "expected_mae_range": [10, 25], "expected_mae_range_rationale": "R... | {"complexity": "High", "dependency_analysis": "Load data -> train model -> predict -> verify -> rank by risk."} | The question text names Paderborn, but the ground truth is computed on the C-MAPSS subset in the `source_dataset` field. The field is correct; the question text is not. Fix planned for v1.1. | |
pdm_rul_015 | rotating_aero | RUL Prediction | Bearing | FEMTO | Predict remaining useful life for Mendeley equipment and identify the 5 units most at risk. | [
"load_dataset",
"load_ground_truth",
"train_rul_model",
"predict_rul",
"verify_ground_truth",
"calculate_mae",
"calculate_rmse"
] | Predict RUL for Mendeley dataset and identify top 5 risk units. | {"algorithm_reference": {"baseline_mae": 0.056, "baseline_model": "TCNMABG", "baseline_rmse": 0.082, "baseline_source": "MDPI 2024 - Temporal Convolutional Multi-Attention", "sota_model": "TcLstmNet-CBAM", "sota_performance": "Best MAE on 11/14 bearings", "sota_source": "Nature Scientific Reports 2025"}, "expected_mae_... | {"complexity": "Medium", "dependency_analysis": "Load data -> train model -> predict -> verify -> rank by risk."} | FEMTO: the expected MAE/RMSE ranges do not state their unit (rul_percentage is 0-1); a constant 50% prediction lands just outside the MAE range. | |
pdm_fault_011 | rotating_aero | Fault Classification | Bearing | Paderborn | Classify fault types for all test units in Paderborn dataset. | [
"load_dataset",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | Classify faults in Paderborn dataset. | {"algorithm_reference": {"baseline_accuracy": 0.92, "baseline_model": "CNN", "baseline_source": "Paderborn bearing fault benchmark", "sota_accuracy": 0.99, "sota_model": "FaultNet", "sota_source": "arXiv - Deep Learning for Bearing Fault Diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_range_rat... | {"complexity": "High", "dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_012 | rotating_aero | Fault Classification | Bearing | HUST | Classify fault types for all test units in HUST dataset. | [
"load_dataset",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | Classify faults in HUST dataset. | {"algorithm_reference": {"baseline_accuracy": 0.88, "baseline_model": "CNN", "baseline_source": "HUST bearing fault benchmark", "sota_accuracy": 0.95, "sota_model": "Condition-aware Deep Network", "sota_source": "Multi-condition bearing fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_rang... | {"complexity": "High", "dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_013 | rotating_aero | Fault Classification | Bearing | MFPT | Classify fault types for all test units in MFPT dataset. | [
"load_dataset",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | Classify faults in MFPT dataset. | {"algorithm_reference": {"baseline_accuracy": 0.94, "baseline_model": "CNN", "baseline_source": "MFPT bearing fault benchmark", "sota_accuracy": 0.98, "sota_model": "Load-aware CNN", "sota_source": "Variable-load bearing fault diagnosis"}, "expected_accuracy_range": [0.85, 0.98], "expected_accuracy_range_rationale": "R... | {"complexity": "High", "dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_014 | rotating_aero | Fault Classification | Bearing | Mendeley | Classify fault types for all test units in Mendeley dataset. | [
"load_dataset",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | Classify faults in Mendeley dataset. | {"algorithm_reference": {"baseline_accuracy": 0.87, "baseline_model": "CNN", "baseline_source": "Non-stationary bearing fault classification", "sota_accuracy": 0.94, "sota_model": "Speed-Invariant CNN", "sota_source": "Adaptive feature extraction for variable-speed machinery"}, "expected_accuracy_range": [0.85, 0.98], ... | {"complexity": "High", "dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_fault_015 | rotating_aero | Fault Classification | Electric motor | ElectricMotorVibrations | Classify fault types for all test units in ElectricMotorVibrations dataset. | [
"load_dataset",
"train_fault_classifier",
"classify_faults",
"verify_classification",
"calculate_accuracy"
] | Classify faults in ElectricMotorVibrations dataset. | {"algorithm_reference": {"baseline_accuracy": 0.9, "baseline_model": "Single-modal CNN", "baseline_source": "Electric motor fault diagnosis benchmarks", "sota_accuracy": 0.97, "sota_model": "Multimodal Fusion CNN", "sota_source": "Acoustic-vibration fusion for motor diagnostics"}, "expected_accuracy_range": [0.85, 0.98... | {"complexity": "High", "dependency_analysis": "Load data -> train classifier -> classify -> verify -> calculate accuracy."} | expected_fault_types holds a placeholder ("Fault_0") left by an earlier tool stub; the accuracy range [0.85, 0.98] is generic. | |
pdm_safety_006 | rotating_aero | Safety/Policy Evaluation | Turbofan engine | CMAPSS_FD001 | Identify safety risks and compliance issues for CMAPSS_FD001 equipment. | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | Assess safety risks for CMAPSS_FD001 equipment with low predicted RUL. | {"expected_mae_range": [7, 18], "expected_mae_range_rationale": "MAE is calculated across ALL 100 test units in CMAPSS_FD001, not just the top 10 high-risk units. Ground truth statistics - Mean RUL: 75.5, Range: 7-145. Expected MAE range represents typical model performance for this dataset.", "expected_output_format":... | {"complexity": "High", "dependency_analysis": "Load data -> predict RUL -> assess risk -> check compliance -> generate recommendations."} | ||
pdm_safety_007 | rotating_aero | Safety/Policy Evaluation | Bearing | CWRU | Identify safety risks and compliance issues for CWRU equipment. | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | Assess safety risks for CWRU equipment with low predicted RUL. | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in CWRU, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": ["low", "... | {"complexity": "High", "dependency_analysis": "Load data -> predict RUL -> assess risk -> check compliance -> generate recommendations."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_008 | rotating_aero | Safety/Policy Evaluation | Bearing | FEMTO | Identify safety risks and compliance issues for FEMTO equipment. | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | Assess safety risks for FEMTO equipment with low predicted RUL. | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in FEMTO, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": ["low", ... | {"complexity": "High", "dependency_analysis": "Load data -> predict RUL -> assess risk -> check compliance -> generate recommendations."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_009 | rotating_aero | Safety/Policy Evaluation | Bearing | XJTU | Identify safety risks and compliance issues for XJTU equipment. | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | Assess safety risks for XJTU equipment with low predicted RUL. | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in XJTU, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": ["low", "... | {"complexity": "High", "dependency_analysis": "Load data -> predict RUL -> assess risk -> check compliance -> generate recommendations."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
pdm_safety_010 | rotating_aero | Safety/Policy Evaluation | Bearing | IMS | Identify safety risks and compliance issues for IMS equipment. | [
"load_dataset",
"predict_rul",
"assess_safety_risk",
"check_compliance",
"generate_safety_recommendations"
] | Assess safety risks for IMS equipment with low predicted RUL. | {"expected_mae_range": [10, 25], "expected_mae_range_rationale": "MAE is calculated across ALL test units in IMS, not just the top 10 high-risk units. Range represents typical model performance for this dataset based on historical benchmarks.", "expected_output_format": "json_report", "expected_risk_levels": ["low", "m... | {"complexity": "High", "dependency_analysis": "Load data -> predict RUL -> assess risk -> check compliance -> generate recommendations."} | Ground truth specifies only the allowed risk levels (and placeholder sample units); no unit-level answer can be checked. | |
engine_health_combined_001 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I need a complete health assessment for this aircraft engine based on the following sensor data from a single operational cycle. Analyze all major components and give me: (1) Health status for each component (Fan, LPC, HPC, HPT, LPT) - Healthy or Fault, (2) If there are timing issues, identify whether they're caused by... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Healthy", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": [], "overall_health_state": "Operating Normally", "rationale": "Ground truth from EngineMTQA engine 108410. Health state: Operatin... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "108410"} | Ground truth lists no faulty components, while its own root-cause note cites LPT efficiency and flow modifiers; pending SME adjudication. | |
engine_health_combined_002 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our maintenance team needs an urgent diagnostic report for this engine. Review the sensor readings below and determine: which components are functioning normally, which have faults, what's causing any timing anomalies, and the engine's overall operational status.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Op... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Healthy", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": [], "overall_health_state": "Operating Normally", "rationale": "Ground truth from EngineMTQA engine 20119. Health state: Operating... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "20119"} | ||
engine_health_combined_003 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Before this aircraft's next flight, I need you to analyze the engine telemetry and provide a full component-by-component health assessment. Check Fan, LPC, HPC, HPT, and LPT systems, identify any efficiency or flow issues, and classify the overall engine condition.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Healthy", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": [], "overall_health_state": "Operating Normally", "rationale": "Ground truth from EngineMTQA engine 8389. Health state: Operating ... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "8389"} | ||
engine_health_combined_004 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine flagged an alert during the last flight. Analyze the sensor data and tell me: (1) Which specific components show signs of malfunction? (2) Are the timing problems related to efficiency degradation or flow restrictions? (3) Should we ground this aircraft for maintenance?
ENGINE SIGNAL DATA SUMMARY (1 operat... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Fault", "HPC": "Fault", "HPT": "Fault", "LPC": "Fault", "LPT": "Fault"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["Fan", "LPC", "HPC", "HPT", "LPT"], "overall_health_state": "Abnormal Degradation", "rationale": "Ground truth from EngineMTQA engine 60739... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "60739"} | ||
engine_health_combined_005 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I need a complete health assessment for this aircraft engine based on the following sensor data from a single operational cycle. Analyze all major components and give me: (1) Health status for each component (Fan, LPC, HPC, HPT, LPT) - Healthy or Fault, (2) If there are timing issues, identify whether they're caused by... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT"], "overall_health_state": "Abnormal Degradation", "rationale": "Ground truth from EngineMTQA engine 78384. Health state: Abno... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "78384"} | ||
engine_health_combined_006 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our maintenance team needs an urgent diagnostic report for this engine. Review the sensor readings below and determine: which components are functioning normally, which have faults, what's causing any timing anomalies, and the engine's overall operational status.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Op... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Fault", "HPT": "Healthy", "LPC": "Fault", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["LPC", "HPC"], "overall_health_state": "Abnormal Degradation", "rationale": "Ground truth from EngineMTQA engine 46790. Health state:... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "46790"} | ||
engine_health_combined_007 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Before this aircraft's next flight, I need you to analyze the engine telemetry and provide a full component-by-component health assessment. Check Fan, LPC, HPC, HPT, and LPT systems, identify any efficiency or flow issues, and classify the overall engine condition.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Fault"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT", "LPT"], "overall_health_state": "Abnormal Degradation", "rationale": "Ground truth from EngineMTQA engine 24953. Health state:... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "24953"} | ||
engine_health_combined_008 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine flagged an alert during the last flight. Analyze the sensor data and tell me: (1) Which specific components show signs of malfunction? (2) Are the timing problems related to efficiency degradation or flow restrictions? (3) Should we ground this aircraft for maintenance?
ENGINE SIGNAL DATA SUMMARY (1 operat... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Fault"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Ground truth from EngineMTQA engine 20495. Health state: Imm... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "20495"} | Question text is identical to engine_health_combined_012; all checkable ground-truth fields agree (benign duplicate). | |
engine_health_combined_009 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I need a complete health assessment for this aircraft engine based on the following sensor data from a single operational cycle. Analyze all major components and give me: (1) Health status for each component (Fan, LPC, HPC, HPT, LPT) - Healthy or Fault, (2) If there are timing issues, identify whether they're caused by... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT"], "overall_health_state": "Imminent Failure", "rationale": "Ground truth from EngineMTQA engine 77593. Health state: Imminent... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "77593"} | ||
engine_health_combined_010 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our maintenance team needs an urgent diagnostic report for this engine. Review the sensor readings below and determine: which components are functioning normally, which have faults, what's causing any timing anomalies, and the engine's overall operational status.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Op... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Healthy", "LPC": "Fault", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["LPC"], "overall_health_state": "Imminent Failure", "rationale": "Ground truth from EngineMTQA engine 107977. Health state: Imminen... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "107977"} | ||
engine_health_combined_011 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Before this aircraft's next flight, I need you to analyze the engine telemetry and provide a full component-by-component health assessment. Check Fan, LPC, HPC, HPT, and LPT systems, identify any efficiency or flow issues, and classify the overall engine condition.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT"], "overall_health_state": "Imminent Failure", "rationale": "Ground truth from EngineMTQA engine 3966. Health state: Imminent ... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "3966"} | ||
engine_health_combined_012 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine flagged an alert during the last flight. Analyze the sensor data and tell me: (1) Which specific components show signs of malfunction? (2) Are the timing problems related to efficiency degradation or flow restrictions? (3) Should we ground this aircraft for maintenance?
ENGINE SIGNAL DATA SUMMARY (1 operat... | [
"analyze_engine_signals",
"assess_component_health",
"diagnose_timing_issues"
] | 1. Parse embedded sensor data summary. 2. Analyze each component's sensor readings for anomalies. 3. Determine health status (Healthy/Fault) for Fan, LPC, HPC, HPT, LPT. 4. Identify root cause of timing issues (efficiency vs flow modifier). 5. Classify overall health state (Operating Normally/Abnormal Degradation/Immin... | {"component_health": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Fault"}, "expected_answer_type": "structured_health_assessment", "faulty_components": ["HPT", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Ground truth from EngineMTQA engine 9788. Health state: Immi... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "comprehensive_component_assessment", "source_engine_id": "9788"} | Question text is identical to engine_health_combined_008; all checkable ground-truth fields agree (benign duplicate). | |
engine_health_combined_013 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I've collected engine telemetry across 10 operational cycles and need a trend analysis. Based on this data: (1) What is the qualitative condition of the engine (Good/Moderate/Poor/Bad/Extremely Poor)? (2) What's the estimated probability range of engine failure? (3) What maintenance actions should we take?
ENGINE SIGN... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "10%-30%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["106656", "106678", "106703", "106716", "106741", "106779", "106797", "106828", "106851", "106874"]} | Question text is identical to engine_health_combined_017, but the two ground truths disagree on qualitative_condition. | |
engine_health_combined_014 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our predictive maintenance system flagged this engine for review. Analyze the 10-cycle trend data and provide: overall condition assessment, failure probability estimate, and your recommended maintenance strategy.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]
- Altitude: stable at 35,... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "10%-30%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["10240", "10254", "10272", "10287", "10306", "10333", "10357", "10373", "10398", "10422"]} | Same signal summary as engine_health_combined_013/017, which carry different ground truths (Good vs Moderate Condition). | |
engine_health_combined_015 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine is due for its scheduled inspection. Based on the multi-cycle signal data, assess whether the condition has degraded, estimate failure risk, and recommend whether to proceed with routine maintenance or escalate to urgent repairs.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "10%-30%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["39611", "39628", "39665", "39699", "39715", "39735", "39768", "39789", "39821", "39848"]} | Same signal summary as engine_health_combined_013/017, which carry different ground truths (Good vs Moderate Condition). | |
engine_health_combined_016 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Fleet management needs a health trend report for this engine unit. Analyze the 10-cycle data and provide: (1) Current condition classification, (2) Failure probability range for the next 50 cycles, (3) Specific maintenance recommendations.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]
... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "10%-30%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["39612", "39628", "39665", "39700", "39716", "39734", "39768", "39790", "39820", "39848"]} | Same signal summary as engine_health_combined_013/017, which carry different ground truths (Good vs Moderate Condition). | |
engine_health_combined_017 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I've collected engine telemetry across 10 operational cycles and need a trend analysis. Based on this data: (1) What is the qualitative condition of the engine (Good/Moderate/Poor/Bad/Extremely Poor)? (2) What's the estimated probability range of engine failure? (3) What maintenance actions should we take?
ENGINE SIGN... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "10%-30%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["89747", "89763", "89781", "89802", "89810", "89833", "89851", "89860", "89870", "89891"]} | Question text is identical to engine_health_combined_013, but the two ground truths disagree on qualitative_condition. | |
engine_health_combined_018 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our predictive maintenance system flagged this engine for review. Analyze the 10-cycle trend data and provide: overall condition assessment, failure probability estimate, and your recommended maintenance strategy.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]
- Altitude: stable at 35,... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "30%-50%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["100319", "100335", "100349", "100366", "100376", "100388", "100402", "100421", "100435", "100451"]} | Scenarios 018-020 share one signal summary but differ in failure_probability_range (30%-50% vs 70%-100%). | |
engine_health_combined_019 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine is due for its scheduled inspection. Based on the multi-cycle signal data, assess whether the condition has degraded, estimate failure risk, and recommend whether to proceed with routine maintenance or escalate to urgent repairs.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "70%-100%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitat... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["74131", "74165", "74189", "74213", "74231", "74257", "74275", "74308", "74334", "74363"]} | Scenarios 018-020 share one signal summary but differ in failure_probability_range (30%-50% vs 70%-100%). | |
engine_health_combined_020 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Fleet management needs a health trend report for this engine unit. Analyze the 10-cycle data and provide: (1) Current condition classification, (2) Failure probability range for the next 50 cycles, (3) Specific maintenance recommendations.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]
... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "70%-100%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitat... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["20473", "20490", "20502", "20514", "20534", "20543", "20555", "20574", "20584", "20603"]} | Scenarios 018-020 share one signal summary but differ in failure_probability_range (30%-50% vs 70%-100%). | |
engine_health_combined_021 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | I've collected engine telemetry across 10 operational cycles and need a trend analysis. Based on this data: (1) What is the qualitative condition of the engine (Good/Moderate/Poor/Bad/Extremely Poor)? (2) What's the estimated probability range of engine failure? (3) What maintenance actions should we take?
ENGINE SIGN... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "50%-70%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["112649", "112680", "112706", "112724", "112748", "112773", "112805", "112827", "112850", "112878"]} | ||
engine_health_combined_022 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Our predictive maintenance system flagged this engine for review. Analyze the 10-cycle trend data and provide: overall condition assessment, failure probability estimate, and your recommended maintenance strategy.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Operational Parameters]
- Altitude: fluctuating b... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data. 2. Analyze degradation patterns across cycles. 3. Classify qualitative condition. 4. Estimate failure probability based on trend severity. 5. Generate maintenance recommendations appropriate to condition. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "50%-70%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitati... | {"complexity": "High", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": ["16461", "16484", "16499", "16518", "16546", "16556", "16575", "16601", "16616", "16631"]} | ||
engine_health_combined_023 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Emergency diagnostic request: An engine fault indicator lit up during cruise. Review the telemetry and determine which components have failed, the nature of the timing issue, and the severity of the situation.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Operational Parameters]
- Altitude: fluctuating betwee... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["HPT"], "healthy_components": ["Fan", "LPC", "HPC", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Fault diagnosis fro... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "2364"} | ||
engine_health_combined_024 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Post-flight inspection revealed abnormal sensor readings. Diagnose which components are compromised, identify the root cause of any efficiency or flow anomalies, and assess whether immediate repair is needed.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Operational Parameters]
- Altitude: fluctuating between... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["HPT"], "healthy_components": ["Fan", "LPC", "HPC", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Fault diagnosis fro... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "4527"} | ||
engine_health_combined_025 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine experienced a performance anomaly mid-flight. Analyze the sensor data to identify: (1) Which components (Fan, LPC, HPC, HPT, LPT) are faulty? (2) What's the root cause - efficiency modifier issues or flow modifier problems? (3) Which specific subsystem is affected?
ENGINE SIGNAL DATA SUMMARY (1 operational... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["HPT"], "healthy_components": ["Fan", "LPC", "HPC", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Fault diagnosis fro... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "6781"} | ||
engine_health_combined_026 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Emergency diagnostic request: An engine fault indicator lit up during cruise. Review the telemetry and determine which components have failed, the nature of the timing issue, and the severity of the situation.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Operational Parameters]
- Altitude: stable at 35,000 f... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Healthy", "HPC": "Healthy", "HPT": "Fault", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["HPT"], "healthy_components": ["Fan", "LPC", "HPC", "LPT"], "overall_health_state": "Abnormal Degradation", "rationale": "Fault diagnosis... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "3102"} | ||
engine_health_combined_027 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Post-flight inspection revealed abnormal sensor readings. Diagnose which components are compromised, identify the root cause of any efficiency or flow anomalies, and assess whether immediate repair is needed.
ENGINE SIGNAL DATA SUMMARY (1 operational cycles):
[Operational Parameters]
- Altitude: stable at 35,000 ft... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Fault", "HPC": "Fault", "HPT": "Fault", "LPC": "Fault", "LPT": "Fault"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["Fan", "LPC", "HPC", "HPT", "LPT"], "healthy_components": [], "overall_health_state": "Abnormal Degradation", "rationale": "Fault diagnosis from ... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "114993"} | ||
engine_health_combined_028 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | This engine experienced a performance anomaly mid-flight. Analyze the sensor data to identify: (1) Which components (Fan, LPC, HPC, HPT, LPT) are faulty? (2) What's the root cause - efficiency modifier issues or flow modifier problems? (3) Which specific subsystem is affected?
ENGINE SIGNAL DATA SUMMARY (1 operational... | [
"analyze_engine_signals",
"diagnose_timing_issues"
] | 1. Parse sensor data for anomaly indicators. 2. Identify which components show fault signatures. 3. Analyze timing patterns to determine efficiency vs flow issues. 4. Pinpoint the affected subsystem. 5. Assess overall severity. | {"component_health_detail": {"Fan": "Fault", "HPC": "Healthy", "HPT": "Healthy", "LPC": "Healthy", "LPT": "Healthy"}, "expected_answer_type": "fault_diagnosis", "faulty_components": ["Fan"], "healthy_components": ["LPC", "HPC", "HPT", "LPT"], "overall_health_state": "Imminent Failure", "rationale": "Fault diagnosis fro... | {"complexity": "High", "is_closed_ended": true, "scenario_type": "fault_diagnosis", "source_engine_id": "93061"} | ||
engine_health_combined_029 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | URGENT: This engine is showing critical degradation across multiple systems. Analyze the 10-cycle trend data and determine: (1) The qualitative condition of the engine, (2) The probability range of imminent failure, (3) What emergency maintenance actions are needed?
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data showing severe degradation. 2. Analyze critical anomalies across multiple components. 3. Classify as Extremely Poor Condition. 4. Estimate high failure probability (70%-100%). 5. Generate urgent maintenance/grounding recommendations. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "70%-100%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitat... | {"complexity": "Critical", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": "synthetic_001"} | ||
engine_health_combined_030 | rotating_aero | Health Analysis | Aero-engine | EngineMTQA | Fleet alert: Engine performance has degraded severely over the past 10 cycles. Based on this critical sensor data, assess the overall condition, estimate failure probability, and recommend whether this engine should be immediately grounded for emergency repairs.
ENGINE SIGNAL DATA SUMMARY (10 operational cycles):
[Op... | [
"analyze_engine_signals",
"detect_degradation_trend",
"assess_component_health",
"optimize_maintenance_schedule"
] | 1. Parse 10-cycle sensor trend data showing severe degradation. 2. Analyze critical anomalies across multiple components. 3. Classify as Extremely Poor Condition. 4. Estimate high failure probability (70%-100%). 5. Generate urgent maintenance/grounding recommendations. | {"condition_options": ["Good Condition", "Moderate Condition", "Poor Condition", "Bad Condition", "Extremely Poor Condition"], "expected_answer_type": "trend_analysis_with_recommendations", "failure_probability_range": "70%-100%", "probability_options": ["1%-10%", "10%-30%", "30%-50%", "50%-70%", "70%-100%"], "qualitat... | {"complexity": "Critical", "is_closed_ended": false, "scenario_type": "multi_cycle_trend_analysis", "source_engine_ids": "synthetic_002"} | ||
bess_health_001 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Perform health analysis for battery B0005 from cycle 60 to 80. Identify the degradation stage, SOH percentage, and current capacity. | Can you check Battery 5 from about cycle 60 to cycle 80. Is it still healthy? | [
"fetch_cycle_summary",
"capacity_soh_calculator"
] | Analyze capacity data and compare against standard thresholds (91% for Healthy). | {"answer_type": "structured_categorical", "capacity": 1.5598, "soh_pct": 83.86, "source": "ground_truth.json:B0005:cycle_labels[80]", "stage": "EARLY_DEGRADATION"} | {"cognitive_category": "Perception", "data_provision_mode": "data_discovery", "dependency_analysis": ["Retrieve cycles 60-80 summary", "Execute SOH calculator with 1.86Ah rated capacity"], "difficulty": "easy", "disambiguation_criteria": ["cycle_end 80 determines current state", "SOH threshold maps to EARLY_DEGRADATION... | |
bess_health_002 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Retrieve discharge capacity for B0005 for the first 10 cycles and cycles 90-100. Calculate the percentage drop in capacity. | For Battery 5, compare the first 10 cycles with cycles 90 through 100. How much capacity has it lost? | [
"fetch_cycle_summary"
] | Time-sequence comparison of historical vs current capacity. | {"answer_type": "numeric_percentage", "capacity_drop_pct": 20.17, "current_avg_cap": 1.48, "initial_avg_cap": 1.854, "source": "data/processed/B0005_cycles.json"} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["Average capacity for cycles 0-10", "Average capacity for cycles 90-100", "Calculate relative drop"], "difficulty": "easy", "disambiguation_criteria": ["compute mean capacity in each requested window", "capacity_dro... | Ground truth uses the c100 endpoint (1.48 Ah, 20.17% drop) instead of the window means the question defines (1.515 Ah, 17.45%). |
bess_health_003 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Determine the degradation stage of B0005 at cycle 120 using the standard SOH thresholds (HEALTHY >= 90%, EARLY 80-90%, ACCELERATED 70-80%, EOL < 70%). Provide a maintenance recommendation chosen from {continue, monitor, plan replacement, replace immediately} based on the stage. Output: {stage, soh_pct, recommendation}. | Battery 5 has gone through about 120 cycles now. Should we keep cycling it, or is it time to plan something? Give me a maintenance call. | [
"capacity_soh_calculator"
] | Map technical state to operational decisions. | {"answer_type": "decision_choice", "recommendation": "Schedule for decommissioning or secondary use; prioritize replacement.", "source": "ground_truth.json:B0005:cycle_labels[120]", "stage": "ACCELERATED_DEGRADATION"} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["SOH at cycle 120", "Consult maintenance_manual.md for stage-action mapping"], "difficulty": "medium", "disambiguation_criteria": ["stage is based on cycle-120 SOH threshold", "ACCELERATED maps to plan replacement... | Question thresholds (90/80/70) differ from the benchmark's (91/83/75); the verdict is the same here. |
bess_health_004 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Calculate the cumulative thermal drift for battery B0005 from cycle 80 to cycle 120. Cumulative thermal drift is defined as max_temperature(cycle 120) - max_temperature(cycle 80). Report a single Celsius value, not a per-cycle rate. | For Battery 5, compare its temperature from cycle 80 to cycle 120. How much has it drifted? | [
"thermal_anomaly_checker",
"fetch_cycle_summary"
] | Identify cumulative thermal drift as a proxy for internal resistance increase. | {"answer_type": "numeric_trend", "classification": "normal_aging_related_rise", "source": "data/processed/B0005_cycles.json", "thermal_drift": 1.85} | {"cognitive_category": "Perception", "data_provision_mode": "data_discovery", "dependency_analysis": ["Trend analysis over 40 cycles", "Compare thermal baseline"], "difficulty": "medium", "disambiguation_criteria": ["thermal drift is cumulative max(end)-max(start)", "per-cycle rate is not the requested answer", "smooth... | |
bess_health_005 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Analyze the state of health for B0005 during cycles 0-20. Confirm its stage according to standard thresholds. | During the first 20 cycles for Battery 5, was it still in healthy condition? | [
"capacity_soh_calculator"
] | Confirm healthy operation baseline. | {"answer_type": "structured_categorical", "soh_pct": 99.8, "source": "ground_truth.json:B0005:cycle_labels[0-20]", "stage": "HEALTHY"} | {"cognitive_category": "Perception", "data_provision_mode": "data_discovery", "dependency_analysis": ["Verify SOH > 91%"], "difficulty": "easy", "disambiguation_criteria": ["cycles 0-20 are early-life baseline", "HEALTHY requires SOH above threshold", "no late-cycle evidence should be used"], "expected_failure_modes": ... | |
bess_health_006 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0018 | Explain the capacity trend of B0018 between cycles 100 and 130. Distinguish between sensor error and physical regeneration. | Battery 18 seems to rebound sometime after the first 100 cycles. Looking through the next 30 cycles or so, is this a sensor glitch we should worry about? | [
"fetch_cycle_data",
"anomaly_detector"
] | Physical phenomenon identification (Capacity Regeneration). | {"answer_type": "reasoning_explanation", "event_cycle": 120, "is_regeneration": true, "justification": "Capacity rose from 1.34Ah to 1.43Ah; consistent increase in discharge duration confirms physical effect, not sensor noise.", "source": "ground_truth.json:B0018:cycle_labels[120], anomalies"} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["Identify jump at c120", "Check consistency across multiple features (voltage, duration)"], "difficulty": "hard", "disambiguation_criteria": ["event_cycle is 120", "capacity and duration both rise around the event",... | Ground truth accepts only the c120 rebound; a larger rebound at c105 inside the asked window is omitted. |
bess_health_007 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005_B0007 | Calculate the average degradation rate (Ah/cycle) for B0005 and B0007 from cycle 0 to 100. Which one is degrading faster? | Over their first 100 cycles, which one is aging faster, Battery 5 or Battery 7? | [
"capacity_soh_calculator",
"fetch_cycle_summary"
] | Cross-battery comparative analysis. | {"B0005_rate": 0.0038, "B0007_rate": 0.0033, "answer_type": "comparative_numeric", "faster_degrading": "B0005", "source": "data/processed/B0005_cycles.json, B0007_cycles.json"} | {"cognitive_category": "Reasoning", "data_provision_mode": "data_discovery", "dependency_analysis": ["Calculate slope for both IDs", "B0007 as a long-life control case"], "difficulty": "medium", "disambiguation_criteria": ["compare absolute degradation-rate magnitudes", "same cycle window 0-100 for both batteries", "la... | |
bess_health_008 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0018 | Evaluate B0018 at cycle 100 against the 1.4 Ah EOL threshold. Determine: (a) which degradation stage (HEALTHY / EARLY / ACCELERATED / EOL) it falls into, (b) the current discharge capacity, and (c) the recommended action (continue / monitor / replace). Output structured: {stage, capacity_Ah, action}. | Battery 18 is around its 100th cycle now. Is it still safe to keep cycling it? | [
"capacity_soh_calculator"
] | EOL Detection and terminal decision. | {"action": "Immediate termination required. Battery has reached end-of-life.", "answer_type": "structured_categorical", "capacity": 1.385, "source": "ground_truth.json:B0018:cycle_labels[100]", "stage": "EOL"} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Check capacity at c100", "State change detection"], "difficulty": "hard", "disambiguation_criteria": ["capacity below 1.4 Ah implies EOL", "EOL action is replacement/termination", "cycle 100 is the evaluation poi... | |
bess_rul_001 | lithium_ion | RUL Prediction | Lithium-ion battery cell | NASA_PCoE_B0005 | Estimate the Remaining Useful Life (RUL) of battery B0005 starting from cycle 40 until it reaches its 1.4Ah EOL threshold. | Battery 5 has completed about 40 cycles. How much useful life does it have left from there? | [
"rul_predictor_ttm_finetuned",
"rul_predictor_ttm_zero_shot",
"rul_predictor_lstm"
] | Foundation-model RUL forecasting based on early-life degradation pattern. | {"answer_type": "numeric_cycles", "mae_threshold": 15, "source": "ground_truth.json:B0005:cycle_labels[40]", "true_rul": 84} | {"cognitive_category": "Prediction", "data_provision_mode": "data_discovery", "dependency_analysis": ["Provide cycle window [0, 40]", "Invoke RUL predictor", "Specify EOL threshold 1.4"], "difficulty": "medium", "disambiguation_criteria": ["forecast from context ending at cycle 40", "EOL threshold is 1.4 Ah", "predicti... | |
bess_rul_002 | lithium_ion | RUL Prediction | Lithium-ion battery cell | NASA_PCoE_B0006 | Estimate RUL for battery B0006 at cycle 80. The cell has shown accelerated degradation. Apply the most appropriate prognostic method given the rapid decay pattern, and report your model choice with the RUL estimate. | Battery 6 has been losing capacity quickly by around cycle 80. How much life does it have left at that point? | [
"rul_predictor_empirical",
"rul_predictor_ttm_finetuned"
] | Predictive analysis for fast-degrading cells. | {"answer_type": "numeric_cycles", "mae_threshold": 15, "source": "ground_truth.json:B0006:cycle_labels[80]", "true_rul": 28} | {"cognitive_category": "Prediction", "data_provision_mode": "data_discovery", "dependency_analysis": ["Recognize high degradation rate", "Use empirical decay as the primary fast-decay forecast", "Forecast until 1.4Ah crossing"], "difficulty": "hard", "disambiguation_criteria": ["fast decay should guide method selection... | |
bess_rul_003 | lithium_ion | RUL Prediction | Lithium-ion battery cell | NASA_PCoE_B0018 | Predict the RUL for battery B0018 at cycle 80 against the 1.4 Ah EOL threshold. The cell has shown irregular behavior in its history; choose the most appropriate forecasting method and report your reasoning. | Take a look at Battery 18 around cycle 80. Given the cycles observed so far, how many cycles does it still have in it? | [
"rul_predictor_chronos",
"rul_predictor_ttm_finetuned"
] | Prognostics in the presence of capacity regeneration. | {"answer_type": "numeric_cycles", "mae_threshold": 10, "source": "ground_truth.json:B0018:cycle_labels[80]", "true_rul": 16} | {"cognitive_category": "Prediction", "data_provision_mode": "data_discovery", "dependency_analysis": ["Forecast RUL for non-monotonic curve"], "difficulty": "medium", "disambiguation_criteria": ["forecast against 1.4 Ah EOL threshold", "method choice should account for irregular history", "MAE threshold is 10 cycles"],... | |
bess_rul_004 | lithium_ion | RUL Prediction | Lithium-ion battery cell | NASA_PCoE_Fleet | Estimate RUL for batteries B0005, B0006, B0007, and B0018 at cycle 80. Rank them from shortest to longest remaining life. | At around cycle 80 for our four cell fleet, which battery is going to fail first? Rank them from soonest to latest. | [
"rul_predictor_ttm_finetuned",
"rul_predictor_lstm"
] | Fleet-level comparative prognostics. | {"answer_type": "ordinal_list", "ranking": ["B0018", "B0006", "B0005", "B0007"], "ruls": {"B0005": 44, "B0006": 28, "B0007": "never_eol", "B0018": 16}, "source": "ground_truth.json:multiple"} | {"cognitive_category": "Reasoning", "data_provision_mode": "data_discovery", "dependency_analysis": ["Batch RUL estimation", "Ordinal ranking", "Handle B0007 non-EOL status"], "difficulty": "hard", "disambiguation_criteria": ["rank shortest remaining life first", "include all four batteries exactly once", "B0007 is cen... | |
bess_rul_005 | lithium_ion | RUL Prediction | Lithium-ion battery cell | NASA_PCoE_B0005 | Estimate RUL for B0005 at cycle 120 with a 95% confidence interval. Recommend immediate replacement vs deferral based on prediction certainty. | Battery 5 has reached about 120 cycles. Should we be pulling it out for replacement, or can it run a bit longer? | [
"rul_predictor_chronos",
"rul_predictor_empirical",
"rul_predictor_lstm"
] | Critical state decision under uncertainty. | {"answer_type": "numeric_cycles_with_interval", "mae_threshold": 5, "recommendation": "Replace immediately; RUL < 5 and uncertainty interval is tight.", "source": "ground_truth.json:B0005:cycle_labels[120]", "true_rul": 4} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Near-EOL RUL check", "Use Chronos as the primary short-horizon forecast", "Uncertainty quantification"], "difficulty": "medium", "disambiguation_criteria": ["near-EOL RUL is less than 5 cycles", "confidence inter... | |
bess_fault_001 | lithium_ion | Fault Classification | Lithium-ion battery cell | NASA_PCoE_B0005 | Classify the degradation stage for B0005 at each of these cycle markers: 0, 40, 80, 100, 120. Use the 4-stage taxonomy (HEALTHY / EARLY_DEGRADATION / ACCELERATED_DEGRADATION / EOL). Output a list of {cycle: stage} pairs. | Walk me through how Battery 5 degraded from the first cycle through about cycle 120. Check the first cycle, then around cycles 40, 80, 100, and 120. | [
"capacity_soh_calculator"
] | Temporal degradation stage mapping. | {"answer_type": "list_categorical", "source": "ground_truth.json:B0005", "stages": {"0": "HEALTHY", "100": "ACCELERATED_DEGRADATION", "120": "ACCELERATED_DEGRADATION", "40": "HEALTHY", "80": "EARLY_DEGRADATION"}} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["Multi-point stage classification"], "difficulty": "medium", "disambiguation_criteria": ["use canonical 4-stage taxonomy", "classify each requested cycle separately", "return cycle-stage pairs"], "expected_failure_m... | |
bess_fault_002 | lithium_ion | Fault Classification | Lithium-ion battery cell | NASA_PCoE_B0006 | Identify capacity and thermal anomalies in battery B0006 from cycle 0 to cycle 168. Use the anomaly_detector tool with parameters rolling_window=20, z_score_threshold=2.55, min_persistence=1. Report the total count of detected anomaly events. | Looking across the full run of Battery 6, from the first cycle through about cycle 168, are there any moments that stand out as abnormal compared to its general trend? | [
"anomaly_detector"
] | Statistical fault discovery. | {"anomaly_count": 26, "answer_type": "list_numeric", "detector_params": {"min_persistence": 1, "rolling_window": 20, "z_score_threshold": 2.55}, "example_cycles": [1, 2, 45, 68, 89], "source": "ground_truth.json:B0006:anomalies"} | {"cognitive_category": "Perception", "data_provision_mode": "data_discovery", "dependency_analysis": ["Unsupervised anomaly detection"], "difficulty": "medium", "disambiguation_criteria": ["use rolling_window=20", "use z_score_threshold=2.55", "min_persistence=1 and report total event count"], "expected_failure_modes":... | Only 1 of the 5 ground-truth example cycles is reproduced by the detector with the stated parameters. |
bess_fault_003 | lithium_ion | Fault Classification | Lithium-ion battery cell | NASA_PCoE_B0006 | B0006 shows a capacity jump of +0.152 Ah at cycle 89. Determine whether this is (a) capacity_regeneration_normal (a known lithium-ion phenomenon where capacity rebounds after rest), or (b) a hardware fault (sensor malfunction or cell defect). Disambiguation criteria: regeneration returns to the prior decay trend within... | Battery 6 had a sudden capacity jump around cycle 89. Is that a fault we should investigate, or is it just normal battery behavior? | [
"fetch_cycle_summary",
"anomaly_detector"
] | Physicochemical interpretation of abnormal trends. | {"answer_type": "reasoning_explanation", "classification": "capacity_regeneration_normal", "magnitude": 0.152, "reasoning": "A rapid capacity increase of 0.152 Ah followed by normal exponential decay is a textbook capacity regeneration event due to rest periods or chemistry relaxation, not a hardware fault.", "source":... | {"cognitive_category": "Reasoning", "data_provision_mode": "data_discovery", "dependency_analysis": ["Observe jump", "Check subsequent decay rate", "Identify as regeneration"], "difficulty": "hard", "disambiguation_criteria": ["jump magnitude is +0.152 Ah", "normal regeneration returns toward decay trend", "persistent ... | |
bess_fault_004 | lithium_ion | Fault Classification | Lithium-ion battery cell | NASA_PCoE_B0007 | Evaluate anomalies in B0007. Despite having 19 statistical anomalies, is this battery in the EOL stage? | Battery 7 is showing some thermal noise. Does that mean the cell is on its way out? | [
"anomaly_detector",
"capacity_soh_calculator"
] | Discriminative analysis of health vs. noise. | {"answer_type": "reasoning_explanation", "has_anomalies": true, "is_eol": false, "logic": "B0007 exhibits thermal noise and minor capacity fluctuations (19 anomalies), but its capacity remains consistently above 1.4Ah, thus it is NOT in the EOL stage.", "source": "ground_truth.json:B0007"} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["Distinguish signal noise from terminal health state"], "difficulty": "medium", "disambiguation_criteria": ["EOL depends on capacity threshold, not anomaly count", "statistical anomalies can coexist with non-EOL sta... | The premise '19 statistical anomalies' is not reproducible (no parameters given; defaults give 48). |
bess_cost_001 | lithium_ion | Cost-Benefit Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Battery B0005 at observation cycle 80 has a confirmed remaining useful life of 44 cycles, provided as ground truth. Use this given RUL only; do not re-predict it. Given replacement cost $450 and reactive failure cost $2800, calculate the cost-optimal replacement cycle. Report a target cycle range. | Battery 5 is around cycle 80, and we need to schedule replacement. When is the right time given where it is in its life? | [] | Economic optimization of maintenance scheduling. | {"answer_type": "numeric_optimization", "optimal_cycle_range": [115, 124], "reasoning": "RUL at c80 is 44, so EOL occurs at c124. Replacing at cycle 120 balances maximum utilization with safety margin.", "source": "ground_truth.json:B0005"} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Use provided RUL fact", "Formula calculation from maintenance_manual.md"], "difficulty": "medium", "disambiguation_criteria": ["given RUL=44 is authoritative", "EOL cycle = 80 + 44 = 124", "target replacement sho... | The 'cost-optimal' range is not derivable: no cost model is given. |
bess_cost_002 | lithium_ion | Cost-Benefit Analysis | Lithium-ion battery cell | NASA_PCoE_Fleet | For batteries B0005, B0006, B0007, B0018 at cycle 80: with a $1500 maintenance budget and $450 cost per replacement, rank batteries by replacement priority and report the remaining budget after allocation. Use RUL as the urgency signal. | At around cycle 80, our four cell fleet needs maintenance but the budget will not cover everything. Which ones should we prioritize? | [
"rul_predictor_ttm_finetuned",
"rul_predictor_lstm"
] | Fleet-level capital allocation. | {"answer_type": "list_categorical", "remaining_budget": 150, "source": "Fleet ranking at [0,80]", "swap_priority": ["B0018", "B0006", "B0005"]} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Batch RUL rank", "Budget constraint mapping"], "difficulty": "hard", "disambiguation_criteria": ["urgency follows shortest RUL first", "budget supports three replacements at $450 each", "remaining budget is $150"... | |
bess_safety_001 | lithium_ion | Safety/Policy Evaluation | Lithium-ion battery cell | NASA_PCoE_B0006 | Evaluate B0006 at cycle 150. Given its 58% SOH, does it meet the safety policy for continued high-power grid usage? | Battery 6 has reached about cycle 150. Does it still meet the IEC safety standard for continued use? | [
"capacity_soh_calculator"
] | Compliance auditing. | {"answer_type": "reasoning_explanation", "compliance": "fail", "reason": "SOH 58% is below the IEC 62133 high-risk threshold for grid BESS applications.", "source": "ground_truth.json:B0006"} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["SOH check", "Standard threshold comparison"], "difficulty": "medium", "disambiguation_criteria": ["compliance verdict is fail/non-compliant", "SOH below policy threshold drives decision", "grid high-power use is th... | Stated SOH 58% vs 63.23% in the data; IEC 62133 defines no grid-BESS SOH threshold. |
bess_safety_002 | lithium_ion | Safety/Policy Evaluation | Lithium-ion battery cell | NASA_PCoE_B0007 | Evaluate B0007's shipping eligibility under UN 38.3 aviation policy. Use B0007's earliest available reading (cycle 0) as the reference baseline state - UN 38.3 requires assessment of cells in their factory-fresh condition, not aged state. Apply thresholds: SOH >= 70%, no critical fault flags, max temperature <= 45 C. R... | We need to ship Battery 7 by air. Using its factory fresh first cycle condition, does it pass the standard aviation safety policy? | [
"capacity_soh_calculator",
"anomaly_detector"
] | Transportation safety compliance. | {"answer_type": "reasoning_explanation", "eligibility": "pass", "logic": "B0007 is healthy (>80% SOH) and has no structural or thermal runway anomalies, meeting UN 38.3 shipment safety requirements.", "source": "ground_truth.json:B0007"} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Health check to ensure 'non-damaged' status"], "difficulty": "medium", "disambiguation_criteria": ["use cycle-0 baseline state", "SOH >= 70 and no critical faults pass", "UN 38.3 shipping is distinct from aged op... | SOH/temperature limits are attributed to UN 38.3, which defines type tests, not these thresholds (the verdict is correct under the stated limits). |
bess_safety_003 | lithium_ion | Safety/Policy Evaluation | Lithium-ion battery cell | NASA_PCoE_Fleet | Summarize the safety risk of the 4-battery fleet at cycle 80. Which battery poses the highest thermal runaway risk? | At around cycle 80, pull together a safety read on our four cell fleet. | [
"generate_health_report"
] | Policy drafting and risk communication. | {"answer_type": "reasoning_explanation", "highest_risk_cell": "B0018", "justification": "B0018 has the lowest RUL (16) and shortest discharge duration, suggesting highest internal resistance and heat generation potential.", "source": "Fleet aggregate RUL"} | {"cognitive_category": "Decision-Making", "data_provision_mode": "data_discovery", "dependency_analysis": ["Aggregation of all diagnostic signals"], "difficulty": "hard", "disambiguation_criteria": ["highest-risk cell must be B0018", "reasoning should cite RUL, discharge duration, or resistance/heat", "fleet answer mus... | The justification ('highest heat generation') conflicts with B0018 having the lowest maximum temperature at c80. |
bess_health_009 | lithium_ion | Health Analysis | Lithium-ion battery cell | NASA_PCoE_B0005 | Retrieve battery B0005's discharge capacity at cycle 0 and report its initial state of health (SOH) percentage using the benchmark rated capacity 1.86 Ah. | At the first recorded cycle of Battery 5, what was its capacity? | [
"fetch_cycle_summary",
"capacity_soh_calculator"
] | Trivial baseline retrieval to establish a healthy starting point. | {"answer_type": "numeric", "initial_capacity": 1.856, "initial_soh_pct": 99.8, "source": "data/processed/B0005_cycles.json, data/labels/ground_truth.json", "stage": "HEALTHY"} | {"cognitive_category": "Understanding", "data_provision_mode": "data_discovery", "dependency_analysis": ["Fetch cycle 0 capacity", "Compute SOH with the benchmark rated capacity"], "difficulty": "easy", "disambiguation_criteria": ["SOH = capacity / rated_capacity * 100", "B0005 benchmark rated capacity is 1.86 Ah", "cy... | |
bess_fault_005 | lithium_ion | Fault Classification | Lithium-ion battery cell | NASA_PCoE_B0005 | Run anomaly_detector on B0005 cycles 0-5 with parameters rolling_window=10, z_score_threshold=3.0, min_persistence=1. Report whether any anomalies are detected and the count. | In the first five cycles of Battery 5, did anything unusual show up? | [
"anomaly_detector"
] | Trivial baseline anomaly check on healthy cells. | {"anomaly_count": 0, "answer_type": "boolean_count", "has_anomalies": false, "source": "ground_truth.json:B0005:anomalies cycle 0-5"} | {"cognitive_category": "Perception", "data_provision_mode": "data_discovery", "dependency_analysis": ["Slice cycles 0-5", "Run anomaly_detector"], "difficulty": "easy", "disambiguation_criteria": ["B0005 is healthy in cycles 0-5", "z_score_threshold=3.0 gives zero events in the baseline slice", "has_anomalies must agre... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.