<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to par_n_iter</title><link>https://sourceforge.net/p/infos/wiki/par_n_iter/</link><description>Recent changes to par_n_iter</description><atom:link href="https://sourceforge.net/p/infos/wiki/par_n_iter/feed" rel="self"/><language>en</language><lastBuildDate>Thu, 08 Sep 2016 15:03:58 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/infos/wiki/par_n_iter/feed" rel="self" type="application/rss+xml"/><item><title>par_n_iter modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_n_iter/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -2,4 +2,5 @@
 After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to [‘par.add_peaks’](/p/infos/wiki/par_add_peaks)+1. As with [‘par.IterFact’](/p/infos/wiki/par_IterFact), increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.

 For ‘par.add_peaks=5’:
-par.n_iter=\[3 3 3 3 3 6\];
+
+    par.n_iter=[3 3 3 3 3 6];
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A. Smith</dc:creator><pubDate>Thu, 08 Sep 2016 15:03:58 -0000</pubDate><guid>https://sourceforge.net54cd5deaf2939cd98c1ddad6fabbbaa4ed3784fc</guid></item><item><title>par_n_iter modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_n_iter/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -1,5 +1,5 @@
 ###par.n_iter
-After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to [‘par.add_peaks’](/p/infos/wiki/par_add_peaks)+1. As with ‘par.IterFact’, increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.
+After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to [‘par.add_peaks’](/p/infos/wiki/par_add_peaks)+1. As with [‘par.IterFact’](/p/infos/wiki/par_IterFact), increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.

 For ‘par.add_peaks=5’:
 par.n_iter=\[3 3 3 3 3 6\];
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A. Smith</dc:creator><pubDate>Thu, 08 Sep 2016 14:51:34 -0000</pubDate><guid>https://sourceforge.net49954ad103e0aab7dd43819b6bae525abce309fa</guid></item><item><title>par_n_iter modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_n_iter/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,5 +1,5 @@
 ###par.n_iter
-After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to ‘par.add_peaks’+1. As with ‘par.IterFact’, increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.
+After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to [‘par.add_peaks’](/p/infos/wiki/par_add_peaks)+1. As with ‘par.IterFact’, increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.

 For ‘par.add_peaks=5’:
 par.n_iter=\[3 3 3 3 3 6\];
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A. Smith</dc:creator><pubDate>Thu, 08 Sep 2016 14:51:08 -0000</pubDate><guid>https://sourceforge.netdb89b665067212d8734832a4e14feea1826e6968</guid></item><item><title>par_n_iter modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_n_iter/</link><description>&lt;div class="markdown_content"&gt;&lt;h3 id="parn_iter"&gt;par.n_iter&lt;/h3&gt;
&lt;p&gt;After each sub-spectrum is fitted, the fit is recombined to correct for peak overlap among sub-spectra, after which the fitting of sub-spectra is repeated. The number of repetitions is determined by ‘par.n_iter’. If a dynamic peak list is being used, then the iterative fitting is repeated after each peak addition/removal step. This means that the number of iterations must be specified at each step. Thus, the number of elements in ‘par.n_iter’ must be equal to ‘par.add_peaks’+1. As with ‘par.IterFact’, increasing the values in ‘par.n_iter’ will improve fitting, but improvements will be reduced as values get higher. However, because ‘par.n_iter’ changes the number of iterations that include corrections for peak overlap, increasing the value of ‘par.n_iter’ is often more beneficial than increasing the value of ‘par.IterFact’.&lt;/p&gt;
&lt;p&gt;For ‘par.add_peaks=5’:&lt;br/&gt;
par.n_iter=[3 3 3 3 3 6];&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A. Smith</dc:creator><pubDate>Thu, 08 Sep 2016 10:31:32 -0000</pubDate><guid>https://sourceforge.net791fe1ff328590fc78be06beda9e07d805d5eb4b</guid></item></channel></rss>