- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
ImpactFormer is trained to predict structured deformations during vehicle impacts. It successfully predicts displacement at requested mesh points and times across datasets with different vehicles, meshes, and crash settings. The authors compare it with CrashSolver as well as a classical reduced-order method.
Critical strengths
- The paper fixed its training and test splits, and repats teh CrashSolver runs to quantify variability. Keeping these choices consistent makes the comparison easier to interpret. The authors also compare several ways to predict time using the same core model, which helps us understand the characteristics of the model itself.
- The authors also openly report results that dont necessarily favor their method - a classical ROM does better in some cases! These results help define where ImpactFormer may be useful and where a simpler or vehicle-specific approach may be safer to rely on.
Critical weaknesses
- The tests do not show that the model works on a new vehicle without retraining. There are only a few vehicles and the Yaris appears to be overrepresented in the available data. While impressive, results across five datasets do not amount to five independent tests on new vehicles.
- Average error does not necessarily show whether the model preserves things like abin intrusion, peak deceleration, absorbed energy, contact timing, or material failure. A small average can still hide a large error at a location or moment that changes a design decision. Reporting other metrics explicitly would help interpret the utility of the tool.
Questions for authors
- If the model is trained on two vehicles and tested on a third that it hasn't seen, how accurate is it?
- What does ImpactFormer add for design decisions beyond lower displacement error in simulations?
2 comments
As the author–reviewer discussion deadline approaches, we would appreciate knowing whether our rebuttal has addressed your concerns, whether any further clarification is needed, and, if your concerns have been resolved, whether you would consider revising your score. Thanks.
Response to Reviewer U1XJ
Thank you for your review.
Q1. Training on two vehicles and testing on a third
The three Yaris datasets. We agree that five datasets are not five independent tests on new vehicles; there are three base vehicles.
We respectfully disagree, however, that sharing the Yaris makes these datasets redundant. Nonlinear crash response depends on 1) geometry, 2) initial and boundary conditions, and 3) material properties, and the three Yaris studies vary different parts of that problem:
They are complementary prediction problems that happen to share a base vehicle.
Training on two vehicles, testing on the third. To answer your question directly, we now hold out each base vehicle in turn and pretrain on the other two. When Yaris is the target, all three Yaris-based datasets are removed together. We then adapt with a few simulations of the new vehicle, either by fine-tuning the pretrained model or by training the same network from scratch on the same runs, with the same budget. Test RMSE in mm, three seeds:
Three things stand out:
The Silverado values at 4 and 16 simulations come from the longer budget of the submitted fine-tuning experiment (about three times the steps of the short adaptation run); with the short budget, fine-tuning gives 26.4 mm and 16.2 mm. We will label both budgets clearly in the paper.
Q2. What does ImpactFormer add for design decisions beyond lower displacement error?
Yes we agree that an average can hide errors where they matter. We added the two quantities engineers use first when comparing frontal-crash designs, computed from the predicted and the simulated fields on every test run:
Maximum crush is predicted within 1.3-5.4 mm, below 1% of the crush depth on every dataset. Toe-pan intrusion is within a few millimeters across ranges of up to 80 mm.
Peak deceleration, energy, contact and failure. Our outputs are displacement fields exported every 5-10 ms.
How the model supports design decisions: