[NeXus-definitions-tickets] [NeXusDefinitions] #130: proposal for image_exchange format

[NeXus Base Classes and Instrument Definitions]

#130: proposal for image_exchange format
------------------------+---------------------------------------------------
Reporter:  Pete Jemian  |       Owner:  Pete Jemian
    Type:  task         |      Status:  assigned   
Priority:  minor        |   Milestone:             
Keywords:               |  
------------------------+---------------------------------------------------
Changes (by Pete Jemian):

  * status:  new => assigned


Comment:

 note on compound strings used in this plan (such as
 {{{positioner_names}}}):

 {{{
 The structure as proposed looks like this:

  textstring_bytes = 16  (grown to next "modulo 4" boundary)
  n_specimen_names = 3
  specimen_names = "string0000000000longer string000msg0000000000000"

 textstring_bytes  tells the maximum number of a bytes a single string can
 hold
 n_specimen_names  tells how many strings are in specimen_names
 specimen_names  holds all the strings for specimen names
 Strings that are shorter than  textstring_bytes  are zero-padded

  Instead, why not use (newline as string delimiter) something like this?
  specimen_names = "string\nlonger string\nmsg"

  Python: "string\nlonger string\nmsg".split("\n") gives
  ('string', 'longer string', 'msg')
 }}}

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/130#comment:1>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions