On Wed, Mar 19, 2008 at 10:43 AM, Roch, Grant F. <<a href="mailto:Grant.Roch@constellation.com">Grant.Roch@constellation.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<p><font face="Arial" size="2">Arlindo-</font>
</p>
<p><font face="Arial" size="2">I downloaded pygrads-1.0.8.win32_superpack.exe and installed everything without issue. I'm trying to play around with the python interface but come across some issues starting the executables. </font></p>
</div></blockquote><div>Did you install the GrADS executables, in particular the win32 superpack? Before you can use PyGrADS you should be able to open a cmd.exe window and type<br><br>C:\> gradsnc<br><br>and have vanilla GrADS fully functional. PyGrADS just uses bi-directoional pipes to mcommunicate with these executables.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><p><font face="Arial" size="2">I'm trying the examples provided on the wiki, but the GaCore(Bin='grads') or GaCore(Bin='gradsnc') or GaNum(Bin='grads') don't work. I've let them run for several minutes (one time a half hour) and kill them and here's the trace back:</font></p>
</div></blockquote><div>When it works, it should be immediate. Come to think of it, I should add some explicit timeouts to the code...<br><br></div><div>...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><p><font face="Arial" size="2">I'm plotting grib files. </font></p></div></blockquote><div>I'll be soon releasing an extension for reading grib-2 files in grads v1.9.0-rc1, as a stop gap measure until we can transition the OpenGrADS development to GrADS v2. Contact me directly if you would like to help us with the early testing.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><p><font face="Arial" size="2">I've done some scripting in GrADS but am excited to try this interface out. How long will it before this the PyGrADS works with GrADS v2?</font><br>
</p>
<p><font face="Arial" size="2"></font></p></div></blockquote><div><br>This is more a question for COLA than for me. I need the ability to write dynamic extensions in order to implement all the PyGrADS functionality (in particular the fast exchange of variable data). So, I am waiting for COLA to define the dynamic UDF Application User Interface (API) before this and other OpenGrADS projects can make a switch to GrADS v2. <br>
<br>I don't know if you realize, but the basic functionality in GaCore (without numpy/pylab interfaces) already works with GrADS v2; you simply cannot exchange variable data with Python transparently. In fact, I have implemented a test suite for GrADS v2 based on GaCore and PyUnit. </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><p><font face="Arial" size="2">Thanks for any assistance you can provide. Should this be posted on the Open GrADS mailing list in the future? I was going to but didn't seem like there's much posted there (at least in comparison to the GRADS user list).</font></p>
</div></blockquote><div><br>For now, send questions like this to the regular gradsusr list. If we ever get to a point of too much traffic, or the discussions get too python specific, then it may justify to have specialized mailing list.<br>
<br> Arlindo<br><br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>
<p><font face="Arial" size="2">Grant F. Roch</font>
<br><font face="Arial" size="2">CCG Strategies Group</font>
<br><font face="Arial" size="2">W: 410-470-2565</font>
<br><font face="Arial" size="2">C: 443-670-4951</font>
</p>
<pre>>>> This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP1
</pre></div>
</blockquote></div><br><br clear="all"><br>-- <br>Arlindo da Silva<br><a href="mailto:dasilva@alum.mit.edu">dasilva@alum.mit.edu</a>