<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Magali,<br>
      <br>
      These are all good points but I did want to correct the point that
      there are no known published work using coupled codes with
      CitcomS. We had three papers, a plume study and two subduction
      studies:<br>
      <br>
      <a class="moz-txt-link-freetext" href="http://www.gps.caltech.edu/~gurnis/Papers/2006_Tan_etal_G3.pdf">http://www.gps.caltech.edu/~gurnis/Papers/2006_Tan_etal_G3.pdf</a><br>
      <br>
<a class="moz-txt-link-freetext" href="http://www.gps.caltech.edu/~gurnis/Papers/2011_DiCaprio_etal_Lithosphere.pdf">http://www.gps.caltech.edu/~gurnis/Papers/2011_DiCaprio_etal_Lithosphere.pdf</a><br>
      <br>
<a class="moz-txt-link-freetext" href="http://www.gps.caltech.edu/~gurnis/Papers/2011_Matthews_etal_GondRes.pdf">http://www.gps.caltech.edu/~gurnis/Papers/2011_Matthews_etal_GondRes.pdf</a><br>
      <br>
      We are currently not using the coupler in my group.<br>
      <br>
      Mike<br>
      <br>
      <br>
      <br>
      On 11/22/13 9:24 AM, Magali Billen wrote:<br>
    </div>
    <blockquote
      cite="mid:7064878E-47A5-400F-8457-E081658C7E7A@ucdavis.edu"
      type="cite">Thorsten and Katie bring up good points. I am more
      concerned about their being good cookbooks
      <div>available, then about coupling codes. </div>
      <div><br>
      </div>
      <div>First, there are known issue with cookbooks (some only work
         as shown with older version of CitcomS), </div>
      <div>so this would be a good opportunity to update these. I
        suggest soliciting very well documented contributions </div>
      <div>from members of this mailing list, which they use when
        starting their students on problems.</div>
      <div><br>
      </div>
      <div>Second, I don't know of any published work using coupled
        codes (please correct me if I'm wrong). While this was
        demonstrated to work for some simple models and was a heroic
        effort for those who made it work, its hard to get to work
        in practice for more complicated problems. For example, if you
        have higher resolution for a CitcomS model embedded inside a
        larger CitcomS models with lower resolution - any thermal
        boundary layer ends up creating thermal instabilities at the
        sides of the box due to the mismatch in the thickness). If
        someone is using the coupler, then we need to keep this
        capability, but if after this much time no one has used it, that
        is telling us something important.</div>
      <div><br>
      </div>
      <div>-Magali</div>
      <div><br>
      </div>
      <div>
        <div apple-content-edited="true">
        </div>
        <br>
        <div>
          <div>On Nov 21, 2013, at 9:15 PM, Catherine Cooper wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">
            <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space; ">
              <div><br>
              </div>
              <div>I am also concerned about this development.  The
                cookbooks provided with the manual will only work if the
                pyre version of CitcomS is installed.  Will there be new
                cookbooks developed?  Or will they too no longer be
                supported?  These are valuable learning tools for new
                users including graduate students.  It would be a shame
                if there were no longer educational examples for new
                users to safely learn on.</div>
              <div><br>
              </div>
              <div>Thanks,</div>
              <div><br>
              </div>
              <div>Katie</div>
              <div><br>
              </div>
              <br>
              <div apple-content-edited="true">
                <span class="Apple-style-span" style="border-collapse:
                  separate; font-family: Helvetica; font-style: normal;
                  font-variant: normal; font-weight: normal;
                  letter-spacing: normal; line-height: normal; orphans:
                  2; text-align: -webkit-auto; text-indent: 0px;
                  text-transform: none; white-space: normal; widows: 2;
                  word-spacing: 0px; -webkit-border-horizontal-spacing:
                  0px; -webkit-border-vertical-spacing: 0px;
                  -webkit-text-decorations-in-effect: none;
                  -webkit-text-size-adjust: auto;
                  -webkit-text-stroke-width: 0px; font-size: medium; ">Catherine
                  Cooper, Ph.D.<br>
                  Assistant Professor in Geophysics<br>
                  School of the Environment<br>
                  Washington State University<br>
                  (509)335-1501<br>
                  <a moz-do-not-send="true"
                    href="mailto:cmcooper@wsu.edu">cmcooper@wsu.edu</a><br>
                  <br>
                </span>
              </div>
              <br>
              <div>
                <div>On Nov 21, 2013, at 9:03 PM, Thorsten Becker wrote:</div>
                <br class="Apple-interchange-newline">
                <blockquote type="cite">
                  <meta http-equiv="Content-Type" content="text/html;
                    charset=ISO-8859-1">
                  <div dir="ltr">Hi
                    <div><br>
                    </div>
                    <div>While I am not a python/pyre user, I wonder how
                      this affects the abilities to couple regional and
                      global codes, for example? This is another
                      extension I am not using, but this always seemed
                      very helpful potentially? Wouldn't this be useful
                      to maintain?</div>
                    <div><br>
                    </div>
                    <div style="">When I compile CitcomS, I simply use
                      the --nopyre option or whatever it's called, and
                      this seems to get rid off many of the issues
                      mentioned above?<br>
                    </div>
                    <div style=""><br>
                    </div>
                    <div style=""> I can see how this must have all been
                      discussed but I am not aware of the reasoning,
                      sorry, so please excuse if these are naive
                      questions. <br>
                    </div>
                    <div style=""><br>
                    </div>
                    <div>Thanks!</div>
                    <div><br>
                    </div>
                    <div>Thorsten</div>
                    <div><br>
                    </div>
                    <div><br>
                    </div>
                  </div>
                  <div class="gmail_extra"><br clear="all">
                    <div>Thorsten W Becker - USC      </div>
                    <br>
                    <br>
                    <div class="gmail_quote">On Thu, Nov 21, 2013 at
                      12:00 PM, <span dir="ltr"><<a
                          moz-do-not-send="true"
                          href="mailto:cig-mc-request@geodynamics.org"
                          target="_blank">cig-mc-request@geodynamics.org</a>></span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        Send CIG-MC mailing list submissions to<br>
                                <a moz-do-not-send="true"
                          href="mailto:cig-mc@geodynamics.org">cig-mc@geodynamics.org</a><br>
                        <br>
                        To subscribe or unsubscribe via the World Wide
                        Web, visit<br>
                                <a moz-do-not-send="true"
                          href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc"
                          target="_blank">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a><br>
                        or, via email, send a message with subject or
                        body 'help' to<br>
                                <a moz-do-not-send="true"
                          href="mailto:cig-mc-request@geodynamics.org">cig-mc-request@geodynamics.org</a><br>
                        <br>
                        You can reach the person managing the list at<br>
                                <a moz-do-not-send="true"
                          href="mailto:cig-mc-owner@geodynamics.org">cig-mc-owner@geodynamics.org</a><br>
                        <br>
                        When replying, please edit your Subject line so
                        it is more specific<br>
                        than "Re: Contents of CIG-MC digest..."<br>
                        <br>
                        <br>
                        Today's Topics:<br>
                        <br>
                           1. CitcomS Python Removal (Eric Heien)<br>
                        <br>
                        <br>
----------------------------------------------------------------------<br>
                        <br>
                        Message: 1<br>
                        Date: Thu, 21 Nov 2013 10:47:06 -0800<br>
                        From: Eric Heien <<a moz-do-not-send="true"
                          href="mailto:emheien@ucdavis.edu">emheien@ucdavis.edu</a>><br>
                        To: <a moz-do-not-send="true"
                          href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a><br>
                        Subject: [CIG-MC] CitcomS Python Removal<br>
                        Message-ID: <<a moz-do-not-send="true"
                          href="mailto:00B7E076-EC0E-4E5B-AA20-4DADB9498AFA@ucdavis.edu">00B7E076-EC0E-4E5B-AA20-4DADB9498AFA@ucdavis.edu</a>><br>
                        Content-Type: text/plain; charset=windows-1252<br>
                        <br>
                        Hello,<br>
                        <br>
                        The CitcomS developers have recently decided to
                        remove Python and Pyre support from CitcomS.
                         There are several reasons for this:<br>
                        <br>
                        - The Python interface in CitcomS is not
                        compatible with Python 2.7 or above.  Python 2.7
                        was released in 2010, meaning most systems set
                        up in the last 3 years won?t support Python in
                        CitcomS.<br>
                        - The interface requires downloading extra
                        packages - this happens automatically but can
                        cause compilation failure on some platforms.<br>
                        - The interface opaquely assigns some parameters
                        with values not controlled by the user.<br>
                        - The Python interface adds a level of
                        complexity making it harder to debug the program
                        and understand how data structures are
                        used/modified during a run.<br>
                        - Many of the major CitcomS users do not use the
                        Python interface.<br>
                        <br>
                        We plan to remove this functionality from
                        CitcomS and provide tools to convert Python
                        based input files to the normal input file
                        format.  Relevant logic that was in the Python
                        framework will be moved into the main CitcomS
                        code.  This change will be implemented over the
                        coming year and incorporated into a future
                        CitcomS release.<br>
                        <br>
                        If you have any concerns about this decision or
                        would like to weigh in, feel free to contact me
                        or the cig-mc mailing list.<br>
                        <br>
                        Thank you,<br>
                        <br>
                        -Eric<br>
                        <br>
                        <br>
                        <br>
                        ------------------------------<br>
                        <br>
                        _______________________________________________<br>
                        CIG-MC mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a><br>
                        <a moz-do-not-send="true"
                          href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc"
                          target="_blank">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a><br>
                        <br>
                        End of CIG-MC Digest, Vol 79, Issue 1<br>
                        *************************************<br>
                        <br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                  _______________________________________________<br>
                  CIG-MC mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a><br>
                  <a moz-do-not-send="true"
                    href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a></blockquote>
              </div>
              <br>
            </div>
            _______________________________________________<br>
            CIG-MC mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a><br>
            <a class="moz-txt-link-freetext" href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a></blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
CIG-MC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a>
<a class="moz-txt-link-freetext" href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a></pre>
    </blockquote>
    <br>
  </body>
</html>