<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    "simtbx" is the name we are giving to my diffraction image
    simulation codes.  You may or may not of heard of their standalone
    versions as MLFSOM, fastBragg (now nanoBragg), nonBragg and
    nearBragg.  Nick and I thought the capability of creating absolutely
    realistic diffraction data from a completely independent code base
    would be an excellent way to generate test data for cctbx, dials,
    phenix, and even third-party packages.  There is also the idea of
    fitting a simulation directly to diffraction images, which I have
    had some success doing independently, but we hope this will work
    better under cctbx.  Until recently, all this was standalone c code,
    with home pages here:<br>
    <br>
    <a class="moz-txt-link-freetext" href="http://bl831.als.lbl.gov/~jamesh/mlfsom/">http://bl831.als.lbl.gov/~jamesh/mlfsom/</a><br>
    <a class="moz-txt-link-freetext" href="http://bl831.als.lbl.gov/~jamesh/nanoBragg/">http://bl831.als.lbl.gov/~jamesh/nanoBragg/</a><br>
    <a class="moz-txt-link-freetext" href="http://bl831.als.lbl.gov/~jamesh/nearBragg/">http://bl831.als.lbl.gov/~jamesh/nearBragg/</a><br>
    <a class="moz-txt-link-freetext" href="http://bl831.als.lbl.gov/~jamesh/nonBragg/">http://bl831.als.lbl.gov/~jamesh/nonBragg/</a><br>
    <br>
    I have spent the bulk of my time for three months trying to wire
    these codes into the boost/Python framework of cctbx.  I put
    docstrings into every single one of my objects, but since I am new
    to Python I don't know where people look for documentation.<br>
    <br>
    Again, sorry this broke everything.  It's been in there since
    February and I was surprised to find that a new developer here
    couldn't access it.  This is why I've been asking so many questions
    about tests I should perform before checking things in, but
    apparently it was all for naught.<br>
    <br>
    -James<br>
    <br>
    <div class="moz-cite-prefix">On 5/3/2017 7:57 AM, Pavel Afonine
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9925f9c7-59cc-1e4f-0b19-30e4a1963ed4@lbl.gov">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Same questions here as Markus asked.. What is simtbx? First time
      hear about it. How cctbx can benefit from it?<br>
      Pavel<br>
      <br>
      <div class="moz-cite-prefix">On 5/3/17 07:53, <a
          class="moz-txt-link-abbreviated"
          href="mailto:markus.gerstel@diamond.ac.uk"
          moz-do-not-send="true">markus.gerstel@diamond.ac.uk</a> wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:415F7F573406BB498256C68158D45674671079A6@exchmbx03">
        <meta http-equiv="Content-Type" content="text/html;
          charset=utf-8">
        <meta name="Generator" content="Microsoft Word 15 (filtered
          medium)">
        <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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        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;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.m-2651995399140751371msolistparagraph, li.m-2651995399140751371msolistparagraph, div.m-2651995399140751371msolistparagraph
        {mso-style-name:m_-2651995399140751371msolistparagraph;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
        <div class="WordSection1">
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi
              Nick,<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Sorry,
              outsider perspective here. I don’t know what simtbx does
              or is supposed to do.<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">What
              is the benefit of having code in a repository that,
              according to your earlier mail, is explicitly not used in
              the project?<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Or
              more bluntly: We (and ccp4) distribute dials and, as part
              of it, the cctbx_project repository.<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Why
              should we ship dead code?<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">-Markus<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><a name="_MailEndCompose"
              moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
          <span style="mso-bookmark:_MailEndCompose"></span>
          <p class="MsoNormal"><b><span
                style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
                lang="EN-US">From:</span></b><span
              style="font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"
              lang="EN-US"> <a class="moz-txt-link-abbreviated"
                href="mailto:cctbxbb-bounces@phenix-online.org"
                moz-do-not-send="true">cctbxbb-bounces@phenix-online.org</a>
              [<a class="moz-txt-link-freetext"
                href="mailto:cctbxbb-bounces@phenix-online.org"
                moz-do-not-send="true">mailto:cctbxbb-bounces@phenix-online.org</a>]
              <b>On Behalf Of </b>Nicholas Sauter<br>
              <b>Sent:</b> 03 May 2017 15:52<br>
              <b>To:</b> cctbx mailing list <a
                class="moz-txt-link-rfc2396E"
                href="mailto:cctbxbb@phenix-online.org"
                moz-do-not-send="true">&lt;cctbxbb@phenix-online.org&gt;</a><br>
              <b>Subject:</b> Re: [cctbxbb] simtbx<o:p></o:p></span></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">Markus,<o:p></o:p></p>
            <div>
              <p class="MsoNormal"><o:p> </o:p></p>
            </div>
            <div>
              <p class="MsoNormal">We want option c.  simtbx should be
                in the cctbx_project directory.  No separate git
                repository.  We need to double check we've gotten all
                the files in cctbx_project, then remove them from the
                separate repo.  James, could you look into this?<o:p></o:p></p>
            </div>
            <div>
              <p class="MsoNormal"><o:p> </o:p></p>
            </div>
            <div>
              <p class="MsoNormal">Nick<o:p></o:p></p>
            </div>
          </div>
          <div>
            <p class="MsoNormal"><br clear="all">
              <o:p></o:p></p>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>
                          <div>
                            <p class="MsoNormal">Nicholas K. Sauter, Ph.
                              D.<br>
                              Senior Scientist, Molecular Biophysics
                              &amp; Integrated Bioimaging Division<o:p></o:p></p>
                            <div>
                              <p class="MsoNormal">Lawrence Berkeley
                                National Laboratory<br>
                                1 Cyclotron Rd., Bldg. 33R0345<br>
                                Berkeley, CA 94720<br>
                                (510) 486-5713<o:p></o:p></p>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
            <p class="MsoNormal"><o:p> </o:p></p>
            <div>
              <p class="MsoNormal">On Wed, May 3, 2017 at 7:49 AM, &lt;<a
                  href="mailto:markus.gerstel@diamond.ac.uk"
                  target="_blank" moz-do-not-send="true">markus.gerstel@diamond.ac.uk</a>&gt;
                wrote:<o:p></o:p></p>
              <blockquote style="border:none;border-left:solid #CCCCCC
                1.0pt;padding:0cm 0cm 0cm
                6.0pt;margin-left:4.8pt;margin-right:0cm">
                <div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">Hi James,</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D"> </span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">It looks that you now have
                        two separate places where simtbx code is kept.
                        One is in the simtbx repository, where you fixed
                        the sign earlier, and the other one is in the
                        cctbx repository, where you just now fixed it
                        again.</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">Simtbx repo: <a
                          href="https://github.com/dials/simtbx"
                          target="_blank" moz-do-not-send="true">https://github.com/dials/simtbx</a></span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">Simtbx folder in cctbx
                        repo: <a
                          href="https://github.com/cctbx/cctbx_project/tree/master/simtbx"
                          target="_blank" moz-do-not-send="true">
https://github.com/cctbx/cctbx_project/tree/master/simtbx</a> </span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D"> </span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">I guess suppose there are
                        three options here:</span><o:p></o:p></p>
                    <p class="m-2651995399140751371msolistparagraph"><span
                        style="color:#1F497D">a.</span><span
                        style="font-size:7.0pt;color:#1F497D">       </span><span
                        style="color:#1F497D">move simtbx into the
                        module directory, add simtbx to the bootstrap
                        script so it is initialised correctly.</span><o:p></o:p></p>
                    <p class="m-2651995399140751371msolistparagraph"><span
                        style="color:#1F497D">b.</span><span
                        style="font-size:7.0pt;color:#1F497D">       </span><span
                        style="color:#1F497D">leave simtbx inside the
                        cctbx_project directory and repository, but as
                        its own git repository (using git submodule)</span><o:p></o:p></p>
                    <p class="m-2651995399140751371msolistparagraph"><span
                        style="color:#1F497D">c.</span><span
                        style="font-size:7.0pt;color:#1F497D">       </span><span
                        style="color:#1F497D">leave simtbx inside the
                        cctbx_project directory, delete the separate git
                        repository</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D"> </span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">NB: This issue is
                        independent of resolving the dials-dependency
                        issue.</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D"> </span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                        style="color:#1F497D">-Markus</span><o:p></o:p></p>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a
                        name="m_-2651995399140751371__MailEndCompose"
                        moz-do-not-send="true"><span
                          style="color:#1F497D"> </span></a><o:p></o:p></p>
                    <div>
                      <div style="border:none;border-top:solid #E1E1E1
                        1.0pt;padding:3.0pt 0cm 0cm 0cm">
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
                              lang="EN-US">From:</span></b><span
                            lang="EN-US"> <a
                              href="mailto:cctbxbb-bounces@phenix-online.org"
                              target="_blank" moz-do-not-send="true">cctbxbb-bounces@phenix-online.org</a>
                            [mailto:<a
                              href="mailto:cctbxbb-bounces@phenix-online.org"
                              target="_blank" moz-do-not-send="true">cctbxbb-bounces@phenix-online.org</a>]
                            <b>On Behalf Of </b>James Holton<br>
                            <b>Sent:</b> 03 May 2017 15:40<br>
                            <b>To:</b> Winter, Graeme (DLSLtd,RAL,LSCI)
                            &lt;<a
                              href="mailto:Graeme.Winter@Diamond.ac.uk"
                              target="_blank" moz-do-not-send="true">Graeme.Winter@Diamond.ac.uk</a>&gt;;
                            <a href="mailto:cctbxbb@phenix-online.org"
                              target="_blank" moz-do-not-send="true">cctbxbb@phenix-online.org</a><br>
                            <b>Subject:</b> Re: [cctbxbb] simtbx</span><o:p></o:p></p>
                      </div>
                    </div>
                    <div>
                      <div>
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
                          Yesterday, Aaron and I were trying to set
                          things up so that simtbx would be available to
                          people who aren't James Holton.  It's been
                          checked in and working for over a month now,
                          and only a few days ago I discovered that a
                          fresh "bootstrap" has a broken simtbx, despite
                          my "git status" telling me all my files are up
                          to date.  I asked Aaron and Nick for help with
                          this.<br>
                          <br>
                            I thought what we did was make cctbx.xfel
                          depends on simtbx, since fitting simulations
                          to stills is the whole reason for porting my
                          stuff into python.  <br>
                          <br>
                          I set up simtbx with a constructor that takes
                          a dxtbx detector as input, but does that make
                          it depend on dials?  I did not expect that.<br>
                          <br>
                          Sorry, didn't mean to break anything!  Would
                          much appreciate any help on this. <br>
                          <br>
                          -James<o:p></o:p></p>
                        <div>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On
                            5/3/2017 1:41 AM, <a
                              href="mailto:Graeme.Winter@Diamond.ac.uk"
                              target="_blank" moz-do-not-send="true">Graeme.Winter@Diamond.ac.uk</a>
                            wrote:<o:p></o:p></p>
                        </div>
                        <blockquote
                          style="margin-top:5.0pt;margin-bottom:5.0pt">
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi
                            Folks<o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We
                            have noticed that simtbx, part of the core
                            cctbx now, depends on dials<o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                            means if you do not have a dials build your
                            cctbx will be broken<o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                            is probably not the way we want things?<o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I
                            thought simtbx was a separate repo?<o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Cheerio
                            Graeme<o:p></o:p></p>
                          <p> <o:p></o:p></p>
                          <p>-- <o:p></o:p></p>
                          <p>This e-mail and any attachments may contain
                            confidential, copyright and or privileged
                            material, and are for the use of the
                            intended addressee only. If you are not the
                            intended addressee or an authorised
                            recipient of the addressee please notify us
                            of receipt by returning the e-mail and do
                            not use, copy, retain, distribute or
                            disclose the information in or attached to
                            the e-mail.<br>
                            Any opinions expressed within this e-mail
                            are those of the individual and not
                            necessarily of Diamond Light Source Ltd. <br>
                            Diamond Light Source Ltd. cannot guarantee
                            that this e-mail or any attachments are free
                            from viruses and we cannot accept liability
                            for any damage which you may sustain as a
                            result of software viruses which may be
                            transmitted in or with the message.<br>
                            Diamond Light Source Limited (company no.
                            4375679). Registered in England and Wales
                            with its registered office at Diamond House,
                            Harwell Science and Innovation Campus,
                            Didcot, Oxfordshire, OX11 0DE, United
                            Kingdom<br>
                             <o:p></o:p></p>
                        </blockquote>
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                      </div>
                    </div>
                  </div>
                  <div>
                    <div>
                      <p> <o:p></o:p></p>
                      <p>-- <o:p></o:p></p>
                      <p>This e-mail and any attachments may contain
                        confidential, copyright and or privileged
                        material, and are for the use of the intended
                        addressee only. If you are not the intended
                        addressee or an authorised recipient of the
                        addressee please notify us of receipt by
                        returning the e-mail and do not use, copy,
                        retain, distribute or disclose the information
                        in or attached to the e-mail.<br>
                        Any opinions expressed within this e-mail are
                        those of the individual and not necessarily of
                        Diamond Light Source Ltd. <br>
                        Diamond Light Source Ltd. cannot guarantee that
                        this e-mail or any attachments are free from
                        viruses and we cannot accept liability for any
                        damage which you may sustain as a result of
                        software viruses which may be transmitted in or
                        with the message.<br>
                        Diamond Light Source Limited (company no.
                        4375679). Registered in England and Wales with
                        its registered office at Diamond House, Harwell
                        Science and Innovation Campus, Didcot,
                        Oxfordshire, OX11 0DE, United Kingdom<br>
                         <o:p></o:p></p>
                    </div>
                  </div>
                </div>
                <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
                  _______________________________________________<br>
                  cctbxbb mailing list<br>
                  <a href="mailto:cctbxbb@phenix-online.org"
                    moz-do-not-send="true">cctbxbb@phenix-online.org</a><br>
                  <a
                    href="http://phenix-online.org/mailman/listinfo/cctbxbb"
                    target="_blank" moz-do-not-send="true">http://phenix-online.org/mailman/listinfo/cctbxbb</a><o:p></o:p></p>
              </blockquote>
            </div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
cctbxbb mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cctbxbb@phenix-online.org" moz-do-not-send="true">cctbxbb@phenix-online.org</a>
<a class="moz-txt-link-freetext" href="http://phenix-online.org/mailman/listinfo/cctbxbb" moz-do-not-send="true">http://phenix-online.org/mailman/listinfo/cctbxbb</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
cctbxbb mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cctbxbb@phenix-online.org">cctbxbb@phenix-online.org</a>
<a class="moz-txt-link-freetext" href="http://phenix-online.org/mailman/listinfo/cctbxbb">http://phenix-online.org/mailman/listinfo/cctbxbb</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>