REVIEW 2 cited by
Autoinverse: Uncertainty Aware Inversion of Neural Networks
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Neural networks are powerful surrogates for numerous forward processes. The inversion of such surrogates is extremely valuable in science and engineering. The most important property of a successful neural inverse method is the performance of its solutions when deployed in the real world, i.e., on the native forward process (and not only the learned surrogate). We propose Autoinverse, a highly automated approach for inverting neural network surrogates. Our main insight is to seek inverse solutions in the vicinity of reliable data which have been sampled form the forward process and used for training the surrogate model. Autoinverse finds such solutions by taking into account the predictive uncertainty of the surrogate and minimizing it during the inversion. Apart from high accuracy, Autoinverse enforces the feasibility of solutions, comes with embedded regularization, and is initialization free. We verify our proposed method through addressing a set of real-world problems in control, fabrication, and design.
Forward citations
Cited by 2 Pith papers
-
PTP: Previous-Token Prediction based LLM Inversion for Near-Exact Prompt Reconstruction
A from-scratch inverse language model trained on token-reversed synthetic LLM outputs reconstructs prompts from a single response, outperforming prior black-box methods on exact-token metrics.
-
Shortcut Learning Susceptibility in Vision Classifiers
CNNs showed the most resistance to position and intensity shortcuts, ViTs with positional encodings relied on shortcuts most, and lower learning rates reduced shortcut reliance.
Discussion (0). Continue with ORCID to comment.