Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #77927

Re: CSV methodology

Show all headers | View raw

jayte wrote:

> On Mon, 15 Sep 2014 09:29:02 +0200, Peter Otten <__peter__@web.de> wrote:
> 
>>jayte wrote:
>>
>>> Sorry, I neglected to mention the values' significance.  The MXP program
>>> uses the "distance estimate" algorithm in its fractal data generation.
>>> The values are thus, for each point in a 1778 x 1000 image:
>>> 
>>> Distance,   (an extended double)
>>> Iterations,  (a 16 bit int)
>>> zc_x,        (a 16 bit int)
>>> zc_y         (a 16 bit int)
>>> 
>>
>>Probably a bit too early in your "Python career",
> 
> Absolutely, just thought it would be interesting to start experimenting,
> while learning (plus, can't help but be anxious) <g>
> 
>> but you can read raw data
>>with numpy. Something like
>>
>>with open(filename, "rb") as f:
>>    a = numpy.fromfile(f, dtype=[
>>        ("distance", "f16"),
>>        ("iterations", "i2"),
>>        ("zc_x", "i2"),
>>        ("zc_y", "i2"),
>>    ]).reshape(1778, 1000)
>>
>>might do, assuming "extended double" takes 16 bytes.
> 
> Will try.  Double extended precision is ten bytes, but I assume
> changing  the "f16" to "f10" would account for that...

Unfortunately it seems that numpy doesn't support "f10" 

>>> numpy.dtype("f8")
dtype('float64')
>>> numpy.dtype("f16")
dtype('float128')
>>> numpy.dtype("f10")
dtype('float32') # looks strange to me

But you better ask for confirmation (and possible workarounds) in a 
specialist forum.

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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