<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Field Precision software tips &#187; OmniTrak</title>
	<atom:link href="http://fieldp.com/myblog/tag/omnitrak/feed/" rel="self" type="application/rss+xml" />
	<link>http://fieldp.com/myblog</link>
	<description>Effective finite-element modeling of electromagnetic fields</description>
	<lastBuildDate>Thu, 17 May 2012 12:45:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Dual voltage modulations in OmniTrak</title>
		<link>http://fieldp.com/myblog/2008/dual-voltage-modulations-in-omnitrak/</link>
		<comments>http://fieldp.com/myblog/2008/dual-voltage-modulations-in-omnitrak/#comments</comments>
		<pubDate>Sun, 16 Nov 2008 21:46:30 +0000</pubDate>
		<dc:creator>shumphries</dc:creator>
				<category><![CDATA[Educational]]></category>
		<category><![CDATA[NewFeatures]]></category>
		<category><![CDATA[Techniques]]></category>
		<category><![CDATA[electrostatics]]></category>
		<category><![CDATA[OmniTrak]]></category>
		<category><![CDATA[particle orbits]]></category>
		<category><![CDATA[RF electric field]]></category>

		<guid isPermaLink="false">http://fieldp.com/myblog/?p=125</guid>
		<description><![CDATA[<p>In the Track mode (single-particle orbits), OmniTrak has long had the capability of including temporal modulations of electric and magnetic fields to approximate RF fields in the long-wavelength limit. For electric fields, the procedure has been to multiply potential values by a modulation function M(t). Recently, I have worked on an application to design an RF [...]]]></description>
			<content:encoded><![CDATA[<p>In the <em>Track </em>mode (single-particle orbits), <strong>OmniTrak </strong>has long had the capability of including temporal modulations of electric and magnetic fields to approximate RF fields in the long-wavelength limit. For electric fields, the procedure has been to multiply potential values by a modulation function <em>M</em>(<em>t</em>). Recently, I have worked on an application to design an RF ion extractor with a biased control electrode. This situation is fundamentally different. When applying a simple modulation, the assumption is that the spatial field distribution is self-similar. The only change with time is the normalization of the field solution. This type of field solution involves a reference potential (ground) and one independent value of the time-varying voltage.</p>
<p>With two independent time-varying electrode voltages, the spatial distribution of the field changes at each instant. Clearly, it would be impractical to solve for the three-dimensional electric field at each integration step of a particle orbit. Fortunately, there is a simple way to find the time-varying field when there are two independent voltages. We can understand the method with reference to the field solution illustrated in the first figure below. The simple three-electrode system has a ground plane at the bottom. Independent voltages may be applied to the electrode at the top left (<em>V1</em>) and right (<em>V2</em>). We can construct two normalized base solutions: solution <em>S10</em> has <em>V1</em> = 1.0 V and <em>V2</em> = 0.0 V while solution <em>S01</em> has <em>V1</em> = 0.0 V and <em>V2</em> = 1.0 V. In the absence of nonlinear materials, the set of all possible electrostatic solutions with arbitrary voltages <em>V1</em> and <em>V2</em> may be generated by a linear combination of the base functions:</p>
<p><em>S</em> = <em>V1*S10</em> + <em>V2*S01</em>.</p>
<p>To illustrate, the bottom solution in the first figure is the sum of the base functions. The same solution would follow from a direct <strong>HiPhi </strong>solution with <em>V1</em> = <em>V2</em> = 1.0 V.</p>
<p>The following procedure is used for modulated dual-voltage solutions in <strong>OmniTrak</strong>:</p>
<ul>
<li>Prepare two base electrostatic solutions with <strong>HiPhi </strong>using the same mesh. One or more reference electrodes in both solutions are grounded (φ = 0.0 V). In the first solution, one electrode (or set of electrodes) has <em>V1</em> = 1.0 V and the other has <em>V2</em> = 0.0 V. The voltages levels are reversed in the second solution.</li>
<li>Load the first solution with the <em>EFIELD3D </em>command. The program reads the mesh characteristics as well as the potential values at all nodes, φ1(<em>i,j,k</em>). A normalization factor may be included in the command to set the amplitude <em>V1</em> in solution <em>S10</em>.</li>
<li>Load the second solution with the new <em>EFIELD3D2 </em>command. In this case, <strong>OmniTrak </strong>checks that the mesh is identical to the previous one and stores the potential values φ2(<em>i,j,k</em>). Again, a normalization factor may be used to set the amplitude <em>V2</em> for <em>S01</em>.</li>
<li>The command <em>MODFUNC E</em> is used to define a modulation function <em>M1</em>(<em>t</em>) for <em>S10</em>, while the command <em>MODFUNC E2</em> sets the modulation function <em>M2</em>(<em>t</em>) for <em>S01</em>.</li>
</ul>
<p>During orbit tracking, the program uses electrostatic potential values of the form</p>
<p>φ = <em>M1</em>(<em>t</em>)*<em>S10</em> + <em>M2</em>(<em>t</em>)*<em>S01</em>,</p>
<p>as input to the electric field interpolation routine. Because much of the computational work involves identification of the element occupied by the particle, there is little change in the orbit tracking time penalty for a dual-voltage solution.</p>
<p>We can track a proton through the solution shown in the first figure to demonstrate the procedure. The <em>Field</em> section of the <strong>OmniTrak </strong>script includes the following commands:</p>
<pre>EFIELD3D: ThreeElect01.HOU 100.0
MODFUNC(E) &gt; sin(1.2566E7*$t)
EFIELD3D2: ThreeElect02.HOU 200.0
MODFUNC(E2) &gt; sin(3.1416E7*$t)</pre>
<p>The left-hand electrode has a sinusoidal variation at 2.0 MHz with amplitude 100 V. The peak electric field far from the gap is <em>Ex</em> = -2000 V/m. The voltage on the right-hand side varies at 5.0 MHz with amplitude 200 V (<em>Ex</em> = -4000.0 V/m). A 250 eV proton moving in <em>z</em> is injected near the left-hand boundary. The transit time over the 20.0 cm distance is about 1.0 μs. The commands</p>
<pre>LISTON 1
LISTTYPE EField</pre>
<p>specify an electric-field listing along the particle trajectory. The second figure shows the resulting electric field experienced by particle as a function of axial position.</p>
<p>For more information on <strong>OmniTrak</strong>, please use this link: <a href="http://www.fieldp.com/omnitrak.html" target="_blank">http://www.fieldp.com/omnitrak.html</a>.<br />
<img class="alignnone" title="Base solutions, three-electrode system" src="http://www.fieldp.com/myblog/images/dualvoltagesuper.png" alt="" width="400" height="346" /></p>
<p><img class="alignnone" title="Voltage level along a protion trajectory" src="http://www.fieldp.com/myblog/images/dualvoltageex.png" alt="" width="400" height="298" /></p>
]]></content:encoded>
			<wfw:commentRss>http://fieldp.com/myblog/2008/dual-voltage-modulations-in-omnitrak/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Porting field information to OmniTrak with Mapper</title>
		<link>http://fieldp.com/myblog/2008/porting-field-information-to-omnitrak-with-mapper/</link>
		<comments>http://fieldp.com/myblog/2008/porting-field-information-to-omnitrak-with-mapper/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 23:12:48 +0000</pubDate>
		<dc:creator>shumphries</dc:creator>
				<category><![CDATA[NewFeatures]]></category>
		<category><![CDATA[Techniques]]></category>
		<category><![CDATA[magnetic field map]]></category>
		<category><![CDATA[Mapper]]></category>
		<category><![CDATA[OmniTrak]]></category>
		<category><![CDATA[orbit calculations]]></category>

		<guid isPermaLink="false">http://fieldp.com/myblog/2008/porting-field-information-to-omnitrak-with-mapper/</guid>
		<description><![CDATA[<p>I am consulting on a project that demands extremely accurate orbit calculations in a high magnetic field environment with saturated iron. Because the organization has another consultant with extensive experience with Maxwell 3D, the working plan is that he performs the magnetic field calculations. The resulting field values in the beam propagation region are transferred to [...]]]></description>
			<content:encoded><![CDATA[<p>I am consulting on a project that demands extremely accurate orbit calculations in a high magnetic field environment with saturated iron. Because the organization has another consultant with extensive experience with <strong>Maxwell 3D</strong>, the working plan is that he performs the magnetic field calculations. The resulting field values in the beam propagation region are transferred to <strong>OmniTrak </strong>in the neutral <strong>AMaze </strong>field table format. I advise on the orbit calculations, and I performed benchmark checks on the 3D field calculations with <strong>Magnum</strong>. After several rounds making sure we were representing the same system, the end result was that the <strong>Magnum </strong>results were numerically identical to the Ansoft results. There were two differences:</p>
<p>* The <strong>Maxwell 3D</strong> solution took several times longer.</p>
<p>* The Ansoft results had high-frequency noise.</p>
<p>I couldn&#8217;t do much about the first problem, but I was able to alleviate the second one. <strong>OmniTrak </strong>has long included a simple command-line utility for field table preprocessing called <strong>FTabTool</strong>. I decided to expand the core of the program and to create a full-featured interactive program <strong>Mapper</strong>. The first figure below shows a screen shot. It was frustrating to deal with field tables without being able to see them, so we included capabilities for 2D slice plots and 1D scans. Most important, we added new routines to smooth values in the field tables. The smoothing method follows the same relaxation techniques used to solve the Poisson equation. The result is that the smoothed values are actually closer to an ideal physical solution.</p>
<p>The second picture below illustrates this effect. I prepared a field table of moderate accuracy in the space <em>z</em> ≥ 0.0 for a magnetic dipole and then reflected it about the midplane using the <em>Reflection </em>command in <strong>Mapper</strong>. The top graph shows a scan of numerical values of <em>Bz</em>(0.0,0.0,z). Theoretically, the variation should be parabolic. The lower graph shows the data after relaxation smoothing. The method leaves the central value almost unchanged, while a conventional smoothing algorithm would raise the central field significantly.</p>
<p>If you would like to learn more about <strong>Mapper</strong>, please use this link to download the <strong>OmniTrak </strong>manual (see Chap. 18):</p>
<p><a href="http://www.fieldp.com/library/omnitrak.pdf">http://www.fieldp.com/library/omnitrak.pdf</a></p>
<p><img src="http://www.fieldp.com/myblog/images/mapper.png" alt="Mapper screen shot" width="434" height="367" /></p>
<p><img src="http://www.fieldp.com/myblog/images/mapper_smooth.png" alt="Mapper smooting demo" width="400" height="566" /></p>
]]></content:encoded>
			<wfw:commentRss>http://fieldp.com/myblog/2008/porting-field-information-to-omnitrak-with-mapper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

