Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77861
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: CSV methodology |
| Date | 2014-09-14 03:02 -0400 |
| References | <b2q91ada6b59ept81ac65vtnnu6sdklp1h@4ax.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.14005.1410678164.18130.python-list@python.org> (permalink) |
On 9/13/2014 9:34 PM, jetrn@newsguy.com wrote: > > Hello. Back in the '80s, I wrote a fractal generator, which, over the years, > I've modified/etc to run under Windows. I've been an Assembly Language > programmer for decades. Recently, I decided to learn a new language, > and decided on Python, and I just love it, and the various IDEs. > > Anyway, something I thought would be interesting, would be to export > some data from my fractal program (I call it MXP), and write something > in Python and its various scientific data analysis and plotting modules, > and... well, see what's in there. First you need to think about (and document) what your numbers mean and how they should be organized for analysis. > An example of the data: > 1.850358651774470E-0002 Why is this so smaller than the next numbers. Are all those digits significant, or are they mostly just noise -- and best dropped by rounding the number to a few significant digits. > 32 > 22 > 27 > ... (this format repeats) After exactly 3 numbers in this range? > So, I wrote a procedure in MXP which converts "the data" and exports > a csv file. Answer the questions above before writing code. .csf is likely not the best format to use. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
CSV methodology jetrn@newsguy.com - 2014-09-13 21:34 -0400
Re: CSV methodology kjs <bfb@riseup.net> - 2014-09-14 02:51 +0000
Re: CSV methodology Terry Reedy <tjreedy@udel.edu> - 2014-09-14 03:02 -0400
Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-14 12:56 -0400
Re: CSV methodology Chris Angelico <rosuav@gmail.com> - 2014-09-15 03:10 +1000
Re: CSV methodology Terry Reedy <tjreedy@udel.edu> - 2014-09-14 14:42 -0400
Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-14 16:19 -0400
Re: CSV methodology Peter Otten <__peter__@web.de> - 2014-09-15 09:29 +0200
Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-15 12:33 -0400
Re: CSV methodology Peter Otten <__peter__@web.de> - 2014-09-16 13:22 +0200
Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-16 14:03 -0400
Works perfectly (was Re: CSV methodology) jayte <jetrn@newsguy.com> - 2014-09-22 20:27 -0400
Re: Works perfectly (was Re: CSV methodology) Peter Otten <__peter__@web.de> - 2014-09-23 09:59 +0200
Re: CSV methodology Cameron Simpson <cs@zip.com.au> - 2014-09-14 18:38 +1000
Re: CSV methodology Rustom Mody <rustompmody@gmail.com> - 2014-09-14 01:56 -0700
Re: CSV methodology Cameron Simpson <cs@zip.com.au> - 2014-09-15 09:28 +1000
Re: CSV methodology Akira Li <4kir4.1i@gmail.com> - 2014-09-15 11:12 +0400
Re: CSV methodology pH <high@cidity.level> - 2014-09-15 12:40 -0400
Re:CSV methodology Dave Angel <davea@davea.name> - 2014-09-15 09:29 -0400
Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-15 12:53 -0400
csiph-web