<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Home</title><link>https://sourceforge.net/p/sidmon3/wiki/Home/</link><description>Recent changes to Home</description><atom:link href="https://sourceforge.net/p/sidmon3/wiki/Home/feed" rel="self"/><language>en</language><lastBuildDate>Fri, 11 Feb 2022 17:03:49 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/sidmon3/wiki/Home/feed" rel="self" type="application/rss+xml"/><item><title>Home modified by Nathan Towne</title><link>https://sourceforge.net/p/sidmon3/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -1,97 +0,0 @@
-&lt;h1&gt;&lt;tt style="font-size: 32;"&gt;sidmon&lt;/tt&gt; for sudden ionospheric disturbance (SID) monitoring&lt;/h1&gt;
-
-&lt;h2&gt;Introduction&lt;/h2&gt;
-
-&lt;p&gt;&lt;tt&gt;&lt;a href="../doc/sidmon2.html"&gt;sidmon&lt;/a&gt;&lt;/tt&gt; is a python program for receiving and recording submarine-transmitter signal intensities in the VLF frequency range using a computer sound card and the &lt;tt&gt;alsaaudio&lt;/tt&gt; package.  The intensities of these signals reflect the ability of radio waves at those wavelengths to propagate in what is essentially a waveguide formed by the earth and the ionosphere above it.  Fluctuations in those signal intensities often reflect daytime perturbations of the ionosphere by solar processes, such as solar flares and coronal mass ejections, making VLF receivers useful tools for probing the sun and the earth's ionosphere.  For more information see the &lt;a href="http://solar-center.stanford.edu/SID/" rel="nofollow"&gt;SID Monitors page&lt;/a&gt; and the &lt;a href="http://solar-center.stanford.edu/SID/data/data-access.html" rel="nofollow"&gt;SID data access page&lt;/a&gt; at the &lt;a href="http://solar-center.stanford.edu/" rel="nofollow"&gt;Stanford Solar Center&lt;/a&gt;.&lt;/p&gt;
-
-&lt;center&gt;&lt;img src="../doc/fig1.png" width="700"/&gt;&lt;/center&gt;
-
-&lt;p&gt;&lt;tt&gt;sidmon 3&lt;/tt&gt; is an enhanced &lt;tt&gt;sidmon 2&lt;/tt&gt; that can employ two loop antennas that are combined to form a simple phased array.  With a single loop, the signal intensity of a transmitter depends on the orientation of the loop relative to the great arc to the transmitter.  A loop is most sensitive if it is edge on (tangent) to the great arc, while an orthogonal loop intercepts no magnetic flux and hence has zero sensitivity to that transmitter.  Two loops, in contrast, can be combined with weights that 'point' the combined loops toward a transmitter, catching maximum flux into the data stream, while injecting equivalent noise of only one ADC.  This can be done digitally for each transmitter being monitored.  In this sense, the antenna/receiver system become isotropic - able to receive with equal sensitivity in all directions.&lt;/p&gt;
-
-&lt;p&gt;This is an interesting technique for monitoring transmitter intensities, detecting SIDS, and isotropic observing in general.  There is also something interesting about the orthogonal beams mentioned earlier, i.e., the ones that intercept no flux from its transmitter, such as happens when the waves are traveling along the great arc.  But when the path deviates from the great arc, it catches some flux, which the receiver picks up.  So the more interesting thing is that the orthogonal beam can detect deviations of the path from the great arc.  In fact, there is remarkable sensitivity realized in &lt;tt&gt;sidmon 3&lt;/tt&gt; of &amp;lt; 0.1 degree on one-minute integrations, that allows another way to detect SIDs and how the ionosphere is impacted by x-rays from solar flares.  &lt;/p&gt;
-
-&lt;p&gt;In the following figure, the uncalibrated intensity is the blue trace, while the calibrated direction relative to the great arc (more precisely, the beam pointing) is the red trace, to which the vertical scale applies.  Notice the very small range of that scale.  There is a SID detection after 1900 UT, evident in both the intensity trace and direction trace..&lt;/p&gt;
-
-&lt;center&gt;&lt;img src="../doc/20220202towne16NML.png" width="700"/&gt;&lt;/center&gt;
-
-&lt;p&gt;The &lt;tt&gt;&lt;a href="../sidmon2.html"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document describes most of the setup of a &lt;tt&gt;sidmon 3&lt;/tt&gt; observatory.  The remainder of this document describes the setup of the loop antennae and beam pointing specific to &lt;tt&gt;sidmon 3&lt;/tt&gt;.&lt;/p&gt;
-
-&lt;h2&gt;Antenna setup&lt;/h2&gt;
-
-&lt;p&gt;To measure source direction and transients, two loop antennae are required.  It is preferable to fabricate them identically, although antenna gains can be entered into the header file.  For example, imagine two antennae on one-meter spindles, one consisting of 30 turns, and the other 35 turns.  Their gain can be set to 30 and 35 m&lt;sup&gt;2&lt;/sup&gt; T, where 'T' represents a turn on the spindle.  Their entries in the header files would be: &lt;/p&gt;&lt;pre&gt;# antenna ant0, 30
-# antenna ant1, 35&lt;/pre&gt;  The two loops are then mounted upright and at right angles to each other a short distance apart.  The antennae are wired to a stereo 3.5 mm audio connector.  In these connectors, the tip contact is channel 0, the center contact is channel 1, and the bottom sleeve contact is common.  Connect one wire from each antenna to the common contact, and the other wire of each to one or the other of the two remaing contacts.  It does not matter particularly which.&lt;p&gt;&lt;/p&gt;
-
-&lt;p&gt;At this point the user should set up single-antenna operation as outlined in the &lt;tt&gt;&lt;a href="../sidmon2.html"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document, and taking data.  It is not necessary to set up the veto feature.  At this point it time to determine a setting for the beam direction for each transmitter.  This value is entered in the header file on the transmitter's line.  To do this, there is a switch, &lt;tt&gt;--scan &amp;lt;point count&amp;gt;&lt;/tt&gt;, that tells &lt;tt&gt;sidmon&lt;/tt&gt; to scan beam rotation angles, taking intensity data and a cross correlation in the process.  &lt;/p&gt;&lt;pre&gt;src/sidmon.py --device &amp;lt;device name&amp;gt; --scan 46 --channelcount 2&lt;/pre&gt;  The scan is over 180 degrees – not 360ˆ because the second 180 is redundant.  When done, it plots both of those quantities as shown in this figure.&lt;p&gt;&lt;/p&gt;
-
-&lt;center&gt;&lt;img src="../doc/scan.png" width="600"/&gt;&lt;/center&gt;
-
-&lt;p&gt;The first plot is of intensities of the transmitters being recorded.  The second is of the x/y cross correlation – more precisely they are of inverse tangents representing angles of the transmitter away from the primary beam, essentially a pointing error.  We are looking for the beam angle at which the error angle is zero, meaing that the primary beam is on the transmitter's bearing.  For example, the setting for the red trace is +44°, and this value is entered in the transmitter's line in the header file.&lt;/p&gt;
-
-&lt;p&gt;Note that the slope of the error angle as a function of beam angle need not be negative.  It depends on which of the antennae is channel 0.  Also, because the loops can be flipped, which reverses the sign of the intercepted flux, this orientation of the loops affects the slope as well.  So one may set the slope as part of the setup by reversing the channel assignments, reversing the leads of one of the loop, or flipping one of the antennae.  This orientation also affects the sign of the angular error represented in the data.  &lt;/p&gt;
-
-&lt;p&gt;One can fine tune the beam angle using from a &lt;tt&gt;supersid_plot.py&lt;/tt&gt; graph, such as shown in the following figure of NML direction (relative to its primary beam) during day-time hours where the signal is relatively stable.  &lt;/p&gt;&lt;pre&gt;src/supersid_plot.py -af &amp;lt;file path&amp;gt; -ps NML2 --dir&lt;/pre&gt;&lt;p&gt;&lt;/p&gt;
-
-&lt;center&gt;&lt;img src="../doc/directionplot.png" width="500"/&gt;&lt;/center&gt;
-
-&lt;p&gt;During those hours, the transmitter direction is -0.1° from its primary beam.  Although already quite small in this example, this difference can be set to zero for later data taking by shifting the beam angle in the transmitter line in the header file by 0.1°, the sign of which is determined by the slope in the scan figure above.  Do not perform this step during night-time hours as the signal direction, like the intensity, varies erratically during those hours.&lt;/p&gt;
-
-&lt;h2&gt;The header file&lt;/h2&gt;
-
-&lt;p&gt;An example header file monitoring two transmitters in two goups and recording directions is this.&lt;/p&gt;
-
-&lt;pre style="font-size: 11;"&gt;# Site = A151
-# Contact = Nathan Towne towne56@ownmail.net
-# Longitude = -107.2391
-# Latitude = 34.1116
-# Elevation = 2020
-# LogInterval = 4.87
-#
-# Stations = NPM, NAA, NPMd, NAAd
-# Frequencies = 21400, 24000, 21400, 24000
-#
-# antenna = ant0, 0.89, 166.0
-# antenna = ant1, 1.0, 76.0
-#
-# samplerate = 64000
-# fourierframe = 16384
-# integrationtime = 4.87
-#
-# group = npm, 21100, 21700, 1
-# transmitter = NPM, 21400, lambda f: np.exp(-((f - 21400)/47)**2/2), -71.4, +21.420166, -158.151140, Pearl Harbour; Lualuahei; HI
-#
-# group = naa, 23600, 24400, 1
-# transmitter = NAA, 24000, lambda f: np.exp(-((f - 24000)/47)**2/2), 85.2, +44.644936, -067.281639, Cutler; ME&lt;/pre&gt;
-
-&lt;p&gt;Some of this is mentioned in the &lt;tt&gt;&lt;a href="../sidmon2.html#header"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document.  When running in the &lt;tt&gt;--channelcount 2&lt;/tt&gt; mode, there are additions in the &lt;tt&gt;Stations&lt;/tt&gt; and &lt;tt&gt;Frequencies&lt;/tt&gt; lines for the benefit of &lt;tt&gt;supersid_plot.py&lt;/tt&gt; because &lt;tt&gt;sidmon&lt;/tt&gt; outputs directions as well as intensities.  The additional names are arbitrary, but must be distinct.  There are also additional parameters in the transmitter lines.  To reiterate, this file may only be used with the &lt;tt&gt;sidmon --channelcount 2&lt;/tt&gt; switch because of the additional parameters.&lt;/p&gt;
-
-&lt;p&gt;The antenna lines are there to provide the gain parameter.  In the example above, there is an additional parameter giving the antenna's orientation relative to geographic north, for reference.  But it is not used by &lt;tt&gt;sidmon&lt;/tt&gt;. &lt;/p&gt;
-
-&lt;p&gt;The parameters &lt;tt&gt;samplerate&lt;/tt&gt;, &lt;tt&gt;fourierframe&lt;/tt&gt;, and &lt;tt&gt;integrationtime&lt;/tt&gt; are present in the file and should not be given on the commandline.  The sample rate is in Hz; the fourier frame sample count should not be changed; and the integration time is in seconds.   The last is a duplicate of the &lt;tt&gt;LogInterval&lt;/tt&gt; parameter.&lt;/p&gt;
-
-&lt;p&gt;The transmitter lines have one additional required parameter beyond those required by &lt;tt&gt;sidmon 2&lt;/tt&gt;, which is the beam direction in degrees as determined by the scan plot.  In the example above there are also latitude, longitude, and a description string placed there for reference.&lt;/p&gt;
-
-&lt;h2&gt;Other notes&lt;/h2&gt;
-
-&lt;p&gt;&lt;tt&gt;supersid_plot.py&lt;/tt&gt; allows the &lt;tt&gt;--dir&lt;/tt&gt; switch, which tells &lt;tt&gt;supersid_plot.py&lt;/tt&gt; to show the vertical scale on the plot.  Use this switch when plotting directions where, unlike intensities, there is a definite unit to the quantities plottted.  The second figure above shows the scale and label with this switch.&lt;/p&gt;
-
-
-
-
-
-
-
-
-
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Towne</dc:creator><pubDate>Fri, 11 Feb 2022 17:03:49 -0000</pubDate><guid>https://sourceforge.net16ec20cab6a8050affae97ccd2b74e2c4017723e</guid></item><item><title>Home modified by Nathan Towne</title><link>https://sourceforge.net/p/sidmon3/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,8 +1,97 @@
-Welcome to your wiki!
+&lt;h1&gt;&lt;tt style="font-size: 32;"&gt;sidmon&lt;/tt&gt; for sudden ionospheric disturbance (SID) monitoring&lt;/h1&gt;

-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+&lt;h2&gt;Introduction&lt;/h2&gt;

-The wiki uses [Markdown](/p/sidmon3/wiki/markdown_syntax/) syntax.
+&lt;p&gt;&lt;tt&gt;&lt;a href="../doc/sidmon2.html"&gt;sidmon&lt;/a&gt;&lt;/tt&gt; is a python program for receiving and recording submarine-transmitter signal intensities in the VLF frequency range using a computer sound card and the &lt;tt&gt;alsaaudio&lt;/tt&gt; package.  The intensities of these signals reflect the ability of radio waves at those wavelengths to propagate in what is essentially a waveguide formed by the earth and the ionosphere above it.  Fluctuations in those signal intensities often reflect daytime perturbations of the ionosphere by solar processes, such as solar flares and coronal mass ejections, making VLF receivers useful tools for probing the sun and the earth's ionosphere.  For more information see the &lt;a href="http://solar-center.stanford.edu/SID/" rel="nofollow"&gt;SID Monitors page&lt;/a&gt; and the &lt;a href="http://solar-center.stanford.edu/SID/data/data-access.html" rel="nofollow"&gt;SID data access page&lt;/a&gt; at the &lt;a href="http://solar-center.stanford.edu/" rel="nofollow"&gt;Stanford Solar Center&lt;/a&gt;.&lt;/p&gt;

-[[members limit=20]]
-[[download_button]]
+&lt;center&gt;&lt;img src="../doc/fig1.png" width="700"/&gt;&lt;/center&gt;
+
+&lt;p&gt;&lt;tt&gt;sidmon 3&lt;/tt&gt; is an enhanced &lt;tt&gt;sidmon 2&lt;/tt&gt; that can employ two loop antennas that are combined to form a simple phased array.  With a single loop, the signal intensity of a transmitter depends on the orientation of the loop relative to the great arc to the transmitter.  A loop is most sensitive if it is edge on (tangent) to the great arc, while an orthogonal loop intercepts no magnetic flux and hence has zero sensitivity to that transmitter.  Two loops, in contrast, can be combined with weights that 'point' the combined loops toward a transmitter, catching maximum flux into the data stream, while injecting equivalent noise of only one ADC.  This can be done digitally for each transmitter being monitored.  In this sense, the antenna/receiver system become isotropic - able to receive with equal sensitivity in all directions.&lt;/p&gt;
+
+&lt;p&gt;This is an interesting technique for monitoring transmitter intensities, detecting SIDS, and isotropic observing in general.  There is also something interesting about the orthogonal beams mentioned earlier, i.e., the ones that intercept no flux from its transmitter, such as happens when the waves are traveling along the great arc.  But when the path deviates from the great arc, it catches some flux, which the receiver picks up.  So the more interesting thing is that the orthogonal beam can detect deviations of the path from the great arc.  In fact, there is remarkable sensitivity realized in &lt;tt&gt;sidmon 3&lt;/tt&gt; of &amp;lt; 0.1 degree on one-minute integrations, that allows another way to detect SIDs and how the ionosphere is impacted by x-rays from solar flares.  &lt;/p&gt;
+
+&lt;p&gt;In the following figure, the uncalibrated intensity is the blue trace, while the calibrated direction relative to the great arc (more precisely, the beam pointing) is the red trace, to which the vertical scale applies.  Notice the very small range of that scale.  There is a SID detection after 1900 UT, evident in both the intensity trace and direction trace..&lt;/p&gt;
+
+&lt;center&gt;&lt;img src="../doc/20220202towne16NML.png" width="700"/&gt;&lt;/center&gt;
+
+&lt;p&gt;The &lt;tt&gt;&lt;a href="../sidmon2.html"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document describes most of the setup of a &lt;tt&gt;sidmon 3&lt;/tt&gt; observatory.  The remainder of this document describes the setup of the loop antennae and beam pointing specific to &lt;tt&gt;sidmon 3&lt;/tt&gt;.&lt;/p&gt;
+
+&lt;h2&gt;Antenna setup&lt;/h2&gt;
+
+&lt;p&gt;To measure source direction and transients, two loop antennae are required.  It is preferable to fabricate them identically, although antenna gains can be entered into the header file.  For example, imagine two antennae on one-meter spindles, one consisting of 30 turns, and the other 35 turns.  Their gain can be set to 30 and 35 m&lt;sup&gt;2&lt;/sup&gt; T, where 'T' represents a turn on the spindle.  Their entries in the header files would be: &lt;/p&gt;&lt;pre&gt;# antenna ant0, 30
+# antenna ant1, 35&lt;/pre&gt;  The two loops are then mounted upright and at right angles to each other a short distance apart.  The antennae are wired to a stereo 3.5 mm audio connector.  In these connectors, the tip contact is channel 0, the center contact is channel 1, and the bottom sleeve contact is common.  Connect one wire from each antenna to the common contact, and the other wire of each to one or the other of the two remaing contacts.  It does not matter particularly which.&lt;p&gt;&lt;/p&gt;
+
+&lt;p&gt;At this point the user should set up single-antenna operation as outlined in the &lt;tt&gt;&lt;a href="../sidmon2.html"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document, and taking data.  It is not necessary to set up the veto feature.  At this point it time to determine a setting for the beam direction for each transmitter.  This value is entered in the header file on the transmitter's line.  To do this, there is a switch, &lt;tt&gt;--scan &amp;lt;point count&amp;gt;&lt;/tt&gt;, that tells &lt;tt&gt;sidmon&lt;/tt&gt; to scan beam rotation angles, taking intensity data and a cross correlation in the process.  &lt;/p&gt;&lt;pre&gt;src/sidmon.py --device &amp;lt;device name&amp;gt; --scan 46 --channelcount 2&lt;/pre&gt;  The scan is over 180 degrees – not 360ˆ because the second 180 is redundant.  When done, it plots both of those quantities as shown in this figure.&lt;p&gt;&lt;/p&gt;
+
+&lt;center&gt;&lt;img src="../doc/scan.png" width="600"/&gt;&lt;/center&gt;
+
+&lt;p&gt;The first plot is of intensities of the transmitters being recorded.  The second is of the x/y cross correlation – more precisely they are of inverse tangents representing angles of the transmitter away from the primary beam, essentially a pointing error.  We are looking for the beam angle at which the error angle is zero, meaing that the primary beam is on the transmitter's bearing.  For example, the setting for the red trace is +44°, and this value is entered in the transmitter's line in the header file.&lt;/p&gt;
+
+&lt;p&gt;Note that the slope of the error angle as a function of beam angle need not be negative.  It depends on which of the antennae is channel 0.  Also, because the loops can be flipped, which reverses the sign of the intercepted flux, this orientation of the loops affects the slope as well.  So one may set the slope as part of the setup by reversing the channel assignments, reversing the leads of one of the loop, or flipping one of the antennae.  This orientation also affects the sign of the angular error represented in the data.  &lt;/p&gt;
+
+&lt;p&gt;One can fine tune the beam angle using from a &lt;tt&gt;supersid_plot.py&lt;/tt&gt; graph, such as shown in the following figure of NML direction (relative to its primary beam) during day-time hours where the signal is relatively stable.  &lt;/p&gt;&lt;pre&gt;src/supersid_plot.py -af &amp;lt;file path&amp;gt; -ps NML2 --dir&lt;/pre&gt;&lt;p&gt;&lt;/p&gt;
+
+&lt;center&gt;&lt;img src="../doc/directionplot.png" width="500"/&gt;&lt;/center&gt;
+
+&lt;p&gt;During those hours, the transmitter direction is -0.1° from its primary beam.  Although already quite small in this example, this difference can be set to zero for later data taking by shifting the beam angle in the transmitter line in the header file by 0.1°, the sign of which is determined by the slope in the scan figure above.  Do not perform this step during night-time hours as the signal direction, like the intensity, varies erratically during those hours.&lt;/p&gt;
+
+&lt;h2&gt;The header file&lt;/h2&gt;
+
+&lt;p&gt;An example header file monitoring two transmitters in two goups and recording directions is this.&lt;/p&gt;
+
+&lt;pre style="font-size: 11;"&gt;# Site = A151
+# Contact = Nathan Towne towne56@ownmail.net
+# Longitude = -107.2391
+# Latitude = 34.1116
+# Elevation = 2020
+# LogInterval = 4.87
+#
+# Stations = NPM, NAA, NPMd, NAAd
+# Frequencies = 21400, 24000, 21400, 24000
+#
+# antenna = ant0, 0.89, 166.0
+# antenna = ant1, 1.0, 76.0
+#
+# samplerate = 64000
+# fourierframe = 16384
+# integrationtime = 4.87
+#
+# group = npm, 21100, 21700, 1
+# transmitter = NPM, 21400, lambda f: np.exp(-((f - 21400)/47)**2/2), -71.4, +21.420166, -158.151140, Pearl Harbour; Lualuahei; HI
+#
+# group = naa, 23600, 24400, 1
+# transmitter = NAA, 24000, lambda f: np.exp(-((f - 24000)/47)**2/2), 85.2, +44.644936, -067.281639, Cutler; ME&lt;/pre&gt;
+
+&lt;p&gt;Some of this is mentioned in the &lt;tt&gt;&lt;a href="../sidmon2.html#header"&gt;sidmon 2&lt;/a&gt;&lt;/tt&gt; usage document.  When running in the &lt;tt&gt;--channelcount 2&lt;/tt&gt; mode, there are additions in the &lt;tt&gt;Stations&lt;/tt&gt; and &lt;tt&gt;Frequencies&lt;/tt&gt; lines for the benefit of &lt;tt&gt;supersid_plot.py&lt;/tt&gt; because &lt;tt&gt;sidmon&lt;/tt&gt; outputs directions as well as intensities.  The additional names are arbitrary, but must be distinct.  There are also additional parameters in the transmitter lines.  To reiterate, this file may only be used with the &lt;tt&gt;sidmon --channelcount 2&lt;/tt&gt; switch because of the additional parameters.&lt;/p&gt;
+
+&lt;p&gt;The antenna lines are there to provide the gain parameter.  In the example above, there is an additional parameter giving the antenna's orientation relative to geographic north, for reference.  But it is not used by &lt;tt&gt;sidmon&lt;/tt&gt;. &lt;/p&gt;
+
+&lt;p&gt;The parameters &lt;tt&gt;samplerate&lt;/tt&gt;, &lt;tt&gt;fourierframe&lt;/tt&gt;, and &lt;tt&gt;integrationtime&lt;/tt&gt; are present in the file and should not be given on the commandline.  The sample rate is in Hz; the fourier frame sample count should not be changed; and the integration time is in seconds.   The last is a duplicate of the &lt;tt&gt;LogInterval&lt;/tt&gt; parameter.&lt;/p&gt;
+
+&lt;p&gt;The transmitter lines have one additional required parameter beyond those required by &lt;tt&gt;sidmon 2&lt;/tt&gt;, which is the beam direction in degrees as determined by the scan plot.  In the example above there are also latitude, longitude, and a description string placed there for reference.&lt;/p&gt;
+
+&lt;h2&gt;Other notes&lt;/h2&gt;
+
+&lt;p&gt;&lt;tt&gt;supersid_plot.py&lt;/tt&gt; allows the &lt;tt&gt;--dir&lt;/tt&gt; switch, which tells &lt;tt&gt;supersid_plot.py&lt;/tt&gt; to show the vertical scale on the plot.  Use this switch when plotting directions where, unlike intensities, there is a definite unit to the quantities plottted.  The second figure above shows the scale and label with this switch.&lt;/p&gt;
+
+
+
+
+
+
+
+
+
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Towne</dc:creator><pubDate>Fri, 11 Feb 2022 17:02:01 -0000</pubDate><guid>https://sourceforge.net828f5ef1d6da82663fc10027912aba5614ab3e91</guid></item><item><title>Home modified by Nathan Towne</title><link>https://sourceforge.net/p/sidmon3/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Welcome to your wiki!&lt;/p&gt;
&lt;p&gt;This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: &lt;span&gt;[SamplePage]&lt;/span&gt;.&lt;/p&gt;
&lt;p&gt;The wiki uses &lt;a class="" href="/p/sidmon3/wiki/markdown_syntax/"&gt;Markdown&lt;/a&gt; syntax.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;h6&gt;Project Members:&lt;/h6&gt;
	&lt;ul class="md-users-list"&gt;
		&lt;li&gt;&lt;a href="/u/towne56/"&gt;Nathan Towne&lt;/a&gt; (admin)&lt;/li&gt;
		
	&lt;/ul&gt;&lt;br/&gt;
&lt;p&gt;&lt;span class="download-button-62053fd59be24fbbbb4c991d" style="margin-bottom: 1em; display: block;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Towne</dc:creator><pubDate>Thu, 10 Feb 2022 16:39:53 -0000</pubDate><guid>https://sourceforge.netb0e637727b5816d4a985876a4adb276e3502a882</guid></item></channel></rss>