85 | | <p> |
86 | | On-line estimation is implemented by method <div class="fragment"><pre class="fragment"> <span class="keywordtype">void</span> bayes(vec dt) |
87 | | </pre></div> Off-line estimation is implemented by method <div class="fragment"><pre class="fragment"> <span class="keywordtype">void</span> bayesB(mat D) |
88 | | </pre></div><p> |
89 | | As an intermediate product, the bayes rule computes marginal likelihood of the data records <img class="formulaInl" alt="$ f(D) $" src="form_103.png">. Numerical value of this quantity which is important e.g. for model selection can be obtained by calling method <code>_ll()</code>.<h2><a class="anchor" name="epdf"> |
| 92 | <p>On-line estimation is implemented by method </p> |
| 93 | <div class="fragment"><pre class="fragment"> <span class="keywordtype">void</span> bayes(vec dt) |
| 94 | </pre></div><p> Off-line estimation is implemented by method </p> |
| 95 | <div class="fragment"><pre class="fragment"> <span class="keywordtype">void</span> bayesB(mat D) |
| 96 | </pre></div><p>As an intermediate product, the bayes rule computes marginal likelihood of the data records <img class="formulaInl" alt="$ f(D) $" src="form_103.png"/>. Numerical value of this quantity which is important e.g. for model selection can be obtained by calling method <code>_ll()</code>.</p> |
| 97 | <h2><a class="anchor" id="epdf"> |
100 | | As introduced above, the results of parameter estimation are in the form of probability density function conditioned on numerical values. This type of information is represented by class <code>epdf</code>.<p> |
101 | | This class allows such as moment evaluation via methods <code>mean()</code> and <code>variance()</code>, marginalization via method <code>marginal()</code>, and conditioning via method <code>condition()</code>.<p> |
102 | | Also, it allows generation of a sample via <code>sample()</code> and evaluation of one value of the posterior parameter likelihood via <code>evallog()</code>. Multivariate versions of these operations are also available by adding suffix <code>_m</code>, i.e. <code>sample_m()</code> and <code>evallog_m()</code>. These methods providen multiple samples and evaluation of likelihood in multiple points respectively.<h2><a class="anchor" name="pc"> |
| 110 | <p>As introduced above, the results of parameter estimation are in the form of probability density function conditioned on numerical values. This type of information is represented by class <code>epdf</code>.</p> |
| 111 | <p>This class allows such as moment evaluation via methods <code>mean()</code> and <code>variance()</code>, marginalization via method <code>marginal()</code>, and conditioning via method <code>condition()</code>.</p> |
| 112 | <p>Also, it allows generation of a sample via <code>sample()</code> and evaluation of one value of the posterior parameter likelihood via <code>evallog()</code>. Multivariate versions of these operations are also available by adding suffix <code>_m</code>, i.e. <code>sample_m()</code> and <code>evallog_m()</code>. These methods providen multiple samples and evaluation of likelihood in multiple points respectively.</p> |
| 113 | <h2><a class="anchor" id="pc"> |
110 | | 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> |
111 | | 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"> |
112 | | <img class="formulaDsp" alt="\[ f(a,b,c) = f(a|b,c) f(b) f(c) \]" src="form_104.png"> |
113 | | <p> |
114 | | In our setup, <img class="formulaInl" alt="$ f(a|b,c) $" src="form_105.png"> is represented by an <code>mpdf</code> while <img class="formulaInl" alt="$ f(b) $" src="form_106.png"> and <img class="formulaInl" alt="$ f(c) $" src="form_107.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> |
115 | | 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> |
116 | | <hr size="1"><address style="text-align: right;"><small>Generated on Sat Aug 29 20:49:42 2009 for mixpp by |
| 122 | <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> |
| 123 | <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> |
| 124 | <p class="formulaDsp"> |
| 125 | <img class="formulaDsp" alt="\[ f(a,b,c) = f(a|b,c) f(b) f(c) \]" src="form_104.png"/> |
| 126 | </p> |
| 127 | <p> In our setup, <img class="formulaInl" alt="$ f(a|b,c) $" src="form_105.png"/> is represented by an <code>mpdf</code> while <img class="formulaInl" alt="$ f(b) $" src="form_106.png"/> and <img class="formulaInl" alt="$ f(c) $" src="form_107.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> |
| 128 | <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>. </p> |
| 129 | </div> |
| 130 | <hr size="1"/><address style="text-align: right;"><small>Generated on Sun Aug 30 22:10:49 2009 for mixpp by |