Weave introductory document. (Attachments)
Prabhu, This is *excellent*. Thanks for taking the time to put together a real world example showing so many different ways of doing things. Its a great introduction to multiple concepts. It should definitely go in SciPy. I'll find a place for it soon. For now, I'll post it on the web-site. Thanks again for all your help debugging things and for the nice document, eric ----- Original Message ----- From: "Prabhu Ramachandran" <prabhu@aero.iitm.ernet.in> To: <scipy-dev@scipy.org> Sent: Monday, January 14, 2002 9:58 AM Subject: [SciPy-dev] Weave introductory document. (Attachments)
hi,
Oops. I forgot to attach the doc and the code.
prabhu
"eric" == eric <eric@scipy.org> writes:
eric> Prabhu, This is *excellent*. Thanks for taking the time to eric> put together a real world example showing so many different eric> ways of doing things. Its a great introduction to multiple eric> concepts. It should definitely go in SciPy. I'll find a eric> place for it soon. For now, I'll post it on the web-site. Thanks! Since I'd spent time learning things I thought it would be easy for others to get the hang of it if I summarized it all and gave a working example. I learnt quite a bit. We also got to benchmark things with c++ and fortran. I have one more question. How good is pyMPI? I noticed that you are one of the developers on the sourceforge project. There isnt a proper web page or docs or any examples. ScientificPython has an MPI module. How good are these in terms of performance/capabilities and ease of use? Its obvious as to what direction I'm going. If pyMPI works well, then based on the preliminary results we have with weave, f2py etc. its pretty clear that one can do really *serious* high performance computing using Python. That would be simply amazing! The power of the Python language with very decent performance. This would make it possible to create complex CFD (or other highly compute intensive) applications using Python. The possibilities are immense! eric> Thanks again for all your help debugging things and for the eric> nice document, eric Thank you for weave!! This is the least I could do. :) prabhu
"PR" == Prabhu Ramachandran <prabhu@aero.iitm.ernet.in> writes:
"eric" == eric <eric@scipy.org> writes:
PR> I have one more question. How good is pyMPI? I noticed that PR> you are one of the developers on the sourceforge project. PR> There isnt a proper web page or docs or any examples. PR> ScientificPython has an MPI module. How good are these in PR> terms of performance/capabilities and ease of use? On a completely separate (but related note), I've updated (fixed) PyPVM to actually work, if you care for PVM's API. See http://software.biostat.washington.edu/statsoft/snake/pypvm (yes, I know that there are reasons for MPI, and it's nice, and I can give lots of reasons for preferring it; but until all of the MPI2 changes make it down, and cross-platform is easy, PVM works for me...). best, -tony -- A.J. Rossini Rsrch. Asst. Prof. of Biostatistics U. of Washington Biostatistics rossini@u.washington.edu FHCRC/SCHARP/HIV Vaccine Trials Net rossini@scharp.org -------------- http://software.biostat.washington.edu/ ---------------- FHCRC: M: 206-667-7025 (fax=4812)|Voicemail is pretty sketchy/use Email UW: Th: 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX --- I'm 40% time until March 1st. Try email the other 3 days.... -----
"AJR" == A J Rossini <rossini@blindglobe.net> writes:
AJR> On a completely separate (but related note), I've updated AJR> (fixed) PyPVM to actually work, if you care for PVM's API. AJR> See AJR> http://software.biostat.washington.edu/statsoft/snake/pypvm Oh, good. Thanks. Will keep this also in mind. prabhu
Prabhu's docs are now on the web. They are linked off the main weave page: http://www.scipy.org/site_content/weave/ eric ----- Original Message ----- From: "Prabhu Ramachandran" <prabhu@aero.iitm.ernet.in> To: <scipy-dev@scipy.org> Sent: Monday, January 14, 2002 9:58 AM Subject: [SciPy-dev] Weave introductory document. (Attachments)
hi,
Oops. I forgot to attach the doc and the code.
prabhu
On Mon, 14 Jan 2002, eric wrote:
Prabhu's docs are now on the web. They are linked off the main weave page:
That's great! However, note that the end of Prabhu's docs is quite difficult to read due to formatting failures. It shows up in my browser as a continuous text, including all code fragments. Pearu
"PP" == Pearu Peterson <pearu@cens.ioc.ee> writes:
PP> On Mon, 14 Jan 2002, eric wrote: >> Prabhu's docs are now on the web. They are linked off the main >> weave page: >> >> http://www.scipy.org/site_content/weave/ PP> That's great! However, note that the end of Prabhu's docs is PP> quite difficult to read due to formatting failures. It shows PP> up in my browser as a continuous text, including all code PP> fragments. Hmm, yeah thats right, on mozilla I cant see anything after the inline part. I dont think I formatted the document too correctly. The biggest problem being the code fragments. I didnt want to indent the code too much for fear of it becoming even harder to read. Also there is trouble with the laplace.py file i.e. http://www.scipy.org/site_content/weave/laplace.html the code after inlineTimeStep is all mangled up. Ahh I get it its the <> marks. I need to use < etc. Should I mail you an updated document? I'm sorry if for all these formatting errors. I guess this type of document is a little painful to write/edit if you use simple formatted text. Do you want me to create the document in proper HTML by using Mozilla composer or something and then mail it across? prabhu
That's great! However, note that the end of Prabhu's docs is quite difficult to read due to formatting failures. It shows up in my browser as a continuous text, including all code fragments.
Can you check and see if it is fixed now? I made a couple changes, and it looks fine here -- well at least readable. eric
"eric" == eric <eric@scipy.org> writes:
>> That's great! However, note that the end of Prabhu's docs is >> quite difficult to read due to formatting failures. It shows up >> in my browser as a continuous text, including all code >> fragments. eric> Can you check and see if it is fixed now? I made a couple eric> changes, and it looks fine here -- well at least readable. Yeah thats much better now, you also need to fix laplace.html similarly I think there are two <'s that need to become <. I just finished editing two different HTML versions of the document with a few spelling mistakes fixed. One was done by hand using Xemacs (this is clean HTML and called report.html) and the other with Mozilla (this is horrible to edit and called Performance_Python.html). I've attached both. Use it if you find it useful. prabhu
participants (4)
-
eric -
Pearu Peterson -
Prabhu Ramachandran -
rossini＠blindglobe.net