<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/jmulti/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/jmulti/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 18 Jan 2007 22:57:41 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jmulti/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Forecast Deterministics in Wrong Order</title><link>https://sourceforge.net/p/jmulti/bugs/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The forecast deterministics matrix in the Specify Forecast feature of the VECM Analysis is not arranged in the same order as the corresponding parameter matrix.  For example, in a model with a constant, trend and monthly dummies you have the following orders:&lt;/p&gt;
&lt;p&gt;forecast deterministics matrix&lt;br /&gt;
constant, monthly dummies, and trend&lt;/p&gt;
&lt;p&gt;parameter matrix&lt;br /&gt;
monthly dummies, constant, trend&lt;/p&gt;
&lt;p&gt;This causes incorrect forecasts.  I have only verified this problem in the VECM Analysis for the example listed above.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David W Carter</dc:creator><pubDate>Thu, 18 Jan 2007 22:57:41 -0000</pubDate><guid>https://sourceforge.netb82cd7564038975a167e2c5404bc3e3ccf430b9b</guid></item><item><title>VECM Chow test </title><link>https://sourceforge.net/p/jmulti/bugs/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;problem with VECM chow test&lt;/p&gt;
&lt;p&gt;fix is coming soon&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 29 Jul 2005 11:34:53 -0000</pubDate><guid>https://sourceforge.net0f38f306910fd75bcc3b5e545d3dcd982737a0aa</guid></item><item><title>Recursive estimation VAR/VEC</title><link>https://sourceforge.net/p/jmulti/bugs/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;sometimes the computation fails with a message &lt;br /&gt;
"not all singular values could be computed"&lt;/p&gt;
&lt;p&gt;will be gone in next release &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Wed, 13 Jul 2005 09:23:25 -0000</pubDate><guid>https://sourceforge.netc877ead7fde239118ca932c39072c57a6b010647</guid></item><item><title>System SER VECM </title><link>https://sourceforge.net/p/jmulti/bugs/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;subset search with the System SER for VECM models &lt;br /&gt;
does not work. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Wed, 06 Jul 2005 10:00:06 -0000</pubDate><guid>https://sourceforge.net8510d1d668ff52c1aa7ae14d71f3c9cba52ac21d</guid></item><item><title>Help Section Johansen Trace Test</title><link>https://sourceforge.net/p/jmulti/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;in section "Eviews Compatibility Guide"&lt;/p&gt;
&lt;p&gt;case 2 and case 3 are mixed up, but the description&lt;br /&gt;
makes it clear&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Thu, 02 Jun 2005 11:28:54 -0000</pubDate><guid>https://sourceforge.net9f042667349d9014dd294cb920fc794e5e315c35</guid></item><item><title>Graphics Settings in Impulse Responses</title><link>https://sourceforge.net/p/jmulti/bugs/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;dialog does not always result in expected settings&lt;br /&gt;
changes, &lt;br /&gt;
defaults are not properly set back for all settings&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Fri, 27 May 2005 18:14:55 -0000</pubDate><guid>https://sourceforge.net9da7f4711be5304513aba5464487f6b67982b15d</guid></item><item><title>Freeze at program startup</title><link>https://sourceforge.net/p/jmulti/bugs/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;JMulTi seems to freeze on some configurations at &lt;br /&gt;
startup without giving any error message. Only the&lt;br /&gt;
splashscreen is visible. This looks like a deadlock. So&lt;br /&gt;
far not reprocucible on &lt;br /&gt;
developer machine, but possible sources are being&lt;br /&gt;
explored. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Mon, 16 May 2005 17:36:44 -0000</pubDate><guid>https://sourceforge.net012ac517d85e479e39c57dcd0eccc909d0847ed6</guid></item><item><title>Trend breaks in cointegration tests</title><link>https://sourceforge.net/p/jmulti/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Trend breaks are not treated correctly in both&lt;br /&gt;
cointegration tests:&lt;/p&gt;
&lt;p&gt;S&amp;amp;L gives an error&lt;/p&gt;
&lt;p&gt;Joh. Trace statistic is ok, but response surface is not&lt;br /&gt;
computed although it would be possible&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Markus Kraetzig</dc:creator><pubDate>Mon, 09 May 2005 15:16:54 -0000</pubDate><guid>https://sourceforge.net2bd9e54e60d0ac3b06c0a0652ebe32247c7787f3</guid></item></channel></rss>