sql-derivative-sensitivity-analyser_demo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
sql-derivative-sensitivity-analyser_demo [2019/06/01 15:46] alisa [Setting up tasks] |
sql-derivative-sensitivity-analyser_demo [2019/09/26 12:36] alisa [Running sensitivity analysis] |
||
|---|---|---|---|
| Line 85: | Line 85: | ||
| ==== Running sensitivity analysis ==== | ==== Running sensitivity analysis ==== | ||
| - | We are now ready to run the analysis. Click the blue button //Analyze//. Let us first set ε = 1 and β = 0.1. Click the green button //Run Analysis//. The most interesting value in the output that we see is the //relative error//. This can be interpreted as an upper bound on the relative distance of the noisy output from the actual output, which holds with probability 80%. There is unfortunately no strict upper bound on the additive noise, and it can potentially be infinite, though with negligible probability. Hence, we can only give a probabilistic upper bound on the noise, which is in our case hard-coded to 80%. | + | We are now ready to run the analysis. Click the blue button //Analyze//. Let us first set ε = 1 and β = 0.1, and set the slider "Confidence level of estimated noise" to 90%. Click the green button //Run Analysis//. The most interesting value in the output that we see is the //relative error//. This can be interpreted as an upper bound on the relative distance of the noisy output from the actual output, which holds with probability 90%. There is unfortunately no strict upper bound on the additive noise, and it can potentially be infinite, though with negligible probability. Hence, we can only give a probabilistic upper bound on the noise, which is in our case set to 90%. |
| We can now play around with the model and see how the error can be reduced. | We can now play around with the model and see how the error can be reduced. | ||
| Line 112: | Line 112: | ||
| If the attacker guesses the location precisely, this is bad. However, it can be bad even if he guesses the location precisely enough. Let us assume that we want to avoid guessing within 5 units of precision. We insert the following code into the window that opens after clicking //Sensitive attributes// button. | If the attacker guesses the location precisely, this is bad. However, it can be bad even if he guesses the location precisely enough. Let us assume that we want to avoid guessing within 5 units of precision. We insert the following code into the window that opens after clicking //Sensitive attributes// button. | ||
| <code> | <code> | ||
| - | leak | + | ship.latitude approx 5 AND |
| - | ship.latitude approx 5; | + | |
| ship.longitude approx 5; | ship.longitude approx 5; | ||
| - | cost | + | cost 100 |
| - | 100 | + | |
| </code> | </code> | ||
sql-derivative-sensitivity-analyser_demo.txt · Last modified: 2021/06/14 11:22 by alisa
Page Tools
