HeaRTDroid

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

User Tools

Site Tools


pub:software:heartdroid:tutorials:inference_config

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pub:software:heartdroid:tutorials:inference_config [2017/01/17 10:19]
admin [Reasoning with Java API]
pub:software:heartdroid:tutorials:inference_config [2019/04/10 08:54] (current)
Line 30: Line 30:
   - **Data-Driven (DDI)**, which can be used to find all possible information that can be inferred from given data. This mode is similar to forward chaining inference. In this mode, the system needs to pass to HeaRTDroid only the //​starting//​ tables, and the engine will crawl the XTT2 network to search for tables that are successors of the initial tables, until no further tables could be found.   - **Data-Driven (DDI)**, which can be used to find all possible information that can be inferred from given data. This mode is similar to forward chaining inference. In this mode, the system needs to pass to HeaRTDroid only the //​starting//​ tables, and the engine will crawl the XTT2 network to search for tables that are successors of the initial tables, until no further tables could be found.
   - **Goal-Driven (GDI)**, which can be used to find only a specific information that can be inferred from a specific subset of XTT2 tables. This mode is similar to backward chaining inference. This mode is kind of opposite to DDI mode. The system needs to pass to HeaRTDroid the table(s) that produce(s) desired conclusions,​ and the engine crawls backward to find all the tables that are needed to derive the conclusion.   - **Goal-Driven (GDI)**, which can be used to find only a specific information that can be inferred from a specific subset of XTT2 tables. This mode is similar to backward chaining inference. This mode is kind of opposite to DDI mode. The system needs to pass to HeaRTDroid the table(s) that produce(s) desired conclusions,​ and the engine crawls backward to find all the tables that are needed to derive the conclusion.
 +
 +In the following Figure DDI and GDI inference modes were presented (FOI was skipped, being trivial).
 +In the Figure, every mode can be //​tokenized//,​ meaning that only tables with sufficient number of tokens can be processed. **This feature is not yet released in stable version**.
 +
 +{{:​pub:​software:​heartdroid:​tutorials:​inference-modes.png|}}
  
 The following paragraphs gives more intuition on when each of these modes is useful. The following paragraphs gives more intuition on when each of these modes is useful.
pub/software/heartdroid/tutorials/inference_config.txt ยท Last modified: 2019/04/10 08:54 (external edit)