Changeset 271 for doc/html/philosophy.html

Timestamp:

02/16/09 10:03:13 (16 years ago)

Author:

smidl

Message:

Next major revision

Files:

• doc/html/philosophy.html (modified) (3 diffs)

doc/html/philosophy.html

@@ -38 +38 @@
 The class BM is designed for both on-line and off-line estimation. We make the following assumptions about data: <ul>
 <li>
-an individual data record is stored in a vector, <code>vec</code> <code>dt</code>, </li>
+an individual data record is stored in a vector, <code>vec</code> <code>dt</code>,  </li>
 <li>
 a set of data records is stored in a matrix,<code>mat</code> <code>D</code>, where each column represent one individual data record  </li>
@@ -64 +64 @@
 <li>
 <code>mpdf</code> a pdf conditioned on another symbolic variable, </li>
+<li>
+<code>RV</code> a symbolic variable on which pdfs are defined. </li>
 </ul>
-<p>
-<code>RV</code> a symbolic variable on which pdfs are defined.  The former class is an extension of mpdf that allows conditioning on a symbolic variable. Hence, when numerical results - such as samples - are required, numericla values of the condition must be provided. The names of methods of the <code>epdf</code> are used extended by suffix <code>cond</code>, i.e. <code>samplecond()</code>, <code>evallogcond()</code>, where <code>cond</code> precedes matrix estension, i.e. <code>samplecond_m()</code> and <code>evallogcond_m()</code>.<p>
+The former class is an extension of mpdf that allows conditioning on a symbolic variable. Hence, when numerical results - such as samples - are required, numericla values of the condition must be provided. The names of methods of the <code>epdf</code> are used extended by suffix <code>cond</code>, i.e. <code>samplecond()</code>, <code>evallogcond()</code>, where <code>cond</code> precedes matrix estension, i.e. <code>samplecond_m()</code> and <code>evallogcond_m()</code>.<p>
 The latter class is used to identify how symbolic variables are to be combined together. For example, consider the task of composition of pdfs via the chain rule: <p class="formulaDsp">
 <img class="formulaDsp" alt="\[ f(a,b,c) = f(a|b,c) f(b) f(c) \]" src="form_89.png">
@@ -72 +73 @@
  In our setup, <img class="formulaInl" alt="$ f(a|b,c) $" src="form_90.png"> is represented by an <code>mpdf</code> while <img class="formulaInl" alt="$ f(b) $" src="form_91.png"> and <img class="formulaInl" alt="$ f(c) $" src="form_92.png"> by two <code>epdfs</code>. We need to distinguish the latter two from each other and to deside in which order they should be added to the mpdf. This distinction is facilitated by the class <code>RV</code> which uniquely identify a random varibale.<p>
 Therefore, each pdf keeps record on which RVs it represents; <code>epdf</code> needs to know only one <code>RV</code> stored in the attribute <code>rv</code>; <code>mpdf</code> needs to keep two <code>RVs</code>, one for variable on which it is defined (<code>rv</code>) and one for variable incondition which is stored in attribute <code>rvc</code>. </div>
-<hr size="1"><address style="text-align: right;"><small>Generated on Wed Feb 11 23:33:56 2009 for mixpp by&nbsp;
+<hr size="1"><address style="text-align: right;"><small>Generated on Sun Feb 15 21:06:01 2009 for mixpp by&nbsp;
 <a href="http://www.doxygen.org/index.html">
 <img src="doxygen.png" alt="doxygen" align="middle" border="0"></a> 1.5.6 </small></address>