<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <language>en-us</language>
    <title>IMCA-CAT News</title>
    <description>The latest news from IMCA-CAT, Sector 17 at the Advanced Photon Source, Argonne National Laboratory.</description>
    <image>
      <url>https://imca-cat.org/tiki-download_file.php?fileId=5&amp;display</url>
      <title>Feed logo</title>
      <link>https://imca-cat.org/</link>
    </image>
    <pubDate>Fri, 17 Apr 2026 14:41:19 +0000</pubDate>
    <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator>
    <link>https://imca-cat.org/</link>
    <author>sysadmin@imca.aps.anl.gov</author>
    <dc:creator>sysadmin@imca.aps.anl.gov</dc:creator>
    <atom:link rel="self" type="application/rss+xml" href="https://imca-cat.org/tiki-blogs_rss.php"/>
    <item>
      <title>Also Goniometer problem during 2016-3</title>
      <description><![CDATA[<p>The Alio goniometer has a problem with one of the stages. The Y-axis is the affected axis which provides the raster centering at phi=0.
- For automated operation, we do not recommend, and have never recommended, using the 5um or 10um aperture.
- For automated operation, we suggest collecting a sweep from -90 to 90 to reduce the possibility of the sample rotating out of the beam.
- For manual operation, we suggest taking test shots every 45 deg from phi=-90 to 180 to ensure the crystal will stay in the beam and then collecting an appropriate sweep.
- Crystals less than 10um may be problematic, as may thin plates, however, we do recommend trying them anyway to see how they behave.
- Symptoms of problems would be observing significant under- or overshoot of the expected position during centering, particularly at phi=0 or chronic rotation out of the beam during automated collection.
- If significant problems occur, the staff can be asked to clean the stages which will usually, temporarily, improve their motion.
- Repair of the stages is planned during the January 2017 shutdown.</p>
]]></description>
      <pubDate>Wed, 18 Jan 2017 17:38:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost55-Also-Goniometer-problem-during-2016-3</link>
      <guid>https://imca-cat.org/blogpost55-Also-Goniometer-problem-during-2016-3</guid>
      <author>keefe</author>
      <dc:creator>keefe</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca45.4 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca45.4 has been released. This update provides improvements and fixes to the instrument setup and auto-mode.</p>

<ul><li>The instrument setup (Instrument -&gt; Setup... menu) will now update the Phi position if the "Initialize Goniometer" checkbox is checked. Previously, if the position was changed outside of JDirector and this setup was performed, the position would not be updated in JDirector.</li>
</ul><ul><li>If an axis move timeout error is detected, an attempt to resync the positions of the XYZ stage and goniometer axes will be made. This can help avoid certain situations where JDirector and CameraMan think the axes are at different positions than they actually are.</li>
</ul><ul><li>The Error Messages dialog now lists errors with a timestamp and in reverse chronological order so that the most recent error is at the top.</li>
</ul><ul><li>A new built-in job sample step called VerifyMount has been added which attempts to verify that the mount was successful. In particular, an attempt is made to ensure that a robot collision did not occur during the mount. If a collision may have occurred, the job is aborted. This reduces the chance of a rogue robot job that destroys all the samples by mounting them on top of each other, one after the other, or by failing to mount them in some other way.</li>
</ul>]]></description>
      <pubDate>Fri, 27 May 2016 17:43:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost54-JDirector-2-2-1_imca45-4-released</link>
      <guid>https://imca-cat.org/blogpost54-JDirector-2-2-1_imca45-4-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca44 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca44 has been released. This update provides improvements and fixes to the crystal view and diffraction centering.</p>

<ul><li>The Crystal View "Save Camera Image As..." pop-up menu item operation will now display an error message to the user if no suitable image writer was found based on the name of the destination file. Previously, an exception was thrown if the file had no extension, or, if no image writer was found for the extension, a zero-length file was written, and the user was not informed that no suitable writer was found.</li>
</ul><ul><li>Increased the size of the manual diffraction center result history from 10 to 20. This is helpful for projects where there's a need to compare rasters when there might be multiple sites of interest or when regions might be rasterized again with a smaller cell size.</li>
</ul><ul><li>Improved the diffraction center moves and syncs of the XYZ stage and Phi. In the auto-mode diffraction center, the move or sync of Phi was not interruptible, so if it hung, there was no way to stop it. This has been changed to be interruptible. In the manual-mode diffraction center, when the XYZ stage or Phi were moved or synced, it did not wait for those operations to complete. This has been corrected.</li>
</ul>]]></description>
      <pubDate>Fri, 12 Feb 2016 16:10:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost53-JDirector-2-2-1_imca44-released</link>
      <guid>https://imca-cat.org/blogpost53-JDirector-2-2-1_imca44-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Imcadr 0.36.0 released</title>
      <description><![CDATA[<p>Subject: Imcadr 0.36.0 released Imcadr 0.36.0 has been released. This update introduces new features.</p>

<ul><li>Added support for fly-scanning. Instead of doing a step-scan for each row or column of a raster, support a fly-scan for each row or column to reduce the time it takes to rasterize a raster.</li>
</ul><ul><li>Added support for computer cluster scoring. To speed up raster cell scoring, support scoring on a computer cluster.</li>
</ul><ul><li>Added configuration file support. Support reading a system-wide, user, and command-line-specified configuration file. Remove the <strike>cluster-key and </strike>cluster-nodes command line options; these are now specified in the configuration file.</li>
</ul><ul><li>Added imcadr(1) and imcadr.conf(5) man pages. Reduce the imcadr --help output to a simple usage message since the arguments are documented in imcadr(1).</li>
</ul>]]></description>
      <pubDate>Wed, 20 Jan 2016 18:34:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost52-Imcadr-0-36-0-released</link>
      <guid>https://imca-cat.org/blogpost52-Imcadr-0-36-0-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Detector update #2</title>
      <description><![CDATA[<p>An engineer from Dectris was here Dec 2 to examine the detector. In the course of their investigation, they swapped cables and circuit boards in the detector and have determined that the problem is with the module, but they are not certain what the problem is. Fortunately the issue is on the edge of the detector and is therefore a cosmetic issue and less a functional problem.</p>

<p>In the meantime, a dead pixel mask has been incorporated in the detector server to block out this region of the image, so no additional work needs to be done from the users standpoint for processing.</p>

<p>A final resolution to this problem is being determined.</p>

<p>If there are any questions/concerns, please contact the staff.</p>
]]></description>
      <pubDate>Tue, 08 Dec 2015 20:41:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost51-Detector-update-2</link>
      <guid>https://imca-cat.org/blogpost51-Detector-update-2</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Detector update</title>
      <description><![CDATA[<p>The failed module in the detector has been replaced. In the process of this repair, we have noticed some issues with a chip in a module at the bottom of the detector. A Dectris engineer will be on-site Dec 2 to address this issue, which they believe is due to a loose cable.</p>

<p>The following command can be used in autoPROC to mask out the bad chip:</p>

<p><span style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">autoPROC_XdsKeyword_UNTRUSTED_</span><span style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">RECTANGLE="798 859 2429 2526"</span></p>

<p>or use the following line in your XDS.INP file:</p>

<p>UNTRUSTED_RECTANGLE=798 859 2429 2526</p>
]]></description>
      <pubDate>Tue, 01 Dec 2015 19:01:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost50-Detector-update</link>
      <guid>https://imca-cat.org/blogpost50-Detector-update</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Detector failure</title>
      <description><![CDATA[<p>A module in the Pilatus failed after the completion of data collection Tuesday Nov 10 and the start of collection Wed Nov 11.</p>

<p>An example image is available here: <a href="https://www.imca.aps.anl.gov/~battaile/IMCA/dummy_0001.cbf" style="color:rgb(17,85,204);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;background-color:rgb(255,255,255);" target="_blank">https://www.imca.aps.anl.gov/~battaile/IMCA/dummy_0001.cbf</a></p>

<p><span style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">If you are using autoPROC, this is the command line option you need to use to mask out the bad module:</span></p>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;"><span style="font-family:arial, sans-serif;font-size:12.8px;">autoPROC_XdsKeyword_UNTRUSTED_</span><span style="font-family:arial, sans-serif;font-size:12.8px;">RECTANGLE="0 486 848 1042"</span></div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;"> </div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">If you are running XDS by itself, insert the following in your XDS.INP file:</div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;"> </div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">UNTRUSTED_RECTANGLE=0 486 848 1042</div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;"> </div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">We are now processing at the beamline using the autoPROC option to mask out the bad module.</div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;"> </div>

<div style="color:rgb(34,34,34);font-family:arial, sans-serif;font-size:12.8px;line-height:normal;">Dectris seems confident that this can be repaired on-site in under 2 hours. We are going to try to scheudle this for a machine studies day.</div>
]]></description>
      <pubDate>Thu, 12 Nov 2015 16:24:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost49-Detector-failure</link>
      <guid>https://imca-cat.org/blogpost49-Detector-failure</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca43.1 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca43.1 has been released. This update fixes a usability issue in manual diffraction centering.</p>

<ul><li>Only allow the characters "a-zA-Z_.-" in manual diffraction center "raster images folder" path elements. This avoids cryptic diffraction center errors caused by the inability of the Dectris Pilatus camserver software to handle paths containing certain characters (e.g. the space character). (The set of characters the camserver software can handle is undocumented.)</li>
</ul>]]></description>
      <pubDate>Tue, 27 Oct 2015 16:55:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost48-JDirector-2-2-1_imca43-1-released</link>
      <guid>https://imca-cat.org/blogpost48-JDirector-2-2-1_imca43-1-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Aaproc 0.4.0 released</title>
      <description><![CDATA[<p>Aaproc 0.4.0 has been released. This update includes the following changes:</p>

<ul><li>Add NumThreadsPerProcessJob configuration option to control the number of threads to use per dataset processing job. This enables more efficient use of the available computing resources.</li>
	<li>Add "autoPROC_CreateGpxPictures=no" to the autoPROC "process" invocation. This keeps processing fast even if autoPROC supports and defaults to the creation of pictures of diffraction and predictions.</li>
</ul>]]></description>
      <pubDate>Thu, 22 Oct 2015 21:14:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost47-Aaproc-0-4-0-released</link>
      <guid>https://imca-cat.org/blogpost47-Aaproc-0-4-0-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca42 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca42 has been released. This update adds support for auto-mode diffraction-center polygon-shaped rasters.</p>

<ul><li>Added support for a polygon raster shape (instead of only a rectangular shape) in auto-mode diffraction centering. This makes diffraction centering faster by skipping raster cells that lie outside the crystal loop and hence do not need to be scanned.</li>
</ul>]]></description>
      <pubDate>Thu, 09 Jul 2015 21:53:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost46-JDirector-2-2-1_imca42-released</link>
      <guid>https://imca-cat.org/blogpost46-JDirector-2-2-1_imca42-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca41 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca41 has been released.  This update adds support for entering X-ray beam attenuation as transmission and other improvements.
</p>

<ul><li> Added support for entering X-ray beam transmission instead of attenuation for users who would prefer to think in terms of transmission.  This applies to the scan editor, the manual diffraction centering configuration, and the job sample table.
</li><li> Fixed the job sample table to use correct detector distance limits.  Previously, the limits were hard-coded which was wrong.  Now the limits are obtained from the instrument server.
</li><li> Improved log messages.  This involved fixing a case where an undefined value was printed as null, where extraneous trailing punctuation was used, and where an exception trace was unnecessarily printed for a diffraction center that terminated due to a low-score cutoff.</li></ul>]]></description>
      <pubDate>Thu, 07 May 2015 16:48:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost45-JDirector-2-2-1_imca41-released</link>
      <guid>https://imca-cat.org/blogpost45-JDirector-2-2-1_imca41-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca36 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca36 has been released.  This update adds support for saving ancillary files with data in auto-mode and other improvements.
</p>

<ul><li> In auto-mode, instead of saving camera snapshots from the centering and before and after steps directly in the sample directory, they are now saved in a "camera" subdirectory.  This makes the sample directory less cluttered and more uniform.
</li><li> Added support for saving ancillary files ("camera", "diff-center", etc.) with the data in auto-mode.  This behavior is off by default but can be enabled via an option in the Job Control options pane.  This is useful for mail-in when collecting for more than one user and want the ancillary files to be saved with the data.  In this mode of operation, the recipe usually contains a path not relative to the sample image directory (i.e. user-defined absolute path or relative to the working directory) and using escape characters.  This can also be used if a user wants to collect their data to a different location than the default one produced by auto-mode.
</li><li> In auto-mode, for the ancillary "camera" and "diff-center" subdirectories, if they already exist, they will now be renamed out of the way first.  They are renamed to a name ending in ".old" or ".old<strong><em>N</em></strong>" where <strong><em>N</em></strong> is an integer &gt;= 2.  This makes the latest camera and diffraction center images always appear in the "camera" and "diff-center" subdirectories.  The previous behavior for "camera" was to just overwrite the images.  (The "camera" subdirectory did not exist previously; it is new in this release.)  The previous behavior for "diff-center" was to create a new "diff-center<strong><em>N</em></strong>" directory where <strong><em>N</em></strong> was an integer &gt;= 2 if "diff-center" already existed.  With that approach, the path to the latest diffraction center images was not stable.
</li><li> Disabled mediaLib in order to prevent the message "Could not load mediaLib accelerator wrapper classes. Continuing in pure Java mode." from being written to the standard error stream the first time one did something involving reading an X-ray diffraction image (e.g. loading an image into the Image Viewer view).</li></ul>]]></description>
      <pubDate>Fri, 03 Oct 2014 15:48:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost44-JDirector-2-2-1_imca36-released</link>
      <guid>https://imca-cat.org/blogpost44-JDirector-2-2-1_imca36-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Aaproc 0.1.1 released</title>
      <description><![CDATA[<p>Aaproc 0.1.1 has been released.  This update ensures that a log of the autoPROC <code>process</code> program's output to the standard output stream is captured in a log file.
</p>

<ul><li> Fixed an issue where the log file of the autoPROC <code>process</code> program's output to its standard output stream was not being saved.  When invoked in a terminal, <code>process</code> creates a log file (e.g. <code>process.20140910_131055.log</code>) of what it writes to its standard output stream.  But when invoked as a subprocess of the <code>aap</code> program, it does not create this log file.  Now <code>aap</code> creates this log file <em>for</em> <code>process</code> to achieve the expected behavior.</li></ul>]]></description>
      <pubDate>Wed, 10 Sep 2014 18:31:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost43-Aaproc-0-1-1-released</link>
      <guid>https://imca-cat.org/blogpost43-Aaproc-0-1-1-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Aaproc 0.1.0 released</title>
      <description><![CDATA[<p>Aaproc 0.1.0 has been released.  This is the first release made available to all users.
</p>

<p>Aaproc (<strong>A</strong>uto <strong>A</strong>uto-<strong>Proc</strong>ess) is a suite of programs for automatically auto-processing X-ray crystallography datasets.  It includes a program, <code>aap</code>, for finding datasets on the file system and auto-processing them using external programs (e.g. autoPROC).  The <code>aap</code> program writes a summary of dataset processing to a file named <code>aap-result.html</code> in the current working directory.
</p>

<p>Aaproc is installed on the processing server (i.e. plankton).  If we typically want to auto-process every dataset as it is collected at IMCA-CAT, Aaproc might be useful to us.  An easy way to use it is to collect all datasets to their own directories somewhere below a particular directory tree.  Let's say we collect all datasets under <code>/depot17id/luke/20140725</code>.  Now simply do the following at a command shell:
</p>

<p><code>$ <strong>cd /depot17id/luke/20140725</strong></code>
<code>$ <strong>aap</strong></code>
</p>

<p>The <code>aap</code> program will run indefinitely, detecting datasets as they are collected, will attempt to auto-process the datasets using autoPROC, and will write a processing summary to <code>/depot17id/luke/20140725/aap-result.html</code> as it goes.  This will work equally well for data collected in manual or auto mode.
</p>

<p>Documentation is available in the form of Unix manual pages.  We can view the <code>aap</code> program manual by typing the following at a shell:
</p>

<p><code>$ <strong>man aap</strong></code>
</p>

<p>Similarly, we can view the <code>aaproc.conf</code> configuration file manual by typing the following at a shell:
</p>

<p><code>$ <strong>man aaproc.conf</strong></code></p>
]]></description>
      <pubDate>Fri, 25 Jul 2014 19:09:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost42-Aaproc-0-1-0-released</link>
      <guid>https://imca-cat.org/blogpost42-Aaproc-0-1-0-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca35 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca35 has been released.  This update fixes a bug in auto-mode abort handling and improves the speed and quality of auto-mode diffraction centering.
</p>

<ul><li> Fixed a bug in auto-mode where pressing the Abort button at the bottom right of the JDirector window would not abort the currently running auto-mode jobs.
</li><li> Reclassified some auto-mode diffraction center log errors as warnings so that an error dialog is not displayed.  The most common case where this is helpful is when an auto-mode diffraction center fails because the minimum score threshold is not achieved.  Instead of an error dialog popping up, the error will just appear in the sample's status field.
</li><li> Reduced width of second diffraction center raster from three cells to one cell.  This will avoid the possibility of the second raster walking away from the optimal Z center found by the first raster, and it will speed up diffraction centering on average because it will now rasterize just one column of cells as opposed to the usual three.</li></ul>]]></description>
      <pubDate>Thu, 17 Jul 2014 21:15:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost41-JDirector-2-2-1_imca35-released</link>
      <guid>https://imca-cat.org/blogpost41-JDirector-2-2-1_imca35-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>detector distance error</title>
      <description><![CDATA[<p>on 17 July we noticed that the detector distance is refining 20mm further than the distance set in the image header. There was a control system problem on 16 July that likely caused this problem.
</p>

<p>This has been resolved and the correct distance should now be written to the image header.
</p>

<p>If you have any questions or concerns about this, please contact the staff.</p>
]]></description>
      <pubDate>Thu, 17 Jul 2014 17:34:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost40-detector-distance-error</link>
      <guid>https://imca-cat.org/blogpost40-detector-distance-error</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>IMCA-CAT Support E-mail address</title>
      <description><![CDATA[<p>In the interest of improving communication between support staff and users, we have a new e-mail address that will go to all the IMCA-CAT support staff.
</p>

<p>Please use ONE of the following addresses:
</p>

<p><a class="convert-mailto" href="mailto:nospam@example.com" data-encode-name="support" data-encode-domain="imca.aps.anl.gov">support at imca.aps.anl.gov</a>
</p>

<p>or...
</p>

<p><a class="convert-mailto" href="mailto:nospam@example.com" data-encode-name="imca-support" data-encode-domain="anl.gov">imca-support at anl.gov</a></p>
]]></description>
      <pubDate>Fri, 27 Jun 2014 14:10:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost39-IMCA-CAT-Support-E-mail-address</link>
      <guid>https://imca-cat.org/blogpost39-IMCA-CAT-Support-E-mail-address</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca31 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca31 has been released.  This update fixes a bug in auto mode diffraction centering and improves auto mode diffraction centering.
</p>

<ul><li> Fixed a bug in auto mode diffraction centering where it would abort after running for exactly 10 minutes even if it had already finished diffraction centering and was just finishing synchronizing the XYZ stage and Phi axis positions.
</li><li> For auto mode diffraction centering, a loop-find will now always be executed even if the "use stored center" option is checked.
</li><li> For auto mode diffraction centering, reduce the maximum raster size from 50x50 cells to a smaller staff-configured size.  This aims to avoid really big rasters that take a long time to scan.</li></ul>]]></description>
      <pubDate>Tue, 15 Apr 2014 19:16:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost38-JDirector-2-2-1_imca31-released</link>
      <guid>https://imca-cat.org/blogpost38-JDirector-2-2-1_imca31-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca30.1 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca30.1 has been released.  This update fixes a bug in the image viewer.
</p>

<ul><li> Fixed a bug in the image viewer that could lead to excessive CPU utilization and a freeze when inverting the color of an image multiple times from the Contrast Adjustment tool.</li></ul>]]></description>
      <pubDate>Tue, 25 Mar 2014 14:49:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost37-JDirector-2-2-1_imca30-1-released</link>
      <guid>https://imca-cat.org/blogpost37-JDirector-2-2-1_imca30-1-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca29 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca29 has been released.  This update adds support for assigning a username to a puck.
</p>

<ul><li> Added support for assigning a username to a puck and for a corresponding '%u' substitution character expansion in scan template paths and manual diffraction centering paths.  (This is useful for staff for mail-in data collection.)</li></ul>]]></description>
      <pubDate>Wed, 12 Mar 2014 15:13:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost36-JDirector-2-2-1_imca29-released</link>
      <guid>https://imca-cat.org/blogpost36-JDirector-2-2-1_imca29-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Monochrometer Maintenance Completed</title>
      <description><![CDATA[On Feb 24th maintenance was initiated on the 17ID mono-chrometer. Plastic tubing that supplies water to the second crystal and shielding inside the mono-chrometer was replaced with metal hoses. This was done to prevent the possibility of a water leak due to radiation damage to the plastic hose as has happened with other Bruker mono-chrometers like the one installed on 17ID. The hose that was replaced was not in a location that could easily be replaced and required opening the mono-chrometer to change. At this time Bruker also fixed a faulty limit switch on the second crystal roll motion that had been broken for some time. The ion pump (vacuum pump) installed on the mono-chrometer was also replaced as it had begun showing signs of decreased performance. The work was completed without issue and the beam-line was returned to service on Feb 25th. This work was scheduled to coincide with a two day machine studies and at a time when it was possible for Bruker to be on site to also do commissioning work on 17ID.]]></description>
      <pubDate>Wed, 26 Feb 2014 17:40:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost35-Monochrometer-Maintenance-Completed</link>
      <guid>https://imca-cat.org/blogpost35-Monochrometer-Maintenance-Completed</guid>
      <author>zoellner</author>
      <dc:creator>zoellner</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca28 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca28 has been released.  This update adds support for a staff-configured auto mode diffraction center best-score cutoff.
</p>

<ul><li> Added support for a staff-configured auto mode diffraction center best-score cutoff.  Now, if the best score of a diffraction raster is less than or equal to the cutoff, diffraction centering will abort, and the sample will be skipped.  This makes the system more intelligent by not fully rasterizing and collecting data on a sample where there appears to be nothing there.</li></ul>]]></description>
      <pubDate>Thu, 20 Feb 2014 19:08:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost34-JDirector-2-2-1_imca28-released</link>
      <guid>https://imca-cat.org/blogpost34-JDirector-2-2-1_imca28-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca27 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca27 has been released.  This update adds support for inverse wedge scans as well as other improvements.
</p>

<ul><li> Added support for inverse wedge scans.  Now, if you want to perform an inverse wedge scan, just check the "Scan in inverse wedge mode" checkbox in the scan editor.  And yes, you can even do an inverse wedge scan along a vector.
</li><li> Improved internal physics constants (e.g. constants used to convert between eV and angstroms) by updating to 2010 CODATA values.
</li><li> Fixed a bug in the handling of image-taken notifications when the image file name does not match the scan template.  Previously, the task that handled the image-taken notifications would exit in this case, meaning future image-taken notifications for future scans would not work.  Now, an error will be generated, but future image-taken notifications for future scans will continue to work.
</li><li> Fixed a bug in the configuration file editor that prevented it from displaying an error dialog to the user in the case where the user does not have sufficient privileges to edit a configuration file.</li></ul>]]></description>
      <pubDate>Wed, 12 Feb 2014 16:57:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost33-JDirector-2-2-1_imca27-released</link>
      <guid>https://imca-cat.org/blogpost33-JDirector-2-2-1_imca27-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca26.2 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca26.2 has been released. This update fixes two bugs related to using Rigaku and UniPuck dewar plates simultaneously.
</p>

<ul><li> Fixed bug where the per-dewar "number of positions in a magazine" configuration file parameters were being ignored if the first per-dewar "number of magazines" configuration file parameter (i.e. for dewar 1) was not present.
</li><li> Fixed bug where an invalid dewar position error would occur when editing the inventory when dewar 1 has a Rigaku plate, dewar 2 has a UniPuck plate, and overriding the mounted sample to be a high magazine position from dewar 2 that does not exist in a Rigaku magazine (e.g. 16).</li></ul>]]></description>
      <pubDate>Tue, 10 Dec 2013 18:53:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost32-JDirector-2-2-1_imca26-2-released</link>
      <guid>https://imca-cat.org/blogpost32-JDirector-2-2-1_imca26-2-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca26.1 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca26.1 has been released. This update fixes two bugs.
</p>

<ul><li> Fixed bug where pressing Reset button more than once after pressing Abort button would result in JDirector indicating it was "busy" (i.e. spinning Rigaku logo) indefinitely with no way to stop it.
</li><li> Fixed bug where no useful error message was provided for CameraMan robot error codes 91-98.</li></ul>]]></description>
      <pubDate>Wed, 27 Nov 2013 23:33:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost31-JDirector-2-2-1_imca26-1-released</link>
      <guid>https://imca-cat.org/blogpost31-JDirector-2-2-1_imca26-1-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Beam alignment</title>
      <description><![CDATA[<p>The APS changed to a reduced horizontal beam lattice configuration Nov 13. During beamline setup on Nov 13, it was noted that the quality of the focused beam had degraded, flux was decreased and that the storage ring beam delivery angles had changed.
</p>

<p>After consultation, on the morning of Nov 14, staff requested the APS to re-optimize storage ring steering at our sector. This has appeared to restore the beam focus and intensity.
</p>

<p>If there are any questions or concerns about this, or if the users on Nov 13 have noticed problems with data, please contact the staff.</p>
]]></description>
      <pubDate>Thu, 14 Nov 2013 17:58:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost30-Beam-alignment</link>
      <guid>https://imca-cat.org/blogpost30-Beam-alignment</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca26 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca26 has been released. This update adds an auto mode diffraction centering speed optimization.
</p>

<ul><li> Made auto mode diffraction centering faster on average by rasterizing the smaller plane first.</li></ul>]]></description>
      <pubDate>Wed, 13 Nov 2013 16:30:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost29-JDirector-2-2-1_imca26-released</link>
      <guid>https://imca-cat.org/blogpost29-JDirector-2-2-1_imca26-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca25.5 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca25.5 has been released. This update adds support for a system defined diffraction center high resolution cutoff in auto mode.
</p>

<ul><li> Added support for specifying the auto mode diffraction center high resolution cutoff (i.e. the high resolution cutoff to be used for diffraction centering in auto mode) in a JDirector configuration file.</li></ul>]]></description>
      <pubDate>Wed, 13 Nov 2013 16:23:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost28-JDirector-2-2-1_imca25-5-released</link>
      <guid>https://imca-cat.org/blogpost28-JDirector-2-2-1_imca25-5-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca25.4 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca25.4 has been released. This update fixes a bug in the crystal view where a raster region resize handle would not resize the region correctly.
</p>

<ul><li> Fixed bug where for certain resizes at certain zooms, the region would incorrectly snap to a zero width or height. For example, at a zoom of 5, resizing a region of one column and multiple rows by dragging down on the bottom edge handle resulted in the region snapping to a width of zero.</li></ul>]]></description>
      <pubDate>Wed, 13 Nov 2013 16:18:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost27-JDirector-2-2-1_imca25-4-released</link>
      <guid>https://imca-cat.org/blogpost27-JDirector-2-2-1_imca25-4-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca25.2 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca25.2 has been released. This update fixes a bug that prevented a mark from being set in the crystal view under certain conditions.
</p>

<ul><li> Fixed bug where if opened the diffraction center dialog, drew a region, and then closed the dialog (thus making the region disappear), clicking where the region was did not result in a mark being set.</li></ul>]]></description>
      <pubDate>Wed, 13 Nov 2013 16:11:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost26-JDirector-2-2-1_imca25-2-released</link>
      <guid>https://imca-cat.org/blogpost26-JDirector-2-2-1_imca25-2-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Base specifications and recommendations</title>
      <description><![CDATA[<p>During October there have been three episodes of pins being stuck in pucks where the robot pulled the puck off the dewar base plate. We believe this is due to the base being out of specification and becoming stuck on the puck magnet.
</p>

<p>The Hampton HT bases with the painted bar code and ALS-style bases appear to be made too small to reliably fit in the ACTOR pucks. These two base styles were responsible for two of the robot accidents this month.
</p>

<p>We have sizing pins that we will distribute to check the size of the bases.
</p>

<p>The following bases have shown to be problematic:
</p>

<p>Hampton CrystalCap HT or Copper HT w/2D code (HR8-1*)
Hampton CrystalCap Magnetic ALS (HR4-779)
Hampton CrystalCap Copper Magnetic ALS
Any other Hampton base with a painted bar code.
</p>



<p>The following bases are recommended:
</p>

<p>MiTeGen: any base
Molecular Dimensions: any base
Hampton: CrystalCap Magnetic (HR4-731, HR4-733, HR4-902)
Hampton: CrystalCap Copper Magnetic
Hampton: CrystalCap HT, no 2D code (HR8-094)
Any base made to the SPINE specification.
</p>



<ol><ol><ol><ol><ol><ol><ol><li> UPDATE: 20 Nov 2013 #######
</li></ol></ol></ol></ol></ol></ol></ol>
<p>MiTeGen supplied us with 500 of their bases to test (100 of each style) and all of them passed the gauge pin test. While this is a rather small sample, we are reasonably confident that their bases will work and can recommend them for use with the ACTOR pucks.</p>
]]></description>
      <pubDate>Tue, 29 Oct 2013 17:57:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost25-Base-specifications-and-recommendations</link>
      <guid>https://imca-cat.org/blogpost25-Base-specifications-and-recommendations</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>End effector repair complete</title>
      <description><![CDATA[The ACTOR robot end effector has been repaired and is expected to be delivered to the beam line tomorrow (Oct 17) morning.  Once the end effector is reinstalled and tested we will resume the original data collection schedule with remote users tomorrow.]]></description>
      <pubDate>Wed, 16 Oct 2013 20:29:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost24-End-effector-repair-complete</link>
      <guid>https://imca-cat.org/blogpost24-End-effector-repair-complete</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Robot end effector damaged</title>
      <description><![CDATA[The robot end effector was damaged in a collision caused by a pin stuck in a magazine.  The end effector has been returned for repair and a loaner is not currently available from Rigaku.  Automated sample mounting is not available until we receive a loaner or our repaired unit, possibly by the beginning of next week.]]></description>
      <pubDate>Mon, 14 Oct 2013 23:13:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost23-Robot-end-effector-damaged</link>
      <guid>https://imca-cat.org/blogpost23-Robot-end-effector-damaged</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Sample Dewar #1 back in service</title>
      <description><![CDATA[The dewar lid for Sample Dewar #1 is fixed and all three dewars are in service. -EZ]]></description>
      <pubDate>Fri, 11 Oct 2013 13:58:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost22-Sample-Dewar-1-back-in-service</link>
      <guid>https://imca-cat.org/blogpost22-Sample-Dewar-1-back-in-service</guid>
      <author>zoellner</author>
      <dc:creator>zoellner</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca25 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca25 has been released.  This update adds support for scan vector visualization as well as other improvements.
</p>

<ul><li> Added support for scan vector visualization in the crystal view.  Now, if you've defined a vector in a scan in the Image Collection view, you can see a graphical overlay of that vector in the crystal view.
</li><li> Improved scan vector definition workflow.  Made vector start and end point text fields in Image Collection view scan editor uneditable.  On sample dismount, all vector start and end points defined in Image Collection view scans are deleted automatically.  This avoids keeping meaningless vector definitions around, and it makes it less confusing to define a new vector on a subsequent sample.
</li><li> Improved auto mode job handling of a sample with a missing pin.  Rather than stopping the job, JDirector now skips the sample with the missing pin and continues on to the next sample.
</li><li> Improved manual centering by clearing the mark on the crystal view after performing a manual center.  Previously, after moving to the new center position and refreshing the crystal view, the mark was still displayed in the crystal view but at the old position.  We considered this to be confusing.  Now, the mark is cleared after performing the manual center.
</li><li> Fixed a bug where commanding an aperture retract from the crystal view could cause the UI to become unresponsive.
</li><li> Fixed a bug where commanding a backlight insert or retract from the crystal view could cause the UI to become unresponsive.
</li><li> Improved inserting and retracting the backlight from the crystal view by refreshing the camera image after every backlight insert and retract command regardless of whether JDirector thinks the backlight position has changed.
</li><li> Fixed a bug in manual diffraction center visualization where the diffraction center overlays on the crystal view were not being hidden when the diffraction center dialog was closed.
</li><li> Fixed a bug in the manual diffraction center dialog where the size of the dialog was reset every time it was closed and opened again.
</li><li> Improved the Clear Marks button on the crystal view so that it will clear the loop outline from an auto center.</li></ul>]]></description>
      <pubDate>Thu, 10 Oct 2013 22:49:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost21-JDirector-2-2-1_imca25-released</link>
      <guid>https://imca-cat.org/blogpost21-JDirector-2-2-1_imca25-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Sample Dewar #1 out of service</title>
      <description><![CDATA[The lid for sample dewar #1 stopped heating and was taken out of service. Troubleshooting discovered a bad thermocouple in the lid. There are two thermocouples installed as redundancy but the good one was apparently not making contact to the connector. The connector has been fixed so that the good thermocouple is working. Lid will be tested when time allows. Replacement of the bad thermocouple in the lid assembly will have to be done by Rigaku when time allows. - EZ]]></description>
      <pubDate>Thu, 10 Oct 2013 19:03:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost20-Sample-Dewar-1-out-of-service</link>
      <guid>https://imca-cat.org/blogpost20-Sample-Dewar-1-out-of-service</guid>
      <author>zoellner</author>
      <dc:creator>zoellner</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>5 micron aperture assembly current default</title>
      <description><![CDATA[The 5 micron aperture assembly (50, 20, 10, 5um) is currently the default at 17ID due to problems with the 20um setting on the other assembly (300, 50, 20, 10).  Full beam can still be used by selecting 'none' for aperture size.]]></description>
      <pubDate>Thu, 10 Oct 2013 12:04:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost19-5-micron-aperture-assembly-current-default</link>
      <guid>https://imca-cat.org/blogpost19-5-micron-aperture-assembly-current-default</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Imcadr 0.25.4 released</title>
      <description><![CDATA[<p>Imcadr 0.25.4 has been released. This update fixes a bug in Labelit scoring.
</p>

<ul><li> When performing diffraction center scoring with Labelit, changed to compute the score as a function of the good Bragg candidates total.  This fixes a bug introduced in version 0.18.0 (released in March 2013) where the score was computed as a function of the spot total when it should have been computed as a function of the good Bragg candidates total.  JDirector uses Imcadr for diffraction centering, so this bug has existed in JDirector since March as well and is now fixed.</li></ul>]]></description>
      <pubDate>Tue, 13 Aug 2013 16:52:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost18-Imcadr-0-25-4-released</link>
      <guid>https://imca-cat.org/blogpost18-Imcadr-0-25-4-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca23 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca23 has been released. This update improves the reliability of auto mode diffraction centering when run in a NoMachine NX session.
</p>

<ul><li> Increased the auto mode diffraction center step XYZ stage initialize timeout from 10 seconds to 3 minutes to ensure it won't bogusly time out during an inopportune NoMachine NX session disconnect or connect.</li></ul>]]></description>
      <pubDate>Wed, 07 Aug 2013 17:47:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost17-JDirector-2-2-1_imca23-released</link>
      <guid>https://imca-cat.org/blogpost17-JDirector-2-2-1_imca23-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca22 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca22 has been released. This update adds support for path expansion in the diffraction center dialog.
</p>

<ul><li> Added an expansion of the raster images folder path in the diffraction center dialog to make it easy to see what the path will expand to.  This also makes it consistent with the scan template expansion in the scan editor.</li></ul>]]></description>
      <pubDate>Fri, 12 Jul 2013 14:05:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost16-JDirector-2-2-1_imca22-released</link>
      <guid>https://imca-cat.org/blogpost16-JDirector-2-2-1_imca22-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca21 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca21 has been released. This update adds support for vector data collection as well as other improvements.
</p>

<ul><li> Made Phi jog control display the position and jog magnitude with a number of decimal places appropriate for the precision of the Phi axis.
</li><li> Added a no-spaces-in-path validation rule for scan templates.
</li><li> Improved robot error messages.
</li><li> Improved communication with the diffraction center subprocess when it first starts up ensuring it has enough time to start up before needing to respond to commands.
</li><li> Improved how the diffraction center dialog is opened and closed to try to avoid a difficult to reproduce system resource leak.
</li><li> Added support for vector data collection (a.k.a. collect along a vector).
</li><li> Improved scan validation error messages.
</li><li> Made the scan template of recipe editor scans default to the sample image directory.
</li><li> Fixed a stack overflow error when saving or restoring a schedule.
</li><li> Added support for the PILATUS_1.2 CBF image header format.
</li><li> Fixed the scan exposure time validator to not allow negative exposure times.
</li><li> Improved the scan editor to align controls better and be easier to read and navigate.
</li><li> Added an expansion of the scan template below the scan template in the scan editor to make it easy to see what the scan template will expand to.</li></ul>]]></description>
      <pubDate>Tue, 09 Jul 2013 22:55:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost15-JDirector-2-2-1_imca21-released</link>
      <guid>https://imca-cat.org/blogpost15-JDirector-2-2-1_imca21-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Modified 5 micron Pinhole Assembly Available for Use</title>
      <description><![CDATA[The 5 micron mini-quad collimator assembly has been modified to replace the 300 micron scatter guard with a 50 micron beam-defining pinhole and is available for use.  The new suite of pinhole sizes in this assembly is 50, 20, 10 and 5 microns.  At this time the default assembly will be the 300, 50, 20, 10 micron pinhole set.  Please notify staff prior to your experiment if you prefer to use the 5 micron set so that we can make the switch at start-up.]]></description>
      <pubDate>Tue, 02 Jul 2013 16:22:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost14-Modified-5-micron-Pinhole-Assembly-Available-for-Use</link>
      <guid>https://imca-cat.org/blogpost14-Modified-5-micron-Pinhole-Assembly-Available-for-Use</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Sample Dewar #2 back in service</title>
      <description><![CDATA[All three sample dewars are now available for use.]]></description>
      <pubDate>Wed, 05 Jun 2013 19:01:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost13-Sample-Dewar-2-back-in-service</link>
      <guid>https://imca-cat.org/blogpost13-Sample-Dewar-2-back-in-service</guid>
      <author>zoellner</author>
      <dc:creator>zoellner</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Sample Dewar #2 out of service</title>
      <description><![CDATA[Sample Dewar #2 has a broken sensor and is unavailable until it is replaced. The sensor is a switch that tells the robot that the plug for the lid is in the proper position. Hopefully this will be resolved Tuesday during this weeks maintenance day.]]></description>
      <pubDate>Mon, 03 Jun 2013 16:43:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost12-Sample-Dewar-2-out-of-service</link>
      <guid>https://imca-cat.org/blogpost12-Sample-Dewar-2-out-of-service</guid>
      <author>zoellner</author>
      <dc:creator>zoellner</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca18 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca18 has been released.  This update includes several stability fixes as well as other improvements.
</p>

<ul><li> Made manual diffraction centering stop if the subprocess exits or hangs.
</li><li> Made manual diffraction centering responsive to being stopped in more situations, and improved how it stops the subprocess to decrease the chance of leaving the beamline in an inconsistent state.
</li><li> Improved how the diffraction center step in auto mode executes the diffraction centering subprocess, and added capturing of the standard error output of the subprocess if a failure occurred.
</li><li> Made the diffraction center step in auto mode interruptible.  Previously, no steps were interruptible; a job could only be stopped after a step completed.  Now a job can be stopped in the middle of a diffraction center step.  This is helpful if a diffraction center step hangs.  (Of course this should never happen, but if it does, at least now there is a good way to stop it.)</li></ul>]]></description>
      <pubDate>Wed, 24 Apr 2013 22:37:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost11-JDirector-2-2-1_imca18-released</link>
      <guid>https://imca-cat.org/blogpost11-JDirector-2-2-1_imca18-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>End effector damaged</title>
      <description><![CDATA[Today there was a collision that damaged the ACTOR end effector.  We have been in touch with Rigaku and they are sending the loaner end effector Monday.  We expect auto-mounting to be fully operational again in time for scheduled data collections on Wednesday.]]></description>
      <pubDate>Sat, 30 Mar 2013 14:38:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost10-End-effector-damaged</link>
      <guid>https://imca-cat.org/blogpost10-End-effector-damaged</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector 2.2.1_imca17 released</title>
      <description><![CDATA[<p>JDirector 2.2.1_imca17 has been released.  This update introduces advanced diffraction centering features as well as other improvements.
</p>

<ul><li> Added diffraction center support for choosing the analysis package (e.g. LABELIT or d*TREK) used for analyzing (including scoring) diffraction center images.
</li><li> Added diffraction center support for configuring the following analysis parameters: high and low resolution cutoff, minimum spot area, and minimum signal height.
</li><li> Made diffraction center raster cells selectable on the result view, and added a detail view showing analysis properties (e.g. spot total, good Bragg candidate total, etc.) for the selected cell.
</li><li> Added diffraction center raster result analysis property drop-down enabling selection of what property is displayed in the raster result view.  Previously, a score was displayed.  Now the displayed value can be the score, spot total, good Bragg candidates total, or total integrated signal.  The score is not exactly the same as before.  Before, the score was a scaled score between 0 and 100, but now it is not scaled.
</li><li> Made the generated HTML result file display scores as they appear in the GUI.  That is, they are the unscaled scores as displayed in the GUI, not scaled scores between 0 and 100.
</li><li> Changed diffraction center configuration to indicate "None" for an optional value that has been unchecked rather than showing the value grayed out.  This better communicates that no value is being specified.  For example, if detector distance is unchecked, it now shows "None" for its value, indicating that the detector distance will not be moved.
</li><li> Improved diffraction center configuration descriptive text, labels, layout, and window resize behavior.
</li><li> Improved diffraction center subprocess communication when subprocess terminates prematurely.</li></ul>]]></description>
      <pubDate>Tue, 26 Mar 2013 22:07:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost9-JDirector-2-2-1_imca17-released</link>
      <guid>https://imca-cat.org/blogpost9-JDirector-2-2-1_imca17-released</guid>
      <author>jlmuir</author>
      <dc:creator>jlmuir</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>JDirector auto-contrast problem resolved</title>
      <description><![CDATA[Recent problems with auto-contrast for image viewing in JDirector were caused by a bad pixel on the Pilatus detector. This pixel, reporting a very high intensity reading, was erroneously expanding the image intensity range.  The pixel has been masked out with detector software, restoring normal auto-contrast behavior.  The pixel was located in the region of the beam stop and would not have affected any data collected.]]></description>
      <pubDate>Thu, 21 Mar 2013 23:17:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost8-JDirector-auto-contrast-problem-resolved</link>
      <guid>https://imca-cat.org/blogpost8-JDirector-auto-contrast-problem-resolved</guid>
      <author>mulichak</author>
      <dc:creator>mulichak</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>XBPM Calibration</title>
      <description><![CDATA[<p>The XBPM has been re-calibrated and positional feedback can be used.
</p>

<p>Limited testing at 94% attenuation has shown that when the beam is moved to the edge of the camera region at 5x magnification, the beam will be returned to the predefined origin.
</p>

<p>Please keep in mind that at high attenuation, the reported beam position will not be accurate and the beam may be moved away from the defined origin. This can be tested by turning off feedback, moving to the required attenuation and observing if the reported position deviates significantly from that reported with standard attenuation (94%). If this occurs, leave the positional feedback off until returning to a lower level of attenuation.
</p>

<p>If problems are noticed with beam drift or any malfunction of the positional feedback system, please notify the staff.</p>
]]></description>
      <pubDate>Sat, 23 Feb 2013 19:06:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost7-XBPM-Calibration</link>
      <guid>https://imca-cat.org/blogpost7-XBPM-Calibration</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Beam position feedback problems</title>
      <description><![CDATA[<p>The steering performed by the APS at the beginning of the run caused a somewhat significant change in the beam profile delivered by the mirrors to the sample. As the XBPM is very sensitive to the beam profile, the automated feedback has not been functional this run.
</p>

<p>Continued consultation with Instrumentation Technologies and Dectris has suggested that the profile change was enough that the XBPM needs to be re-calibrated. A quick test of this on Feb 18 showed this to be the case.
</p>

<p>Recalibration will be attempted on Feb 23, after which the beam feedback should be functional.</p>
]]></description>
      <pubDate>Fri, 22 Feb 2013 17:29:00 +0000</pubDate>
      <link>https://imca-cat.org/blogpost6-Beam-position-feedback-problems</link>
      <guid>https://imca-cat.org/blogpost6-Beam-position-feedback-problems</guid>
      <author>battaile</author>
      <dc:creator>battaile</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
  </channel>
</rss>
