HeaRTDroid

HeaRTDroid is a rule-based inference engine both for Android mobile devices, and desktop solutions

User Tools

Site Tools


pub:software:heartdroid:tutorials:uncertainty_cf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

pub:software:heartdroid:tutorials:uncertainty_cf [2017/01/04 13:35]
admin [Use case]
pub:software:heartdroid:tutorials:uncertainty_cf [2019/04/10 08:54]
Line 1: Line 1:
-====== Managing uncertainty with Certainty Factors Algebra ====== 
-This tutorial focuses on the practical aspect of using he CF algebra to model uncertainty in XTT2 models. 
-The detailed information on the theory that stays behind the uncertainty handling mechanism in HeaRTDroid, can be found in //Bobek S., Nalepa G. (2016). [[http://​dx.doi.org/​10.1016/​j.pmcj.2016.09.004|Uncertainty handling in rule-based mobile context-aware systems]], Pervasive and Mobile Computing//​. 
- 
- 
-This tutorial is an continuation of the following tutorials: 
-  * [[pub:​software:​heartdroid:​tutorials:​hmr_quickstart|HMR language quickstart]] ​   
-  * [[pub:​software:​heartdroid:​tutorials:​callbacks|Callbacks and actions]] 
-  * [[pub:​software:​heartdroid:​tutorials:​tbo|Time-based operators]] ​ 
-If you did not read them, please go through them quickly to get a glimpse on the context of the use case. 
- 
-===== Use case ===== 
- 
-In [[pub:​software:​heartdroid:​tutorials:​tbo|Time-based operators]] tutorial we added time-parametrized operators to our //urban helper// application,​ to decide weather the car was just parked, or has been parked earlier, or maybe has just started. 
-The user activity that we can obtain from the [[http://​www.awareframework.com/​plugin/?​package=com.aware.plugin.google.activity_recognition|activity recognition sensor]] allows us only to recognize the case when the user is ''​in_vehicle''​. 
-However, ''​in_vehicle''​ could mean: in a car, in a taxi, in a bus, etc. 
-Furthermore,​ the data that comes from the sensor is inherently uncertain -- alongside with every reading we get an information about its confidence, which hardly is 100%. 
- 
-Therefore, we need to have a tool that will allow us to model and potentially decrease somehow this kind of uncertainty. 
-This is where the Certainty Factors algebra come in handy. 
-If you are not familiar with the CF algebra, see [[.:​uncertainty_cf#​certainty_factors_algebra_axioms| Certainty Factors Axioms]] section. 
- 
-The model that (partially) solves the problem given above is presented in the following figure. 
-The complete model with test scripts and basic callbacks can be downloaded from {{:​pub:​software:​heartdroid:​tutorials:​parking-zones-cf.zip|here}}. 
- 
-{{:​pub:​software:​heartdroid:​tutorials:​parking-zones-cf.png|}} 
- 
-To run the example, you will need the latest version of [[pub:​software:​heartdroid:​tutorials:​haquna|HaQuNa]]:​ 
- 
-<​code>​ 
-javac -cp haquna.jar:​. *.java 
-java -cp haquna.jar:​. haquna.HaqunaMain --console test-script-cf.hqn 
-</​code>​ 
- 
-The certainty factors (CF) in XTT2 models can be assigned to the attributes'​ values, to rules conditions, and to the rules directly. ​ 
-You can see, that for instance table ''​transportationModeA''​ has rules which CF are lower than 1. 
-It means that the rules themselves are not completely certain ​ and the resulting confidence of the conclusion they produce is not certain as well. 
-Its certainty is calculated as a product of a minimal CF of the conditions and the confidence of the rule. 
-For example if the value of ''​recent_activity''​ was ''​in_vehicle'',​ but the confidence of this activity was 0.3, and the number of nearby devices was 3 with confidence 1.0, than the overall confidence of the conclusion of the first rule would be ''​min(0.3,​1.0)*0.6=0.18''​. 
-The same confidence would be calculated for the last rule, and both rules will be fired. 
-As a result, two ambiguous values of the attribute will be stored in the memory: 
-<​code>​ 
-transportation_mode = car#0.18 
-transportation_mode = taxi#0.18 
-</​code>​ 
- 
-However, there is another table that produces values for ''​transportation_mode''​ attribute -- the ''​transportationModeB''​ table. 
-This table sets the value of the ''​transportation_mode''​ attribute based on the analysis of mobile phone [[http://​www.awareframework.com/​screen/​|screen activity]]. If the user plays with the phone, it could mean that he or the is not driving a car. 
-Let us assume that only the last rule from this table is true. 
-According to disjunctive formula, the confidence of the ''​transportation_mode set car''​ will be ''​min(0.3,​1.0)*0.9=0.27''​ 
- 
-Now, we have following values in the working memory: 
-<​code>​ 
-transportation_mode = car#0.18 
-transportation_mode = car#0.27 
-transportation_mode = taxi#0.18 
-</​code>​ 
- 
-''​transportationModeB''​ was the last table that produces the value for ''​transportation_mode''​ (actually there is another one, but is is empty), hence the disambiguation process for these three values can begin. 
-This values are treated as cumulative values (i.e. they strengthen or weaken their confidence) and are evaluated according to cumulative formula from CF algebra presented in the last equation in the [[pub:​software:​heartdroid:​tutorials:​uncertainty_cf##​certainty_factors_algebra_axioms|CF axioms]] section: 
-''​0.18+0.27-0.18*0.27=0.4014''​. 
- 
-After running the example script given at the beginning of the section you should see the output presented below. 
-Note, that the certainty factors of transportation mode is exactly the same as we calculated. 
- 
- 
-<​code>​ 
-Attribute: daytype ​ = workday ​ cf = 1.0 
-Attribute: recent_activity ​ = in_vehicle ​ cf = 0.3 
-Attribute: vehicle_action ​ = in_motion ​ cf = 0.21599999 
-Attribute: past_activity ​ = in_vehicle ​ cf = 0.26999998 
-Attribute: notification ​ = null  cf = 1.0 
-Attribute: application_foreground ​ = null  cf = 1.0 
-Attribute: hour  = 13.0  cf = 1.0 
-Attribute: transportation_mode ​ = car  cf = 0.40140003 
-Attribute: screen_active ​ = false  cf = 1.0 
-Attribute: payment ​ = null  cf = 1.0 
-Attribute: location ​ = pay_zone ​ cf = 1.0 
-Attribute: tariff ​ = pay  cf = 1.0 
-Attribute: day  = tue/2  cf = 1.0 
-Attribute: bluetooth_count ​ = 3.0  cf = 1.0 
-</​code>​ 
- 
-Set the value of the ''​recent_activity''​ to ''​on_foot'':​ 
-<​code>​ 
-wm.setValueOf('​recent_activity','​on_foot'​) 
-</​code>​ 
-Wait for a minute (literally, as this is what was set in the formula) and run the inference again twice (to force that the ''​on_foot''​ will appear more than 80% during last minute): 
-<​code>​ 
-model.run(wm,​inference=gdi,​tables=['​parkingReminder'​]) 
-wm.showCurrentState() 
-</​code>​ 
-You should now see that the ''​vehicle_action''​ changed from ''​in_motion''​ to ''​start_parking''​ and the value of the ''​notification''​ attribute was set appropriately to your time and day of a week. The sample output may look as follows: 
- 
-<​code>​ 
-Attribute: daytype ​ = workday ​ cf = 1.0 
-Attribute: recent_activity ​ = on_foot ​ cf = 1.0 
-Attribute: vehicle_action ​ = start_parking ​ cf = 0.24299997 
-Attribute: past_activity ​ = in_vehicle ​ cf = 0.26999998 
-Attribute: notification ​ = start_parking_fee ​ cf = 0.24299997 
-Attribute: application_foreground ​ = null  cf = 1.0 
-Attribute: hour  = 13.0  cf = 1.0 
-Attribute: transportation_mode ​ = car  cf = 0.40140003 
-Attribute: screen_active ​ = false  cf = 1.0 
-Attribute: payment ​ = null  cf = 1.0 
-Attribute: location ​ = pay_zone ​ cf = 1.0 
-Attribute: tariff ​ = pay  cf = 1.0 
-Attribute: day  = tue/2  cf = 1.0 
-Attribute: bluetooth_count ​ = 3.0  cf = 1.0 
-</​code>​ 
- 
-Note, that the ''​notification''​ attribute was also set with lower certainty (the certainty equal to the minimal certainty of the conditional part times the confidence of the rule). 
- 
-===== Certainty factors algebra axioms ===== 
- 
-Rule in CF algebra is represented according to formula: 
-\begin{equation*} 
-\mathit{condition}_1 \wedge \mathit{condition}_2 \wedge \ldots \wedge \mathit{condition}_k \rightarrow \mathit{conclusion} 
-\label{eq:​rule} 
-\end{equation*} 
-Each of the elements of the formulae from equation~(\ref{eq:​rule}) can have assigned a certainty factor 
-$\mathit{cf}(element) \in [-1; 1]$ where $1$ means that the element is absolutely true; $0$ denotes element about which nothing can be said with any degree of certainty; $-1$ denotes an element, which is absolutely false. 
-The CF of the conditional part of a rule is determined by the formulae: 
-$$\mathit{cf}(\mathit{condition}_1 \wedge \ldots \wedge \mathit{condition}_k) = \min_{i \in 1 \ldots k}{\mathit{cf}(\mathit{condition}_i)}$$ 
-The CF of conclusion $C$ of a single \textit{i-th} rule is calculated according to a formula: 
-\begin{equation*} 
-\mathit{cf}_{i}(C) = \mathit{cf}(\mathit{condition}_1 \wedge \ldots \wedge \mathit{condition}_k) * \mathit{cf}(rule) 
-\label{eq:​cf-rule} 
-\end{equation*} 
- 
-The $\mathit{cf}(rule)$ defines a certainty of a rule which is a measure of the extent, to which the rule is considered to be true. It is instantiated by the rule designer, or it comes from a machine learning algorithm (like for instance an association rule mining algorithms). 
- 
-There are two types of rules: **disjunctive** and **cumulative**. 
- 
-Disjunctive rules have the same conclusions but are conditionally dependent (i.e. value of any of the conditions determine values of other rules conditions). ​ 
- 
-The equation for calculating certainty factor of a disjunctive rule is presented in the following equation: \begin{equation*} 
-\mathit{cf}(C) = \max_{i \in 1 \ldots k}{\left \{ \mathit{cf}_i(C) \right \} }  ​ 
-\label{eq:​disjunctive} 
-\end{equation*} 
- 
-Cumulative rules have the same conclusions and have independent conditions (i.e. value of any of the conditions does not determine values of other rules conditions). The formula for calculating the certainty factor of the combination of two cumulative rules is given in the equation below. 
- 
-\begin{equation*} 
-\mathit{cf}(C) = \begin{cases} 
-\mathit{cf}_{i}(C)+ \mathit{cf}_{j}(C) - \mathit{cf}_{i}(C)*\mathit{cf}_{j}(C) & \text{ if } \mathit{cf}_{i}(C) \ge 0,​\mathit{cf}_{j}(C) \ge 0  \\  ​ 
-\mathit{cf}_{i}(C)+ \mathit{cf}_{j}(C) + \mathit{cf}_{i}(C)*\mathit{cf}_{j}(C) & \text{ if } \mathit{cf}_{i}(C) \le 0,​\mathit{cf}_{j}(C) \le 0  \\  ​ 
-\frac{\mathit{cf}_{i}(C) + \mathit{cf}_{j}(C))}{1- \min { \left \{ |\mathit{cf}_{i}(C)|,​ |\mathit{cf}_{j}(C)| \right \} }} & \text{ if } 
-\mathit{cf}_{i}(C)\mathit{cf}_{j}(C) \not \in \left \{ -1,0 \right \}  
-\end{cases} 
-\label{eq:​cumulative} 
-\end{equation*} 
- 
- 
- 
- 
-===== Disjunctive rules ===== 
-Disjunctive rules are the rules that have independent condition list. 
- 
-The XTT2 convention suggest putting all of these rules within a single table. 
-The example of disjunctive rules are presented for example in table ''​transportationModeA''​. 
-If there are several rules that produce the same conclusion (e.g. they set the value of transportation mode to ''​car'',​ only the most certain rules are selected for execution. 
- 
-This applies to all different values that are set by the rules. 
-It means that in case of ''​recent activity eq in_vehicle''​ and ''​bluetooth_count lte 4''​ are true, two last rules from the ''​transportationModeA''​ table will be executed, and the value of the ''​transportation_mode''​ attribute will be ambiguous, until all the tables that produce the value of ''​transportation_mode''​ are executed. 
- 
-In case when there are only this two equally uncertain values in the memory, always the last value is chosen as the one that stays in the memory **despite the conflict set resolution mechanism chosen for the inference**. 
- 
- 
-===== Cumulative rules ===== 
-Cumulative rules are rules that have the same attributes in decision parts and can be executed simultaneously in one reasoning cycle. 
-The final conclusion is calculated according to the equation given in [[.:​uncertainty_cf#​certainty_factors_algebra_axioms|Certainty factors axioms]] section. 
- 
-By XTT2 convention, the cumulative rules should be located in separate tables. 
-However, if you choose fire all conflict resolution mechanism rules within a single table will also be treated as cumulative. 
- 
-This mechanism is useful in strengthening or weakening conclusions that may depend on many different attributes, not related to each other. 
- 
- 
  
pub/software/heartdroid/tutorials/uncertainty_cf.txt ยท Last modified: 2019/04/10 08:54 (external edit)