This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
sql-derivative-sensitivity-analyser [2019/05/31 17:54] alisa [Quick guide] |
sql-derivative-sensitivity-analyser [2019/05/31 17:56] alisa [Quick guide] |
||
---|---|---|---|
Line 111: | Line 111: | ||
Clicking on //Analyze// button opens a menu entitled //Analysis settings// on the right side of the page (in sidebar). There you can adjust "Privacy level ε" and "Smoothness level β" parameters. Simply put, smaller ε means more privacy. The variable β is an optimization parameter that does not affect privacy at all, but is related to the noise lever. In general, smaller β means less noise, but not all values of β will work for a particular query, resulting in an error. The user may choose not to fix β and let the analyzer find a suitable β itself (which depends on ε). The analysis takes more time, but the obtained β can be reused afterwards, and still be reasonable if the query or the data does not change too much. | Clicking on //Analyze// button opens a menu entitled //Analysis settings// on the right side of the page (in sidebar). There you can adjust "Privacy level ε" and "Smoothness level β" parameters. Simply put, smaller ε means more privacy. The variable β is an optimization parameter that does not affect privacy at all, but is related to the noise lever. In general, smaller β means less noise, but not all values of β will work for a particular query, resulting in an error. The user may choose not to fix β and let the analyzer find a suitable β itself (which depends on ε). The analysis takes more time, but the obtained β can be reused afterwards, and still be reasonable if the query or the data does not change too much. | ||
- | Clicking on a sub-button "Attacker Settings" opens a window tab where the user can define known bounds on data, which may reduce the noise or even turn an infeasible result into feasible. | + | Clicking on a sub-button "Attacker Settings" opens a window tab where the user can define known bounds on data, which may reduce the noise or even turn an infeasible result into feasible. These settings are essential for GROUP BY queries, defining the total number of possible groups. |
<code> | <code> | ||
table_1.attr_1 range lower_bound upper_bound ; | table_1.attr_1 range lower_bound upper_bound ; | ||
... | ... | ||
- | table_n.attr_n range lower_bound upper_bound ; | + | table_n.attr_n set value_1 ... value_n ; |
</code> | </code> | ||