<div dir="ltr">We will definitely provide new versions of the cookbooks, and the manual will be updated with these new versions of the cookbooks. We also plan to provide a tool that would convert your existing Python-based .cfg files to the corresponding C-based versions. <div>
<br></div><div>Best,</div><div><br></div><div>Rajesh Kommu</div><div>Software Developer, CIG</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 21, 2013 at 9:15 PM, Catherine Cooper <span dir="ltr"><<a href="mailto:cmcooper@wsu.edu" target="_blank">cmcooper@wsu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><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>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Catherine Cooper, Ph.D.<br>
Assistant Professor in Geophysics<br>School of the Environment<br>Washington State University<br><a href="tel:%28509%29335-1501" value="+15093351501" target="_blank">(509)335-1501</a><br><a href="mailto:cmcooper@wsu.edu" target="_blank">cmcooper@wsu.edu</a><br>
<br></span>
</div><div><div class="h5">
<br><div><div>On Nov 21, 2013, at 9:03 PM, Thorsten Becker wrote:</div><br><blockquote type="cite"><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>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><br></div><div> 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><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 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 href="mailto:cig-mc@geodynamics.org" target="_blank">cig-mc@geodynamics.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a 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 href="mailto:cig-mc-request@geodynamics.org" target="_blank">cig-mc-request@geodynamics.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cig-mc-owner@geodynamics.org" target="_blank">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 href="mailto:emheien@ucdavis.edu" target="_blank">emheien@ucdavis.edu</a>><br>
To: <a href="mailto:CIG-MC@geodynamics.org" target="_blank">CIG-MC@geodynamics.org</a><br>
Subject: [CIG-MC] CitcomS Python Removal<br>
Message-ID: <<a href="mailto:00B7E076-EC0E-4E5B-AA20-4DADB9498AFA@ucdavis.edu" target="_blank">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 href="mailto:CIG-MC@geodynamics.org" target="_blank">CIG-MC@geodynamics.org</a><br>
<a 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 href="mailto:CIG-MC@geodynamics.org" target="_blank">CIG-MC@geodynamics.org</a><br><a href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc" target="_blank">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a></blockquote>
</div><br></div></div></div><br>_______________________________________________<br>
CIG-MC mailing list<br>
<a href="mailto:CIG-MC@geodynamics.org">CIG-MC@geodynamics.org</a><br>
<a href="http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc" target="_blank">http://geodynamics.org/cgi-bin/mailman/listinfo/cig-mc</a><br></blockquote></div><br></div>