<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Centaur;
panose-1:2 3 5 4 5 2 5 2 3 4;}
@font-face
{font-family:inherit;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear Marcus,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We have a K3 on a Krios at Duke. I upgraded the GMS version to a 3.5 and recently to 3.5.1. Along with our 3.5 version upgrade, I also upgraded our SerialEM software to be
compatible. Our Duke users collect SPA data using latitude and version 3.5 had the image shift option by which we could collect many targets for each focus. Version 3.5.1 is said to have a better comma correction.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With the version upgrades as per our experience the K3 has been more stable with occasional crashes. The syncing has been much better too. We did go through all the upgrades
and don’t think skipped any. Maybe something simple like a reinstalling might help.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Nilakshee<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Centaur",serif;color:#1F497D">Nilakshee Bhattacharya, PhD<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Centaur",serif;color:#1F497D">CryoEM Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Centaur",serif;color:#1F497D">Shared Materials Instrumentation Facility (SMIF)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Centaur",serif;color:#1F497D">101 Science Dr.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Centaur",serif;color:#1F497D">Duke University, Durham, NC 27708-0271<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> 3dem <3dem-bounces@ncmir.ucsd.edu>
<b>On Behalf Of </b>Marcus FISLAGE<br>
<b>Sent:</b> Friday, April 8, 2022 8:28 AM<br>
<b>To:</b> Reinhard Rachel <Reinhard.Rachel@biologie.uni-regensburg.de>; 3dem@ncmir.ucsd.edu<br>
<b>Subject:</b> Re: [3dem] GMS3.5 shutdown experiences<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Hi Reinhard and others,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">first, please note that I upgraded from version 3.3 and skipped the 3.4. So, my reasons may not apply to you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">The reasoning for my upgrade is not because of features per se but more because of stability and constant errors from the old software/firmware combination.
The upgrade was not directly advised by David or Gatan, but also not discouraged.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">With the 3.3 version we had to regularly restart the Camera fully because of several syncing errors. The initial advise of Gatan was just to restart the
PC, but often the restart still resulted in a bad sync and bad 'health status'. This needed to be sometimes done twice or thrice in a row. A shutdown PC and restart PC was more successful but was rather annoying because somebody needs to come in to physically
push the button. But in many cases that was still not enough, and we needed to cycle the Power supply of the K3 as well, which leads to even longer delays before we could restart the data collection. (This whole issue does not exist anymore, except of this
major new type of problem)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">The other main reason was that the K3 was always rather bad at interpolating the gain reference if some images were done with a significant lower beam intensity
than the gain. This was a nuisance if we had samples where we measured in significantly different ice thicknesses. Our engineer indicated that this behavior may be improved in the latest version. (Not sure it is that much different (yet).)<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">We knew from a recent install close by here on a JEOL2100 w. SerialEM that came directly with GMS3.5 that the software itself works so I wanted to give it a try to see if it alleviates
most of my camera sync errors. But note they are just doing performance test, so they do not (yet) collect thousands of imaged per day.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">A feature that I came by that is different is that the camera uses different suggested reference intensities now as well for CDS and non-CDS mode when doing the linear reference.
In 3.3 it only distinguished in counting mode. However, this will probably not really matter.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">I of course would like to know how common this new issue is and to what extent it may be a Gatan-JEOL, Gatan-SerialEM or pure Gatan issue. My money is currently completely on the
latter option. And if my regular restart quick fix of GMS3.5 works I still majorly prefer it over my issues with GMS3.3.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Cheers<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Marcus<o:p></o:p></span></p>
</div>
<div id="Signature">
<div>
<div id="divtagdefaultwrapper">
<p><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222">______________________________________</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#ED5C57">Please note upcoming days with limited access to BECM:</span></b><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:9.5pt;font-family:inherit;color:#ED5C57">22 April - 2<sup>nd</sup> May</span></b><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222">Dr. Marcus Fislage<br>
</span><span style="font-family:"Arial",sans-serif;color:#222222"><br>
EM Manager</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#222222">BECM<br>
</span><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222">VIB-Center for Structural Biology<br>
VUB (Vrije Universiteit Brussel)<br>
Building P1T, room 0.01<br>
Pleinlaan 2<br>
1050 BRUSSELS<br>
<br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.becm.be&d=DwMFAw&c=-35OiAkTchMrZOngvJPOeA&r=L7-zyQ-04fFCMRqzLIOnx7H0exGZHwIQe_wMPuY600I&m=FkJH7Kb7Y-tEZ7ekkMmrh8yZ8Hxbwnsx8kSn21ERWeTqFtM38aWSaN2ALYOEoupW&s=8vKP9fKScNm9e7DXLPFePd98aej-ZRGSOHztOXdGcy4&e=" target="_blank"><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#1155CC">www.becm.be</span></a><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Reinhard Rachel <</span><a href="mailto:Reinhard.Rachel@biologie.uni-regensburg.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reinhard.Rachel@biologie.uni-regensburg.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Sent:</b> Friday, April 8, 2022 12:06 PM<br>
<b>To:</b> </span><a href="mailto:3dem@ncmir.ucsd.edu"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3dem@ncmir.ucsd.edu</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <</span><a href="mailto:3dem@ncmir.ucsd.edu"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3dem@ncmir.ucsd.edu</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">>;
Marcus FISLAGE <</span><a href="mailto:Marcus.Fislage@vub.be"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marcus.Fislage@vub.be</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Subject:</b> Re: GMS3.5 shutdown experiences</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">> Dear all,<br>
> <br>
> since we upgraded our Camera software from Gatan to version 3.5 (K3 camera <br>
> on JEOL CryoARM300 using SerialEM 4.0.1-4) we experienced regular full <br>
> shutdowns of the GMS software. I.e. no error message and the whole software<br>
<br>
> package is just not running anymore. And a simple reopening of the GMS3 <br>
> software works and I can continue the data collection.<br>
> I am already in contact with our Gatan engineer, but he is rather surprised<br>
<br>
> about this behavior.<br>
> <br>
> I would therefore like to ask the crowd if you have had or currently have a<br>
<br>
> similar experience.<br>
> <br>
> To the best of my knowledge, it appears that the frequency of GMS shutdown <br>
> is correlated to the number of images taken. I.e. After a certain threshold<br>
<br>
> of images taken with the K3 camera, the GMS software will just disappear.<br>
> I currently tested it by a daily (or every second day) restart of the GMS <br>
> software and since then the error did not appear again for 2 weeks. This <br>
> would initially support my theory.<br>
<br>
valuable to know, Marcus. <br>
question back to you: <br>
is there any good reason to upgrade GMS to 3.5?<br>
any interesting features I am not aware of? <br>
is this version "better" in any aspect? <br>
or just recommended by -a- Gatan, or by -b- David M? <br>
thank you and kind regards,<br>
Reinhard<br>
<br>
<br>
-- <br>
Prof. Dr. Reinhard Rachel<br>
University of Regensburg<br>
Centre for EM / Anatomy<br>
Faculty of Biology & Preclin. Med.<br>
Universitaetsstrasse 31<br>
D-93053 Regensburg - Germany<br>
tel +49 941 943 -2837, -1666<br>
mail </span><a href="mailto:reinhard.rachel@biologie.uni-regensburg.de"><span style="font-size:11.0pt">reinhard.rachel@biologie.uni-regensburg.de</span></a><span style="font-size:11.0pt"><br>
office: VKL 3.1.29 <br>
member of the IFSM board<br>
<br>
Next microscopy conferences:<br>
- MC2023, DGE: 26.2.-2.3. 2023<br>
- next European EM conf.: EMC2024 in Kopenhagen, August 2024<br>
- IMC20 in Busan, South Korea: Sept, 2023<br>
- next Microbiol. conferences: VAAM 26.2.-1.3. 2023 - Göttingen <o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>