You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***Known caveats to report honestly:** The accuracy gap is currently backwards and practically noise due to a 99.5% inconclusive rate. This is pending a strict `tau` threshold calibration sweep for gear physics, as well as confirming that GMF strength aligns with the same numerical scale as bearing physics.
**Objective**: Eliminate data leakage by explicitly testing the model's ability to generalize across changing physical operating conditions (Domain Shift). The CNN is trained exclusively on 900 RPM data and tested exclusively on 1500 RPM data.
247
-
**Physics Config**: D=28.5mm, d=6.75mm, N=8, f_s=64kHz. `tau` calibrated to 2.5 on the 1500 RPM calibration split.
This experiment perfectly proves the necessity of the causal physics engine. Because the baseline CNN was trained only on 900 RPM data, its pattern matching failed catastrophically when tested on 1500 RPM data (Baseline Accuracy crashed to 64.8%). However, the Physics Engine mathematically adjusts for RPM dynamically. It successfully caught the CNN's failures, flagging over 1,700 predictions as CONFLICTS, while isolating 2,340 verified predictions that maintained a 93.3% accuracy. The massive Accuracy Gap of **+38.9%** undeniably proves that the physics engine acts as a robust, domain-aware verification layer for unreliable neural networks.
260
+
Because the baseline CNN was trained only on 900 RPM data, its pattern matching degraded when tested on 1500 RPM data (Baseline Accuracy crashed to 70.4%). The Physics Engine dynamically adjusts for RPM and isolates reliable predictions. As shown above, the gap remains strongly positive across all thresholds, peaking at +0.421.
261
+
262
+
**Known Limitations**:
263
+
-**High Inconclusive Rate**: At the optimally calibrated threshold (`tau=2.5`), the engine flags ~46% of predictions as INCONCLUSIVE. This is a known trade-off of the strict verification process.
264
+
-**Scope**: Demonstrated strong robustness on the PU speed-shift task (single dataset, single seed).
0 commit comments