<?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_rangeX</title><link>https://sourceforge.net/p/infos/wiki/par_rangeX/</link><description>Recent changes to par_rangeX</description><atom:link href="https://sourceforge.net/p/infos/wiki/par_rangeX/feed" rel="self"/><language>en</language><lastBuildDate>Mon, 12 Sep 2016 15:13:28 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/infos/wiki/par_rangeX/feed" rel="self" type="application/rss+xml"/><item><title>par_rangeX modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_rangeX/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -1,5 +1,5 @@
 ###par.rangeX
-For each dimension, X, one may specify the range that the peak positions may vary. Using a peak list with initial peak positions ‘fit0.deltaX’, the peaks may then move only between ‘fit0.deltaX–par.rangeX/2’ and ‘fit0.deltaX+par.rangeX/2’. This is useful if the peak positions are approximately known, but some variability is need to optimize the fitting. One typically only uses this setting with fixed peak lists, although when used with a dynamic peak list, then this will restrict the peak positions relative to their initial placement. This usage may cause poor fitting, however, since the initial peak placement may be somewhat far from the correct position. ‘par.rangeX’ only accepts one argument.
+For each dimension, X, one may specify the range (in ppm) that the peak positions may vary. Using a peak list with initial peak positions ‘fit0.deltaX’, the peaks may then move only between ‘fit0.deltaX–par.rangeX/2’ and ‘fit0.deltaX+par.rangeX/2’. This is useful if the peak positions are approximately known, but some variability is need to optimize the fitting. One typically only uses this setting with fixed peak lists, although when used with a dynamic peak list, then this will restrict the peak positions relative to their initial placement. This usage may cause poor fitting, however, since the initial peak placement may be somewhat far from the correct position. ‘par.rangeX’ only accepts one argument.

 For the 1st dimension:

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A. Smith</dc:creator><pubDate>Mon, 12 Sep 2016 15:13:28 -0000</pubDate><guid>https://sourceforge.nete50dcd4bc22b991522651655d2927bb0431eae79</guid></item><item><title>par_rangeX modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_rangeX/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -2,4 +2,5 @@
 For each dimension, X, one may specify the range that the peak positions may vary. Using a peak list with initial peak positions ‘fit0.deltaX’, the peaks may then move only between ‘fit0.deltaX–par.rangeX/2’ and ‘fit0.deltaX+par.rangeX/2’. This is useful if the peak positions are approximately known, but some variability is need to optimize the fitting. One typically only uses this setting with fixed peak lists, although when used with a dynamic peak list, then this will restrict the peak positions relative to their initial placement. This usage may cause poor fitting, however, since the initial peak placement may be somewhat far from the correct position. ‘par.rangeX’ only accepts one argument.

 For the 1st dimension:
-par.range1=.5;
+
+    par.range1=.5;
&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:01:40 -0000</pubDate><guid>https://sourceforge.net60298c6e25c57058e5a05e15c670ca508fd55195</guid></item><item><title>par_rangeX modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_rangeX/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,2 +1,5 @@
 ###par.rangeX
 For each dimension, X, one may specify the range that the peak positions may vary. Using a peak list with initial peak positions ‘fit0.deltaX’, the peaks may then move only between ‘fit0.deltaX–par.rangeX/2’ and ‘fit0.deltaX+par.rangeX/2’. This is useful if the peak positions are approximately known, but some variability is need to optimize the fitting. One typically only uses this setting with fixed peak lists, although when used with a dynamic peak list, then this will restrict the peak positions relative to their initial placement. This usage may cause poor fitting, however, since the initial peak placement may be somewhat far from the correct position. ‘par.rangeX’ only accepts one argument.
+
+For the 1st dimension:
+par.range1=.5;
&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 10:40:38 -0000</pubDate><guid>https://sourceforge.net84e87818f8bc76c669a15a9503b6cf6d2d035fe0</guid></item><item><title>par_rangeX modified by A. Smith</title><link>https://sourceforge.net/p/infos/wiki/par_rangeX/</link><description>&lt;div class="markdown_content"&gt;&lt;h3 id="parrangex"&gt;par.rangeX&lt;/h3&gt;
&lt;p&gt;For each dimension, X, one may specify the range that the peak positions may vary. Using a peak list with initial peak positions ‘fit0.deltaX’, the peaks may then move only between ‘fit0.deltaX–par.rangeX/2’ and ‘fit0.deltaX+par.rangeX/2’. This is useful if the peak positions are approximately known, but some variability is need to optimize the fitting. One typically only uses this setting with fixed peak lists, although when used with a dynamic peak list, then this will restrict the peak positions relative to their initial placement. This usage may cause poor fitting, however, since the initial peak placement may be somewhat far from the correct position. ‘par.rangeX’ only accepts one argument.&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:40:00 -0000</pubDate><guid>https://sourceforge.net29344fb66240e53ce83e7624e6cae759e7e4dba4</guid></item></channel></rss>