Re: Reading Fortran Data

2007-01-21 Thread Tyler
Wow! Thanks for the help everyone. I will look into each of your comments in more detail in the morning, but I'll mention a few things I guess. The first is, the list-directed output was not necesarily my choice as some of the code is also used by my supervisor (and her colleagues) and I had to ke

Re: Reading Fortran Data

2007-01-21 Thread Carl Banks
Beliavsky wrote: > Carl Banks wrote: > > > > > > A Fortran > > > list-directed write can print results in an almost arbitrary format, > > > depending on the compiler. Many compilers will separate integers by > > > several spaces, not just one, and they could use commas instead of > > > spaces if

Re: Reading Fortran Data

2007-01-21 Thread Beliavsky
Carl Banks wrote: > > A Fortran > > list-directed write can print results in an almost arbitrary format, > > depending on the compiler. Many compilers will separate integers by > > several spaces, not just one, and they could use commas instead of > > spaces if they wanted. > > 1. Hardly any co

Re: Reading Fortran Data

2007-01-21 Thread Carl Banks
Beliavsky wrote: > Carl Banks wrote: > > > > > > WRITE(90,*) nfault,npoint > > > > Fortran writes this as two arbitrary integers separated by a space. > > I wrote a paragraph in my reply explaining why this is wrong. It's a safe assumption for a line of two integers. It might not exactly prod

Re: Reading Fortran Data

2007-01-21 Thread Beliavsky
Carl Banks wrote: > > WRITE(90,*) nfault,npoint > > Fortran writes this as two arbitrary integers separated by a space. I wrote a paragraph in my reply explaining why this is wrong. A Fortran list-directed write can print results in an almost arbitrary format, depending on the compiler. Many

Re: Reading Fortran Data

2007-01-21 Thread Carl Banks
Tyler wrote: > Hello All: > > After trying to find an open source alternative to Matlab (or IDL), I > am currently getting acquainted with Python and, in particular SciPy, > NumPy, and Matplotlib. While I await the delivery of Travis Oliphant's > NumPy manual, I have a quick question (hopefully) re

Re: Reading Fortran Data

2007-01-21 Thread Beliavsky
Tyler wrote: > Hello All: > > After trying to find an open source alternative to Matlab (or IDL), I > am currently getting acquainted with Python and, in particular SciPy, > NumPy, and Matplotlib. While I await the delivery of Travis Oliphant's > NumPy manual, I have a quick question (hopefully) re

Re: Reading Fortran Data

2007-01-21 Thread Robert Kern
Tyler wrote: > Hello All: > > After trying to find an open source alternative to Matlab (or IDL), I > am currently getting acquainted with Python and, in particular SciPy, > NumPy, and Matplotlib. While I await the delivery of Travis Oliphant's > NumPy manual, I have a quick question (hopefully) r

Re: Reading Fortran Data

2007-01-21 Thread Robert Kern
[EMAIL PROTECTED] wrote: > I don't know if this is helpfull or not but (or for that matter > current). http://cens.ioc.ee/projects/f2py2e/ offers some suggestions > and it looks like you can use it with c code also. f2py has been folded into numpy. -- Robert Kern "I have come to believe that t

Re: Reading Fortran Data

2007-01-21 Thread [EMAIL PROTECTED]
I don't know if this is helpfull or not but (or for that matter current). http://cens.ioc.ee/projects/f2py2e/ offers some suggestions and it looks like you can use it with c code also. Tyler wrote: > Hello All: > > After trying to find an open source alternative to Matlab (or IDL), I > am curren

Reading Fortran Data

2007-01-21 Thread Tyler
Hello All: After trying to find an open source alternative to Matlab (or IDL), I am currently getting acquainted with Python and, in particular SciPy, NumPy, and Matplotlib. While I await the delivery of Travis Oliphant's NumPy manual, I have a quick question (hopefully) regarding how to read in F