2019
DOI: 10.1145/3290352
|View full text |Cite
|
Sign up to set email alerts
|

Trace abstraction modulo probability

Abstract: We propose trace abstraction modulo probability, a proof technique for verifying high-probability accuracy guarantees of probabilistic programs. Our proofs overapproximate the set of program traces using failure automata, nite-state automata that upper bound the probability of failing to satisfy a target speci cation.We automate proof construction by reducing probabilistic reasoning to logical reasoning: we use program synthesis methods to select axioms for sampling instructions, and then apply Craig interpola… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
30
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 16 publications
(31 citation statements)
references
References 79 publications
0
30
0
Order By: Relevance
“…In contrast, our language allows for arbitrary loops and we provide a decision procedure for accuracy. Trace Abstraction Modulo Probability (TAMP) in Smith et al [2019], is an automated proof technique for accuracy of probabilistic programs. TAMP generalizes the trace abstraction technique of Heizmann et al [2009] to the probabilistic setting.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In contrast, our language allows for arbitrary loops and we provide a decision procedure for accuracy. Trace Abstraction Modulo Probability (TAMP) in Smith et al [2019], is an automated proof technique for accuracy of probabilistic programs. TAMP generalizes the trace abstraction technique of Heizmann et al [2009] to the probabilistic setting.…”
Section: Related Workmentioning
confidence: 99%
“…In some cases, the definition of accuracy is similar to the one used in the context of randomized algorithm design [Motwani and Raghavan 1995], where we require that the output of the differentially private algorithm be close to the true output (say within distance γ ) with high probability (say at least 1 − β). Such a notion of accuracy is similar to computing error bounds, and there has been work on formally verifying such a definition of accuracy on some examples [Barthe et al 2016b;Smith et al 2019;Vesga et al 2019]. Unfortunately, prior work on formal verification of accuracy suffers from two shortcomings:…”
Section: Introductionmentioning
confidence: 99%
“…In order to make these estimates as precise as possible, DPella uses taint analysis to track the use of noise to identify which variables are statistically independent. This information is used by DPella to soundly replace, when needed, the union bound with the Cherno bound, something that to the best of our knowl-edge other program logics or program analyses also focusing on accuracy, such as [8] and [54], do not consider. We envision DPella's accuracy estimations to be used in scenarios which align with those considered by tools like GUPT, PSI, and Apex.…”
Section: Contributionmentioning
confidence: 99%
“…We leave exploring this direction for future works. More recently, Smith et al [54] propose an automated approach for computing accuracy bounds of probabilistic imperative programs. This work shares some similarities with our.…”
Section: Formal Calculi For Dpmentioning
confidence: 99%
“…Most proofs are constructed by hand, and as such are tailored to the algorithm of interest. While there exist program logics for reasoning about accuracy [Barthe et al 2016], automations of said logics (i) are so slow as to dwarf the cost of synthesis (see ğ6), and (ii) themselves reduce to synthesis [Smith et al 2019]. Considering accuracy in addition to privacy therefore poses a significant challenge to program synthesis, which necessitates our use of the weak notion of deterministic satisfaction (ğ3) to ensure programs have some utility to an end user.…”
Section: Utility Of Synthesis Solutionsmentioning
confidence: 99%